Telesign
Connect Telesign to SMS — coming soon; Norbix cannot send through Telesign yet.
Telesign offers a global SMS API used for verification and engagement messages.

Get your credentials
Sign in to the Telesign portal.
On the dashboard copy the Customer ID and the API key.
Pick a sender: a number in E.164 format or an alphanumeric name where allowed.
Connect it in Cloud
Where: SMS → Integrations → Add New Integration → Telesign — Connect is turned off for now.
The form exists in Cloud and opens only by its address, /projects/<project>/sms/integrations/new/telesign; it starts with the note Sending SMS through Telesign is not supported yet. An integration saved there (or from code) stays in the integrations list with SENDING NOT SUPPORTED YET, can be edited and deleted, and is not offered on campaigns, trigger actions or template tests.
Customer ID
yes
Names your Telesign account; paired with the API Key.
00000000-0000-0000-0000-000000000000
Sender
yes
The number or alphanumeric name the SMS comes from.
Acme
API Key
yes
Secret; encrypted on save and never shown again.
your-telesign-api-key
Integration Name
yes
The name in your integrations list.
Telesign production

Test and set as default
Test integration answers Test failed with Sending SMS through Telesign is not supported yet. Use Twilio or the Fake provider., and the integration is not offered as a sender, so setting it as default has no use yet. See Test an integration and Set an integration as default for the flow once Telesign goes live.
Common errors
Sending SMS through Telesign is not supported yet. Use Twilio or the Fake provider.
Every send or test through Telesign today.
Use Twilio or Fake SMS (Test Me).
Secret is not provided (CM-ERRORS-SECRETS-001)
An update without the secret fields.
Send every secret again on each save.
Required
An empty field on the form.
Fill every field.
Do it from code
The client setup is on the SMS page. API: Save Sms Integration
Last updated
Was this helpful?