SMS

Autocloz + Twilio SMS

Twilio SMS sends Autocloz text messages through your own Twilio account. Enter your Account SID and Auth Token, plus a from-number or a Messaging Service SID, on the Twilio card in Settings → Integrations. Then add the sending number under SMS → Numbers and click Verify. SMS steps in sequences go out through Twilio's Messages API. If you set a Messaging Service SID it wins over the from-number, so Twilio can pick the sender from its pool. Inbound replies need a relay, described below. US traffic needs 10DLC or a toll-free number.

Good to know. Outbound Twilio SMS works from the Settings card. Twilio's inbound webhook format is not accepted directly, so two-way threading needs a relay.

Bring your own accountWorkspace-scoped, no cross-org leakFree-forever CRM core

Start free See pricing

What you can do with Twilio SMS

Twilio SMS plugs into the SMS stack — bring your own sms provider, scoped to your workspace.

From-number or Messaging Service

Send from one number, or from a Messaging Service SID so Twilio picks a sender from the service's pool.

SID and token only

Twilio authenticates with the Account SID and Auth Token. The card also has an API base override for Twilio test mode.

Part of a sequence

SMS steps sit next to email, LinkedIn, WhatsApp and calls, and stop for a lead once they reply on any connected channel.

How to connect Twilio SMS

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

1
Prepare Twilio
Buy or port an SMS-capable number, and register a 10DLC brand and campaign (or a verified toll-free number) for US recipients.
2
Fill in the Twilio card
Settings → Integrations → SMS → Twilio: Account SID (starts AC), Auth Token, from-number and optionally a Messaging Service SID.
3
Add the SMS sender
SMS → Numbers → add the number with provider Twilio, set limits, click Verify.
4
Send a test
Text your own phone from a one-lead sequence and check the Twilio console shows the message as delivered.

Twilio card fields used for SMS

The Twilio card serves voice, SMS and WhatsApp. SMS reads these fields:

Account SID (starts AC) and Auth Token: always required.
Messaging service SID: if set, used as the sender instead of the from-number.
From number: the E.164 sender when no Messaging Service is set.
API base URL: only for Twilio test mode.

Messaging Service SID versus from-number

When the Twilio card has a Messaging Service SID, Autocloz sends with that SID and Twilio chooses the actual number, which helps with sender pools and sticky senders. Without it, the card's from-number is used. The Twilio card also stores a WhatsApp sender for Twilio WhatsApp; SMS ignores it.

Credentials are read from the card each send, so rotating the Auth Token in Twilio only needs one update in Settings.

Replies, delivery status and STOP

Twilio posts inbound texts and status callbacks as form-encoded requests signed with Twilio's own scheme. Autocloz's inbound endpoint expects its own JSON shape signed with its inbound secret, and its outcomes endpoint works the same way. A small relay that translates Twilio's callbacks is needed for replies to reach the Unibox and for delivery status to update. With a relay in place, STOP-style replies add the number to DNC across all channels. Twilio also applies its own opt-out handling on US numbers regardless.

What Twilio SMS does not do in Autocloz

No native Twilio inbound or status webhook.
No number buying or 10DLC registration inside Autocloz.
SMS templates over 320 characters are rejected at save time.

Troubleshooting Twilio SMS

Twilio error 30034 or similar on US sends.: The number is not in an approved A2P 10DLC campaign.
Sends go out from an unexpected number.: A Messaging Service SID is set, and Twilio picks from its pool.

Part of the SMS stack

Twilio SMS is one of the providers behind the SMS channel. All providers share the same two-way threading, STOP-keyword DNC and quiet-hours enforcement.

Explore the SMS feature