Agent-readable docs index: /docs/llms.txt. Full docs in one file: /docs/llms-full.txt. Download /docs/docs.zip to grep all markdown files locally.

WhatsApp, SMS and email messaging documentation

Convert brings WhatsApp, SMS, and email messaging into one workspace. Use the dashboard to build audiences and campaigns, or connect your application through the REST API for transactional notifications and customer events.

Choose your starting point

Set up your workspace
Connect a channel, add contacts, and prepare your first message.
Integrate the API
Create a scoped key and validate your first request without sending.
Build a campaign
Choose an audience, personalize content, and review delivery results.
Automate a journey
React to contact activity with messages, delays, and conditions.

What you can do

  • Channels: connect a WhatsApp number or Meta Cloud channel, use approved SMS Sender IDs, and send from your own verified email domain.
  • Audiences: manage contact lists, import CSV or Excel files, collect signups with forms, and publish reusable segments.
  • Messaging: create templates, launch campaigns, send single transactional messages, and queue personalized batches.
  • Automation: identify contacts, report events, and run versioned journeys with conditions and checkpoints.
  • Tracking: inspect campaign outcomes and receive signed delivery, engagement, and inbound-message webhooks.

Understand the delivery lifecycle

Acceptance is the first milestone. A synchronous API response indicates provider submission; a batch response indicates queued work. Delivery receipts and webhooks report subsequent outcomes. A campaign finishing its send phase does not guarantee every recipient received or read the message.
Dashboard or API ──> Validation and eligibility ──> Queue or provider submission
                                                            │
                    Your webhook receiver <── Delivery events <── Recipient
Smart routing on the messages API chooses WhatsApp or SMS. Automation Smart Channel can also include email. See routing.

Documentation scope

These guides describe the current Convert implementation. Examples use fictional contacts and placeholder credentials. Use the sender, domain, limits, and prices displayed in your workspace; availability can depend on deployment and plan. Reference content was checked against the code on 11 October 2026.
Need a specific answer? Start with troubleshooting, API errors, or the go-live checklist.