The same suite, without the server room.
Managed hosting for the modules you choose: no installation project, no hardware sizing, and the same interface your team would run on-premise. Start with channels and helpdesk, add voice later.
The same PDS applications, operated by us as a subscription service. No servers to provision, no upgrades to schedule, no backup job to forget.
Cloud is the right choice when the team is distributed, when user counts change month to month, or when internal IT capacity is already committed elsewhere.
- 0Servers to provision before the first conversation
- 1Interface across plans — moving to on-premise later changes the address, not the workflow
- 24/7Managed operation with a monitored backup schedule
Live in days, not in a project plan.
The tenant is provisioned, the channels are connected, and the team is invited. The first configuration is the same one you would do on-premise: working hours, agent groups, templates, and the knowledge base.
- Tenant provisioned with an administrator account and a test workspace
- Channel connections done from the admin screen, not from a ticket to support
- Starter configuration: working hours, groups, templates, articles
The plan changes when the team changes, not the interface.
Adding agents, channels, or storage is a plan change. Voice can be added when the call volume justifies it, with its own numbering and queue configuration.
- Agents, channels, and storage adjusted per plan
- Voice added later without a migration project
- Usage visible per month, per module
| # | Subjek | SLA |
|---|---|---|
| 1841 | Gagal login aplikasi | 2 jam |
| 1842 | Permintaan reset kata sandi | Selesai |
| 1843 | Invoice belum diterima | Hari ini |
Your data is exportable, and leaving is not an argument.
Contacts, tickets, conversations, and reports export in a documented format. Backups run on a monitored schedule, and the retention per document type is agreed in the contract — including what happens at termination.
- Documented export of contacts, conversations, tickets, and reports
- Monitored backup schedule with a stated retention
- Termination and data-return terms agreed before the first invoice
What the cloud plan includes
Managed hosting
Application, database, and workers operated for you.
Channels
WhatsApp, Instagram, Facebook, Telegram, email, and webchat connectors.
Helpdesk & CRM
Same modules as the on-premise plan, same interface.
Voice (optional)
Numbering, IVR, queues, and recording added per plan.
Reporting
Operational reports with monthly exports.
Support
Support window per plan, with an escalation path that is written down.
From trial to production
One channel, one team, two weeks of real conversations.
Agents, channels, storage, and whether voice is in scope.
Contacts and open tickets imported; templates and articles recreated.
Monthly review of backlog, response time, and cost per conversation.
Questions before a cloud plan
Can we move to on-premise later?
Yes. The data exports, and the module configuration follows; the deployment model is a contract decision, not a rebuild.
Where is the data hosted?
In the region agreed in the contract, operated under our backup and access policy.
Is voice available in the cloud plan?
Yes, as an add-on with its own numbering and queue configuration.
What happens to our data if we stop?
It is exported in the documented format within the agreed window, then deleted per contract.
Estimate your subscription.
Tell us the module set, active users, and expected message volume. We respond with a monthly figure and a migration path.