Sending SMS, WhatsApp, and RCS messages should be simple β but in the real world, you end up dealing with registrations, approvals, carrier routing, country rules, retries, and webhooks just to answer one question: did the message land?
This video shows how to avoid all of that complexity with Sent, a single API that can route messages across WhatsApp, SMS, and RCS automatically.
Sent handles channel availability, formatting, fallbacks, compliance, delivery states, and webhook updates behind the scenes, so your app can send the right message through the best channel without maintaining separate integrations for each one.
Iβll walk you through a full delivery tracking demo using the Sent's TypeScript SDK, Convex, real webhooks, approved templates, contacts, automatic routing, and AI agent setup with the Sent's MCP Server.
Weβll cover:
β
Why sending SMS gets complicated fast
β
How Sent routes WhatsApp, SMS, and RCS from one API
β
Setting up API keys, webhook secrets, and template IDs
β
Sending real WhatsApp and SMS messages from a demo app
β
Tracking queued, sent, delivered, and read states in real time
β
Using templates, dynamic variables, buttons, and rich WhatsApp messages
β
Handling Sent's webhooks with Convex or Next.js route handlers
β
Using the Sent's MCP and docs to build faster with AI agents
If youβre building apps that need reliable user messaging, this is one of the cleanest ways Iβve seen to ship multi-channel delivery without fighting every carrier and platform yourself.