Cadence sends SMS using a provider configuration your staff add under SMS settings. Today this is Twilio with your organisation’s own account credentials. You can save multiple named configurations (for example sandbox vs production), but only one is active for outbound SMS at a time. Your Twilio auth token is stored encrypted, and only staff with the appropriate permissions can create, update, or switch the active configuration. Additional SMS providers may be offered over time while keeping the same pattern (pick a provider, name the configuration, activate one).
Sender configuration
Section titled “Sender configuration”You need to configure one of the following in Cadence to send SMS:
- A Twilio Messaging Service (starts with
MG) - recommended if you’re using number pools, sticky sender, or other Twilio features. - A specific phone number in the format your country requires (for Australia, this is
+61followed by the number without the leading zero - for example,+61400000000).
Security
Section titled “Security”- Treat your Twilio auth token like a password. If it’s ever exposed, rotate it in the Twilio Console immediately and update Cadence with the new token.
- Where possible, use a dedicated Twilio subaccount rather than your main account credentials.