Add A2P routes without building carrier relationships in every market

Verification codes, account and order notifications, and marketing to recipients who opted in. We review sample content before a route goes live.

Yes. Request a test route; after we review your inquiry we set up test credentials so you can send to your own handsets.

No. Request a rate sheet with your destinations and monthly volumes and we send rates for those routes.

We do not promise a fixed lead time. The agreement, company verification and, where a market requires it, sender registration set the pace, so the timeline depends on your destinations and sender types. Your quote sets it out.

Rates are wholesale and quoted per destination and volume, so ask for a rate sheet for the destinations you sell and build your own retail price on top of it. Keep the CDR export in your billing: it carries the per-message records you need to reconcile with your customer invoices.

Registration is per market, and it is tied to the brand your customer sees. Tell us the sender and the destination early; where a market requires registration we coordinate it, but the paperwork and the brand proof come from your customer. Sender registration explains what is usually asked for, and sender IDs in Mexico and Brazil shows how two markets differ.

You can start with the destinations you choose; the quote confirms volume and terms per destination. One SMPP bind or HTTP endpoint to us covers every destination, while sender type and route change per destination, so keep the sender as a parameter in your template layer. Start with a test route: after we review your inquiry we set up test credentials so you can send to your own handsets on the destination you choose. Dedicated number ranges can be reserved for your traffic. A delivery report says the network accepted a message, not what the handset showed, so before you move a destination, rule out template causes with the content pre-check, the SMS segment counter and the SMPP and DLR code decoder.

Delivery reports show acceptance rates per destination, and a test to your own handsets shows what the phone actually received. Tell us what you see; a failed test leads to a route review.

Yes. The agreement is wholesale: your platform is the product your customers see, and rate sheets and route notices come to you. The partners page covers reseller and aggregator terms.

Yes, and it is common to use SMPP for volume and HTTP for back-office or fallback paths. The trade-offs are latency per message, how you handle retries and how you receive delivery reports; SMPP or HTTP compares them, and connecting over SMPP or HTTP covers the session details.