Deployments in detail
Two deployments are documented below in full: what each customer was running beforehand, what was installed, and the current position. Figures are stated only where we have measured them.
Our customers operate under their own brands, so these accounts are published without names or identifying detail, with the customer’s agreement.
A two-person startup that became a regional SMS distributor
Before
Two employees of an SMS marketing company left to establish their own business. They had market knowledge and commercial contacts but no technical platform: no messaging gateway, no billing, no client portals and no routing.
What we built
A new installation of the full platform on their own server, under their brand, with reseller portals and billing configured during handover. Seven days elapsed between first payment and live traffic.
Current position
The reseller portal became their principal commercial differentiator, allowing partners to trade under their own branding with independent rate cards and billing. Traffic grew alongside the reseller base. The customer has taken each subsequent release, adding WhatsApp and RCS as client demand required, and is now among the larger SMS distributors in its region.
Thank you for all your support. We are very grateful for your urgent assistance.
A CPaaS operator required multi-user accounts
Before
The operator was running an earlier release in which one account permitted one set of credentials. Several staff needed to work within the same account, each with individual logins, while sharing contacts, credit and message history. The only available workaround was a shared password.
What we built
An upgrade to the current release including the team-members module, which allows one account to carry multiple users with individual credentials and per-user permissions. The chatbot builder and multi-currency billing were included in the same release. Existing users, credit balances and message history were migrated. Approximately two weeks elapsed between agreement and handover.
Current position
The platform is running on the current release. Team accounts are in use and permissions are administered per user rather than through shared credentials. This entry will be extended once a full quarter of operating data is available; we do not publish projected results.
Further deployments
Most of our customers operate under their own brand and prefer not to be written about at all. Deployments are documented here only after go-live and with the customer’s agreement, which is why this page is shorter than the install count.