Using SMS In Flows
Send automated SMS messages to clients and members with the Twilio SMS flow node.
Twilio SMS is primarily used through Flows (automation). You add a Twilio SMS action node to a flow, choose who the SMS should go to, and write the message using template variables.
Fast answer
Flows → create/edit a flow → add a Twilio SMS node.
Where Do I See If The SMS Was Sent?
Open the related booking/consultation → Flow Logs.
Flow logs show what the Twilio node tried to do, who it sent to, and any error returned by Twilio.
Delivery vs sent
TatTool logs sent when Twilio accepts the message. Carrier “delivered” status is not currently tracked inside TatTool.
Add A Twilio SMS Node
- Open Flows
- Create or edit a flow
- Add an action node: Twilio SMS
- Choose a recipient
- Write the message
Recipients (And Phone Numbers)
SMS can only be sent if the chosen recipient has a phone number saved in TatTool.
Typical recipients:
- Client (the booking’s client)
- Participant (usually the artist assigned to the booking/consultation)
Recipient limitations (important)
Some triggers show recipients like Admins or Organizer, but Twilio SMS works best when sending to Client or Participant.
If the selected recipient type has no phone number available, the node will fail with “No phone number found…”.
Message Content
- Phone numbers should be E.164 format (example:
+14155552671) - TatTool validates messages up to 1600 characters, but SMS is often billed/delivered in ~160-character segments
- Use template variables for links and booking info
Template Variables (Recommended)
You can use variables like:
{{client_name}}{{event_start}}{{event_end}}{{event_location}}{{payment_link}}(payment request flows){{consent_form_link}}(consent form flows)
Examples:
- Booking reminder:
Hi {{client_name}} — reminder: {{event_start}} at {{event_location}}. - Payment link:
Hi {{client_name}} — your payment link: {{payment_link}} - Consent form:
Hi {{client_name}} — please fill out your consent form: {{consent_form_link}}