SMS that can actually hear the word STOP.

What the Twilio integration actually does

You save your Twilio Account SID, Auth Token and sender number into your workspace. Creaiter checks those credentials against Twilio's own API before claiming they work, and stores the Auth Token in a secrets vault rather than anywhere it can be read back into a browser.

Connecting also sets the inbound webhook on your Twilio number, which is the piece almost everyone forgets. Without it, Twilio has nowhere to deliver a customer's reply, and the entire opt-out chain sits there fully built and never firing. Creaiter wires it during the connection, and if it cannot, it shows you the exact URL to paste into the Twilio console yourself.

• Outbound SMS sent through your own Twilio account and number
• Credentials checked against Twilio before the connection is called verified
• The Auth Token is stored in a secrets vault and never returned to the browser
• The inbound reply webhook is set on your Twilio number during connection
• STOP and other opt-out keywords are recorded in a ledger
• Every send is checked against that ledger before a message goes out
• Delivery outcomes are recorded, so a failure is visible rather than assumed

How to connect Twilio

The setup lives in your workspace settings and is restricted to workspace owners and admins, because this is the connection that spends money and speaks to real customers.

• Create a Twilio account and buy a number capable of SMS in the countries you send to
• Complete whatever carrier registration Twilio requires for your country and use case
• Copy your Account SID and Auth Token from the Twilio console home page
• In Creaiter, open Settings, then Integrations, then the Twilio card
• Paste the Account SID, the Auth Token, and your sender number in full international format such as plus one four one five five five five one two three four
• Save, and read the result, which tells you whether the credentials verified and whether the reply webhook was wired

Saved and verified are different words here

If Twilio accepts your credentials, the connection is marked verified. If it does not, the credentials are still saved but the connection reads as saved and not verified, with the reason attached. A typo in an Auth Token and a temporary Twilio outage produce different messages, because they need different responses from you.

The same honesty applies to the reply path. There are legitimate setups where the webhook cannot be set automatically, such as a number owned by a different Twilio subaccount or a sender pool. In those cases Creaiter does not quietly show a green badge. It says the webhook is not wired, explains why, and gives you the URL to configure by hand.

One consequence worth knowing before you plan around it: a Twilio account can be verified on one Creaiter workspace at a time. If you run two workspaces on one Twilio account, there is nothing in an incoming message that says which workspace it belongs to, and delivering a client's replies to the wrong tenant would be much worse than a limitation you can read about here.

What day to day looks like

You describe the message in the chat and confirm the send. Creaiter checks the recipients against the opt-out ledger, sends the ones that are still eligible through your Twilio account, and records what happened to each one.

When someone replies STOP, Twilio delivers that reply to the webhook set during connection, and the opt-out is written to the ledger. The next campaign never reaches them, without anyone having to remember to remove them by hand.

What the Twilio integration does not do

The limits, including the ones that cost money.

• It does not give you a Twilio account or a phone number. You bring both
• It does not bill you for messages. Twilio charges you per message segment, directly, at their rates, and a long message is more than one segment
• It does not complete carrier registration for you. Number provisioning and registration happen in Twilio
• It does not verify a Twilio account on two Creaiter workspaces at once, for the routing reason described above
• It does not guarantee delivery. Carriers filter, and Creaiter reports what Twilio reports rather than assuming success
• It does not run paid advertising, it is not a sales CRM, and it does no backlink auditing