Integrations
Copy page
Connect 23 Telecom to the tools where you build customer journeys. Each guide below shows who configures the connection, what to prepare, exactly where to click, and how to send a safe test before you go live.
Two things are always kept separate on every page, because they are not the same event:
- Accepted — 23 Telecom queued the message. It is not proof of delivery.
- Delivered — the carrier confirmed handset delivery (a later DLR).
Where a platform can show carrier delivery in its own UI, the table says so. Otherwise, check delivery in Message status and Statistics inside 23 Telecom.
iGaming platforms
Section titled “iGaming platforms”| Platform | Setup | Delivery reporting | Availability | Guide |
|---|---|---|---|---|
| Fast Track | Native · managed | In Fast Track | Available | Open guide |
| Optimove | Native · managed rollout | Defined during rollout | Integration programme | Open guide |
| Xtremepush | Webhook · self-service | In 23 Telecom | Managed activation | Open guide |
| Smartico | Native · guided | Confirmed during onboarding | Guided setup | Open guide |
| Symplify | Guided setup | Project-specific | Guided setup | Open guide |
Customer engagement & CRM
Section titled “Customer engagement & CRM”| Platform | Setup | Delivery reporting | Availability | Guide |
|---|---|---|---|---|
| Customer.io | Webhook · self-service | In 23 Telecom | Managed activation | Open guide |
| Braze | Webhook · self-service | In 23 Telecom | Managed activation | Open guide |
| Iterable | Webhook · self-service | In 23 Telecom | Managed activation | Open guide |
| Klaviyo | Webhook · guided activation | In 23 Telecom | Managed activation | Open guide |
| HubSpot | Custom code · technical admin | In 23 Telecom | Managed activation | Open guide |
| Salesforce Marketing Cloud | Managed custom activity | Defined during rollout | Integration programme | Open guide |
| Adobe Journey Optimizer | Custom action · technical admin | In 23 Telecom | Managed activation | Open guide |
| MoEngage | Custom connector · guided | Project-specific | Guided setup | Open guide |
| WebEngage | Call API · self-service | In 23 Telecom | Managed activation | Open guide |
| CleverTap | Generic SMS · self-service | In 23 Telecom | Managed activation | Open guide |
Customer.io is our recommended first CRM connection: its reusable webhook keeps credentials protected and uses Customer.io’s automatic retry key. You can configure and test it immediately in sandbox; 23 Telecom then enables production for your workspace and completes a short launch check with your team.
What the setup types mean
Section titled “What the setup types mean”- Native / custom integration — 23 Telecom is configured directly as the provider or delivered through a dedicated platform adapter. Self-service means you configure it yourself; managed means the teams handle credentials and callbacks for you.
- Webhook / Call API / Custom code — the platform calls the 23 Telecom API from a campaign, flow or journey step. Where the platform exposes the response body, you can read the API response there; carrier delivery reports stay in 23 Telecom unless a page says otherwise.
- Guided setup — 23 Telecom coordinates the provider credentials and platform configuration with your team.
What availability means
Section titled “What availability means”The Availability column shows how each connection is launched:
- Available — ready to activate today, either directly or with the platform teams.
- Managed activation — configure and test in sandbox, then your 23 Telecom account manager enables production and completes a short launch check covering retry safety, sender IDs and account throughput.
- Guided setup — our team handles the tenant-specific provider configuration and secure credential exchange with you.
- Integration programme — a platform-specific adapter delivered through a scoped rollout. Contact us to confirm the onboarding plan for your brand; live sending begins after adapter release and tenant activation.
Before you connect
Section titled “Before you connect”Every guide assumes you already have:
- an active workspace (see Workspaces);
- an approved sender ID for your destination countries (see Sender IDs);
- a test phone number in E.164 format, e.g.
+447911123456.
Self-service guides only (the webhook, Call API and custom-code pages) also
need a 23 Telecom API key with just the sms.send permission — create a
separate key per platform (see API keys & permissions). Start with a
sandbox sk_test_ key (see Sandbox & test mode) and switch to a
restricted sk_prod_ key as part of managed production activation. Managed,
guided and integration-programme pages (Fast Track, Optimove, Symplify, Smartico,
Salesforce Marketing Cloud, MoEngage) don’t need a key from this documentation —
the teams exchange credentials for you.