Twilio SMS Notifications

Twilio SMS notifications send one operational text message to one fixed admin-configured recipient after a successful form submission.

Scope

This is an admin-notification integration, not submitter SMS.

• one SMS per successful submission;
• one fixed recipient number configured by the admin;
• no visitor-controlled phone target;
• no campaign, inbound SMS, MMS, or delivery-callback workflow.

That narrower scope keeps the feature useful for operational alerts without turning a form into a general-purpose SMS sender.

Configure it

1. Open Form Settings → Integrations.
2. Open Twilio SMS notification.
3. Choose the Twilio region matching the API key you created: us1, ie1, or au1.
4. Add Account SID, API Key SID, and API Key Secret.
5. Choose a sender mode:
   • Twilio phone number, or
   • Messaging Service SID.
6. Enter the fixed recipient number in E.164 format, for example +38970123456.
7. Write the SMS template and save.

Message templates

The message body supports:

• {{form_title}}
• &#123;&#123;field:<name>&#125;&#125;

Templates are plain text and capped to keep operational alerts compact. submission_json is intentionally unsupported.

Security and delivery

• API key secrets are encrypted at rest and write-only in the UI.
• Dispatch runs through the normal async integration queue so the visitor does not wait on Twilio latency.
• Local misconfiguration logs a warning and skips dispatch; transient remote failures can be retried by the queue.
• Phone numbers must be entered in exact E.164 format. The component does not silently rewrite spaces or punctuation.

Downgrade behavior

Existing Pro-authored Twilio config is preserved after downgrade and can continue dispatching if it was already active. New activation on Free is blocked.