SMS Aggregation for CPaaS and Enterprises

Use cases

• One-time passcodesLogin and transaction verification, where seconds matter. OTP messaging
• Transactional alertsPayments, account changes, deliveries and bookings.
• NotificationsReminders and service messages from apps and enterprises.
• CPaaS resalePlatforms reselling international SMS to their own developers and customers.

How it works

1. Connect once. Bind to us over SMPP, or send over HTTP.
2. Submit messages. Each message carries the destination number, sender ID and text.
3. We route by destination network. The number's current network is identified, and the message goes on an approved route to that operator.
4. You get a delivery report. The final status returns on the same connection.

Sender ID registration by country

Sender ID rules are the most common reason A2P messages fail. Some countries accept alphanumeric sender IDs freely, some require each one to be registered with the operator or regulator, and some allow only numeric senders. We tell you each destination's rule before traffic starts and help with registrations where needed.

Throughput and failover

Throughput per connection is agreed during onboarding and set to match your traffic. Traffic to each destination can fail over between approved routes when quality drops. Technical details are on SMPP connectivity.

Reporting

Delivery reports per message, and traffic summaries by destination and status, so you can reconcile against your own records and invoices.

Coverage and policy

Every country except those under UN, US (OFAC), EU or UK sanctions, on direct and approved routes only. Traffic that breaches destination rules or operator policies, such as unregistered sender IDs or prohibited content, is not delivered.