Reaching everyone in Eswatini at once
Harvest coordination and worker dispatch. One send covers the whole list on +268 numbers, with reached over direct routes.
Nature · +268
Harvest coordination and worker dispatch. In Eswatini that traffic runs on the route that performs best for +268, priced per message before you send.
Harvest coordination and worker dispatch. One send covers the whole list on +268 numbers, with reached over direct routes.
We hold a primary and a backup route for Eswatini. If the primary rejects or times out the message moves instantly, so the send finishes inside its window.
Every destination has a published price per message segment. Your balance is reduced with that exact price, so the cost of a campaign is known before the first message leaves.
Sender ID rules differ between markets. We apply the local registration and formatting requirements for Eswatini so your messages arrive with the identity your recipients expect.
Each message returns a status: queued, sent, delivered or failed, with the reason attached. History is searchable and exportable for reconciliation.
Create an API key in your workspace and send from your own systems. The same routes, pricing and reporting apply to API traffic and to messages sent from the interface.
The route to Eswatini has a published price per segment in EUR that you see before sending.
Yes. Pick the local delivery time for Eswatini and the send runs then, or cancel it beforehand at no cost.
Messages on direct routes to Eswatini normally reach the handset within seconds. Delivery time depends on the receiving operator and the current network load.
Each route has a fixed price per segment in EUR, shown before you send. Longer messages are split into segments and priced per segment.
Yes, where the local rules in Eswatini allow alphanumeric sender IDs. Some markets require pre-registration, which we handle with you.
Get the Eswatini route price for farms.