Skip to main content
Send SMS texts a customer from an automation. Find it in the step list under Twilio. The step does not talk to Twilio by itself. It hands the text to your brand’s SMS settings, which run the compliance checks (STOP list, quiet hours, consent, state rules) and then send it from one of your senders in Settings -> SMS. Set those up first: see SMS compliance.

The fields

Marketing or transactional

Pick Marketing for anything promotional: offers, cart reminders, win-backs. Pick Transactional only for texts the person needs, like a shipping update. A transactional text with promotional words in it gets a content warning.

What the step returns

The step finishes with the result of the checks, and the run goes on to the next step in every case: A skipped text is not a failure. See Why a text was skipped. A retried run never texts the same person twice for the same step and event. A test run in the builder asks the checks for their answer and sends nothing.

Example: cart reminder

Trigger: a cart abandon. Step: Send SMS with Phone number {trigger.customer_phone}, Type Marketing and a message such as:
Start the text with your brand name and end it with how to opt out. Use your own domain for the link: public shorteners like bit.ly get a content warning, and carriers often filter them.
  • SMS compliance: the checks, senders, suppression list and SMS log
  • Twilio: connect the account your texts go out from
  • Variables: insert values from the trigger and earlier steps
  • Run history: see what each run did