When a messaging operator needs to resell SMS to hundreds of downstream businesses, the panel behind it has to do a lot more than "send a message." It has to meter every credit, switch routes when an operator link drops, keep each reseller's data walled off from the next, and never lose a delivery report. That is the platform we built.
The brief
The client ran bulk SMS at scale but was stitched together across spreadsheets and a basic sending tool. They wanted a single product they could put their own brand on, hand to resellers, and trust with a billion-plus messages a year.
What we built
We designed a multi-tenant core where every reseller gets an isolated account, their own logo and login URL, their own pricing, and their own sub-users. On top of that sits a credit-and-billing engine that meters transactional, promotional and OTP traffic separately, because each carries a different cost and route.
The part that mattered most was routing. We built failover across multiple operator connections so that if one route degrades, traffic re-balances automatically to a healthy one — the difference between an OTP arriving in two seconds and a customer abandoning a checkout. Delivery receipts are reconciled back to each message so reporting is accurate down to the individual SMS.
The result
The operator now runs their entire reseller network from one panel, onboards a new reseller in minutes instead of days, and exposes a clean HTTP/XML/SMPP API that downstream developers integrate without hand-holding. It is the same engineering discipline behind our own bulk SMS service in Coimbatore.