Connect approved SMS, WhatsApp and voice workflows.
Confirm the data, permission, owner and evidence needed to achieve this outcome.
Messaging & voiceBeta
Connect SMS, MMS, WhatsApp and voice support through Twilio.
Verify Twilio signatures, track message delivery, enforce consent keywords and turn calls or voicemails into support tickets.
Supported SMS, WhatsApp and voice workflows require provider configuration.
Connection statusBeta
CategoryMessaging & voice
Production ruleTest before enabling
TransparencyReview status definitions Business outcomes
Connect Twilio to accountable customer-support work.
These outcomes describe the intended operating value. They are not fabricated customer results.
Keep provider callbacks and delivery states visible.
Confirm the data, permission, owner and evidence needed to achieve this outcome.
Apply consent, recording and regional controls before launch.
Confirm the data, permission, owner and evidence needed to achieve this outcome.
Operational fit
Understand what the connection needs before enabling it.
Enterprise integration pages should state availability, prerequisites, data exchanged, permissions, failure behavior and operating ownership.
Requirements
Prerequisites and ownership
- Twilio account and sender
- Public HTTPS callbacks
- Consent and recording policy
Supported workflows
What teams can operate
- SMS and MMS
- Twilio WhatsApp
- Delivery callbacks
- Opt-in and opt-out tracking
- Incoming and outbound voice
- Voicemail and recording callbacks
Enterprise implementation
Move through scope, configuration, validation and operation.
A connector is not production-ready because credentials were accepted. Validate behavior, ownership and failure handling.
Scope
Define the business workflow, provider account, data objects, permissions, owners and success criteria.
Configure
Create dedicated credentials, select minimum scopes and connect a non-production HelpoSoft workspace.
Validate
Test normal, duplicate, delayed, failed, revoked and unauthorized events with safe sample data.
Operate
Enable monitoring, rotation, incident ownership, change review and a documented rollback path.
Configuration sequence
Connect, verify and test before production.
Use a non-production workspace, scoped credentials and explicit acceptance tests for normal, duplicate, delayed and failed events.
Create a Twilio or Voice connection
Record the expected result and verify it in a test environment before continuing.
Enter encrypted credentials and sender details
Record the expected result and verify it in a test environment before continuing.
Configure generated webhook URLs
Record the expected result and verify it in a test environment before continuing.
Test inbound messaging or calling
Record the expected result and verify it in a test environment before continuing.
Review delivery/call states inside the ticket
Confirm monitoring, rollback and support ownership before launch.
Data exchanged
Make the data path reviewable.
- Twilio sends message, call and delivery events
- HelpoSoft sends authorized outbound actions
Permissions
Use the minimum access required.
- Validate Twilio signatures
- Keep recording disabled unless approved
Acceptance testingA valid event or request creates the expected HelpoSoft record exactly once. Invalid signatures, expired credentials and unauthorized scopes are rejected without leaking sensitive details. Duplicate and delayed events do not create duplicate customer work or repeat privileged actions. Provider timeouts, throttling and temporary failures enter a visible retry or exception path. Credential revocation stops future access and produces an actionable administrator signal. Customer-facing content contains only approved data and preserves internal/private boundaries.
Prove safe behavior before launch.
Operational monitoringConnection health and last successful operation Authentication or authorization failures Delivery latency, retry count and terminal failures Duplicate or replayed event detection Credential age, ownership and planned rotation Provider quota, rate-limit and policy changes
Keep provider health and failures visible.
Troubleshooting1 2
Resolve connection failures methodically.
Confirm callback URLs
Review sender capability and geo permissions
Known boundariesVerify installed-version status
Do not hide provider or version limits.
No additional limitation has been documented.
Provider policy, eligibility, quotas and the installed HelpoSoft version still apply.
Cloud responsibility
A secure connector has named owners on every side.
Approve service, customer and provider responsibilities before sharing production data or credentials.
Review integration assuranceConnected product areas
Use the integration inside a complete workflow.
Implementation guidance
Related guides and controls.
Integration FAQ
Twilio questions.
Availability and provider eligibility should always be checked against the installed version and provider account.
Yes. Supported Twilio webhooks are validated before events are processed.
No. Recording is disabled by default and should only be enabled with appropriate notice and retention rules.