Skip to content
WhatsApp

Autocloz + Twilio WhatsApp

Twilio WhatsApp sends Autocloz WhatsApp messages through a WhatsApp sender registered on your Twilio account. You add your Account SID, Auth Token and a WhatsApp sender (such as whatsapp:+14155238886 for Twilio's sandbox) on the Twilio card in Settings → Integrations, then add the number under WhatsApp → Numbers. Outside the 24-hour window, a step sends a Twilio Content template by its Content SID (HX…) with variables. Replies need a relay into Autocloz, because Twilio's webhook format is not accepted directly. For native two-way WhatsApp, Meta Cloud API is simpler.

Good to know. Outbound Twilio WhatsApp works from the Settings card. Inbound replies and status callbacks need a relay to Autocloz's signed endpoints.

Autocloz and Twilio WhatsApp integration
Bring your own accountWorkspace-scoped, no cross-org leakFree-forever CRM core

What you can do with Twilio WhatsApp

Twilio WhatsApp plugs into the WhatsApp stack — bring your own whatsapp business account, scoped to your workspace.

Content templates by SID

Outside the 24-hour window the step's template field carries a Content SID and its variables, and Autocloz sends ContentSid and ContentVariables to Twilio.

Same Messages API as SMS

WhatsApp uses Twilio's Messages endpoint with whatsapp: prefixed numbers. Autocloz adds the prefix.

Sender pools

A Messaging Service SID can be used as the WhatsApp sender, so Twilio picks from your registered senders.

How to connect Twilio WhatsApp

Bring your own WhatsApp Business account — you keep control of the account, the spend and the data boundary.

  1. 1

    Register a WhatsApp sender in Twilio

    Use Twilio's sandbox for testing, or register your business number as a WhatsApp sender through Twilio.

  2. 2

    Create Content templates

    In Twilio Content Template Builder create templates and get Meta approval. Note each Content SID (HX…).

  3. 3

    Fill in the Twilio card

    Settings → Integrations → WhatsApp → Twilio: Account SID, Auth Token and WhatsApp sender.

  4. 4

    Add the sender and test

    WhatsApp → Numbers → add the number with provider Twilio, Verify, then send a template to your own number.

Twilio WhatsApp versus Meta Cloud API in Autocloz

Both send official WhatsApp Business messages. Meta Cloud API connects in one sign-in, manages templates inside Autocloz, and receives replies and read receipts natively. Twilio needs templates built in Twilio and a relay for replies, but suits teams already using Twilio numbers and billing.

Twilio card fields used for WhatsApp

WhatsApp reads these fields from the shared Twilio card:

  • Account SID and Auth Token
  • WhatsApp sender: a registered WhatsApp number, or a Messaging Service SID (MG…)
  • API base URL: only for test mode

Templates on Twilio versus on Meta

With Twilio, templates live in Twilio's Content API and are referenced by a Content SID. Autocloz does not submit or sync Twilio templates; you create them in Twilio and paste the SID into the step. With Meta Cloud API, templates are created and tracked inside Autocloz. That difference matters if you manage many templates.

Inside the 24-hour window, the step can send free text instead, and Autocloz posts it as a normal Body. It detects the open window from inbound WhatsApp messages it has seen, which again depends on replies being relayed in.

What a relay needs to do for Twilio WhatsApp

Twilio posts inbound WhatsApp messages and status callbacks as form data signed with Twilio's scheme. Autocloz's inbound endpoint expects JSON with the channel, from and to numbers and body, signed with its own shared secret. A relay translates one to the other. With it in place, replies thread in the Unibox, the 24-hour window opens, and the lead stops receiving sequence steps. Without it, WhatsApp through Twilio is outbound only. Background on the rules: WhatsApp Business API.

What Twilio WhatsApp does not do in Autocloz

  • No native Twilio inbound or status webhook.
  • No creation or sync of Twilio Content templates.
  • No bypass of Meta's opt-in and template rules.

Troubleshooting Twilio WhatsApp

Twilio error 63016 (outside the window).
Free text was sent to a contact outside 24 hours. Use a Content SID template.
Twilio rejects the sender.
The WhatsApp sender field must be a registered WhatsApp sender, with or without the whatsapp: prefix.

Part of the WhatsApp stack

Twilio WhatsApp is one of the providers behind the WhatsApp channel. All providers share the same template gating, opt-in enforcement and unified-inbox threading.

Explore the WhatsApp feature

Related integrations

Frequently asked

Can I use Twilio's sandbox?

Yes. Put the sandbox number in the WhatsApp sender field and join the sandbox from your phone first.

Does Autocloz sync Twilio WhatsApp templates?

No. Create them in Twilio's Content Template Builder and paste the Content SID into the step.

Can I use Twilio for WhatsApp and SMS at once?

Yes. The same Twilio card holds the SMS from-number and the WhatsApp sender. Add a sender for each channel.

Run Twilio WhatsApp inside Autocloz

Bring your own account, plug it into the WhatsApp channel, and keep a free-forever CRM for 3 users.