Skip to content

Make WhatsApp feel like part of your product.

Connect your WhatsApp Business Account and give customers rich, two-way conversations with a business they recognize. Sent handles the operational complexity behind every message.

  • Interactive Buttons
  • Rich Media
  • Two-Way Conversations
  • Customer Support
  • Smart Routing
  • Read Receipts

14,000+ developers and product teams rely on Sent for messaging

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

A familiar place for important customer conversations.

  • A verified business thread telling a customer their order has shipped

    Recognizable from the first message

    Communicate through your WhatsApp Business identity so customers immediately understand who is contacting them.

  • A check-in message offering a seat choice and a bag add-on as buttons

    The next step is built in

    Give customers the information and action they need without sending them through another channel or disconnected journey.

  • A delivery notice, a customer asking for the parcel to be left out back, and the business confirming

    The conversation can continue

    Let customers respond naturally and carry their reply into your product, automation or support workflow.

Turn product events into WhatsApp journeys.

Trigger the right conversation from the systems that already know what happened.

  • An abandoned cart event triggering a WhatsApp message that links back to checkout

    Bring shoppers back to checkout

    When checkout stops, send the saved products, an offer where appropriate, and a direct route back to the customer cart.

  • A locked-gate delivery exception becoming a WhatsApp message with two ways to resolve it

    Keep every order moving

    Send confirmations, shipping progress, delivery windows and exception alerts with a clear next action.

  • Verify accounts in context

    Send approved authentication messages with a clear code, expiry and recognizable business identity.

  • Confirm appointments immediately

    Let customers confirm, reschedule or view appointment details directly from the message.

  • Resolve support through replies

    Receive customer responses and move the conversation into your product, automation or support system.

Messages people understand at a glance and act on immediately.

Combine structured content, customer data, rich media and channel-native actions to create messages that feel designed for WhatsApp.

A WhatsApp message opening with a product photograph above a delivery slot button

From business setup to an approved send.

Bring WhatsApp Business setup, sender identity, template approval, consent and conversation rules into one managed workflow.

  • The Sent mark linked to the WhatsApp mark

    Connect WhatsApp Business

    Link an existing or new WhatsApp Business Account and attach the sender identity your customers will see.

  • A template with variables moving through review to approved

    Create and submit templates

    Build the message with variables, media and actions, then submit it to Meta and follow its approval state.

  • A 24-hour service window opening when a customer replies

    Manage active conversations

    Know when an approved template is required and when a customer reply has opened the 24-hour service window.

  • WhatsApp Business Account
  • Meta template approval
  • Consent controls
  • Conversation-window rules
One request passing through smart routing to WhatsApp, with a fallback path ready

Send once. Let Sent handle the route.

Trigger a WhatsApp message with one API request. Sent checks consent and availability, then uses the configured fallback when WhatsApp cannot deliver.

Explore the API
A delivered and read message with the customer reply returning to the product

Know what happened after every send.

Track every message from queued to delivered, read, or failed, and receive customer replies in your product through real-time webhooks.

Explore webhooks

Three channels. One consistent way to send.

Use SMS, WhatsApp, and RCS through the same API, templates, routing system, and delivery data.

  • SMS

    Reach almost any phone with fast, reliable messages for authentication, alerts, reminders, notifications, and campaigns.

    Read More
  • WhatsApp

    Create rich, two-way customer experiences with templates, media, conversations, and official WhatsApp Business delivery.

  • RCS

    Send branded messages with images, buttons, cards, and carousels, with automatic SMS fallback when RCS is unavailable.

    Read More

Frequently asked questions

Sent gives you one API for SMS, WhatsApp and RCS, with routing, retries, template management, compliance handling and delivery tracking built in. You send one request and Sent decides how it reaches the customer.

Yes. Templates support locale variants, so you can define a message once per language and Sent selects the right one from the recipient profile or an explicit locale on the request.

You can pin a message to a single channel, give an ordered list of preferred channels, or let Sent Routing choose. Pinning is useful for regulated message types that must go over one specific channel.

Transactional messages such as one-time passcodes, order and delivery updates and account alerts, plus conversational and campaign messages where the channel allows it.

Sent sits behind one API and emits signed webhooks for every state change, so it drops into an existing stack without replacing your CRM, support desk or data warehouse.

Install the SDK, authenticate with your API key, then call sent.messages.send with a recipient, a template and the channels you allow. Everything after that, including routing and fallback, is handled for you.

Yes. Images, video, documents and rich cards are supported on the channels that allow them, and Sent adapts or drops the media automatically when a message falls back to a channel that does not.

Add them to the template as variables. Sent handles link shortening and per-channel attachment rules, and click events come back through the same webhooks as delivery events.

Every message exposes its full timeline: accepted, routed, sent, delivered, read and failed, with the route taken at each step. The same data is available in the dashboard and over the API.

Sent manages sender registration, template approval, opt-out handling and per-country sending rules, and blocks a send when the destination would breach them.

That is the default. One integration covers every channel you enable, and adding a new one does not require changes to your send code.

A full sandbox mirrors production behaviour, including routing decisions, failures and webhooks, so you can test fallback paths without sending a real message.