Fleet & driver dispatch
Dispatch teams coordinate drivers across shifts, routes, and job queues. A consistent number means drivers always know where instructions come from and can reply to acknowledge with no app install, no login, and no push notification to miss.
Field teams and delivery drivers are not always in front of a screen. An app-based dispatch system requires every driver to have the app installed, logged in, and notification-enabled on their personal device. SMS requires none of that. Every driver already has it, and it works on any phone regardless of OS version or storage space.
When a job is assigned, your dispatch system sends an outbound message with the driver's number, the job details, and the device ID of your dispatch phone. The driver receives the assignment and replies ACK. The reply arrives at your webhook automatically, your system marks the job as acknowledged, and dispatch knows the message was read without calling the driver to confirm.
The same API handles customer-facing ETAs. Use a different device ID for a customer-facing number and your system can send arrival updates automatically as the driver progresses through the route. Two numbers, same API key, controlled separately.
Reply events trigger the next step in your dispatch logic automatically. A driver who replies DONE closes the job. A driver who replies DELAY triggers a reroute. The conversation is structured SMS, not free-form chat, and your system handles each keyword as a workflow event.
Clinic appointment reminders
Send reminders from the clinic's own number. Patients already have it saved. Replies route back to your system.
Read →AIAI agents that text humans
Give your AI agent a real phone number. Outbound messages and inbound replies flow through the same API.
Read →E-commerceOrder & shipping updates
Confirmations and dispatch notifications from a number your customers recognise. Flat monthly cost.
Read →Ready to connect your first device?
Free plan. One device, 500 messages per month. No credit card required.