Skip to content

Building the #1 platform for messaging

Get a demo tailored to your messaging use case.

  • Modulify
  • onesim
  • Motion
  • Loop
  • attio
  • Antimetal
  • Retool

Talk to sales

Share a few details and we'll redirect you to schedule a 30-minute call with our team.

Frequently asked questions

You go straight to our calendar to pick a 30-minute slot. Before the call we read what you wrote here, so we arrive knowing which channels you need and roughly what you send.

No. You can create an account, get an API key and send your first message today without speaking to anybody. Sales exists for volume pricing, sender registration and migrations, not as a gate in front of the product.

Per message, with the rate depending on channel, destination country and monthly volume. There is no platform fee to reach the API. On the call we price against your actual traffic rather than a list rate.

One integration, so most teams are sending in test on the first day. Production timing depends on registration: SMS sender IDs and WhatsApp business verification are decided by carriers and Meta, and typically take a few days to a few weeks by country.

Yes, and most teams do. You can route a share of traffic through Sent, compare delivery against your existing provider on the same messages, and move the rest once the numbers agree.

We run the submissions, template approvals and business verification with you, and tell you where each one stands. We cannot shorten the review itself: that decision belongs to Meta and to the carriers.

The platform runs well past a billion contacts and the API is built for burst traffic, so a campaign spike is a normal event rather than a capacity conversation. Bring your peak send and we will talk through how it is routed.

Yes. Sent operates to a 99.9% uptime guarantee, and annual plans can carry support response times and an escalation path alongside it.

SMS reaches effectively every market. WhatsApp and RCS coverage varies by country and by device, so Sent falls back to a channel that will actually arrive rather than failing the message. We will map your destinations on the call.

Consent, opt-outs, quiet hours and frequency rules are applied before a message is dispatched, not audited afterwards, and every send leaves a delivery record you can query. Regulated teams should bring their requirements to the call.

On annual plans, yes: a named account contact and a shared channel with the engineers who run the platform, rather than a ticket queue.

Which channels you want, roughly what you send a month, the countries you send to, and your deadline. That is enough for us to give you real pricing and a realistic timeline on the call itself.