Sent wants your message to take the hint

Daniel Vataj was travelling internationally when his bank sent him a verification code. According to Sent’s account of its origins, the SMS never arrived. The bank account remained out of reach. A small message had become a very large inconvenience. Vataj’s objection was wonderfully practical: why couldn’t the code have come through WhatsApp instead?

That question became the premise of Sent, founded by Vataj and Betim Drenica in December 2023, according to its current company history. Both had spent years dealing with messaging integrations. Their diagnosis was that reliability needed to live beneath the application. Sent’s own telling includes the admission that the platform was built partly out of spite. Infrastructure rarely gets such an honest motive.

Let the number choose the door

Think of an order confirmation. The business knows the recipient’s phone number and what it needs to say. Choosing the channel introduces another set of questions: which service is available, which template is approved, which route can actually deliver? With separate integrations, those questions accumulate inside the business’s software. Every new channel gives the developers another small jurisdiction to administer.

Sent offers a unified API for SMS, WhatsApp and RCS. Its routing documentation describes a decision made at send time, using recipient capabilities, account rules and compliance checks. Candidate routes are ordered; the first viable candidate gets the message. Developers can also pin a channel when their application requires one. The convenience is a default, with room for a deliberate choice.

The same thinking extends to content. Templates keep a message’s identity while changing its presentation. Sent’s template documentation supports channel-specific overrides: an RCS version can use rich cards and suggested actions, while SMS receives plain text. A merchant gets room for an expressive message without making the plain version an entirely separate engineering project. The costume changes; the order number should not.

Fallback is the next part of the bargain. Recoverable failures can trigger another candidate route, with at most three distinct routes attempted under the documented process. Invalid numbers and opted-out recipients stop the send. That distinction matters. A useful routing system must know when persistence helps and when persistence becomes a mistake.

A penny and a half, then the postage

Sent sells infrastructure to businesses whose software needs to communicate with customers. Login codes, appointment reminders and order confirmations are obvious uses. Its product pages also offer WhatsApp media and template management, plus RCS cards, carousels and interactive replies. These are tools for product teams building customer communication into an application, with the channel machinery supplied underneath.

The dedicated pricing page lists a platform fee of $0.015 per contact messaged per month, alongside delivery costs. Message destination, carrier network, provider availability and fallback route can change the total. For 10,000 contacts in a month, the platform component alone is $150. That is useful arithmetic because it separates access to the routing layer from the cost of carrying the messages.

A comparison should therefore use an actual traffic mix. How many people receive messages? Where are they? How often are they contacted? What happens when the preferred route fails? The answers decide whether a tidy headline rate becomes a tidy bill. Buying a messaging API on a single advertised number is rather like judging a hotel by the price of its minibar water.

Twilio, Sinch, Infobip and Bird are established alternatives in business messaging. Sent’s positioning emphasizes a shared routing and compliance layer that saves customers from maintaining channel-specific logic. Another alternative is keeping direct integrations or building that layer internally. The important comparison includes engineering attention: somebody must own the retries, changing approvals and awkward delivery failures.

The plumbing acquires a licence

Sent announced a $3.55 million seed round in May 2025, led by Companyon Ventures. In July 2026 it announced a $12 million Series A, again led by Companyon, with Bessemer Venture Partners, Urban Innovation Fund and CP Overture participating. The announced spending priorities include expanding its direct carrier network, developing agent-facing infrastructure and growing engineering, compliance and enterprise teams.

“The next generation of messaging infrastructure has to make complexity disappear without sacrificing control.”Betim Drenica · CTO and co-founder

The company says it has become a licensed U.S. telecom carrier. In its July announcement, it names TrimRX, ITM Studio and ITNIO Tech as customers that moved from Twilio. The ambition reaches beyond a neater API: Sent wants greater participation in the network beneath it. Its published MCP tooling also gives compatible AI clients a way to use messaging tools. An agent’s eloquence is of limited value if its confirmation never arrives.

Try the ordinary messages first

For a developer, the entrance is modest. Sent’s quickstart describes light onboarding with a verified email and phone number, six pre-built templates and daily sending limits. Custom templates and an owned sender number require fuller setup. Official SDKs cover TypeScript, Python, Go, Java, C#, PHP and Ruby. Webhooks return delivery and other events, giving an application something more useful than an optimistic assumption.

There is operational work here, even with shared infrastructure. Sent’s troubleshooting guide lists unapproved templates, incomplete verification, carrier filtering and unavailable channels among delivery problems. Its January 2026 changelog records fixes to fallback logic and SMS encoding. These mundane details make the proposition easier to assess: messaging reliability is an ongoing maintenance task, including for the company selling it.

The practice readers can copy is Sent’s staged migration advice: begin with non-critical notifications, run a comparison with the existing integration, then move critical flows after evaluating delivery and cost. Its own comparison guide suggests direct providers can suit low-volume, single-channel needs or applications requiring provider-specific features. Sent makes its strongest case when channel complexity is already consuming a team’s time. Start with a message you can measure, and see where it goes.