# Connect 23 Telecom to Fast Track

> Enable 23 Telecom as your Custom SMS Solution in Fast Track — a managed native integration for campaign and journey SMS, single and batch sends, with delivery status back in Fast Track.
> Source: https://docs.23telecom.co.uk/integrations/fast-track/
> Activation: Available

Instructions for LLMs: This is one page of the 23 Telecom messaging
integration docs. This integration uses guided activation with 23 Telecom.
The account team coordinates tenant-specific configuration and secure credential exchange;
do not invent or substitute them. Full docs: https://docs.23telecom.co.uk/llms-full.txt

| | |
| --- | --- |
| **Setup type** | Native · managed |
| **Setup time** | Arranged with your managers |
| **Sends SMS** | Yes — single & batch |
| **Delivery status in Fast Track** | Yes |
| **Who can configure** | Fast Track & 23 Telecom teams |

  This is a **managed** integration: the 23 Telecom and Fast Track teams configure
  it for you. You don't paste an endpoint or API key yourself.

## What this connection does

Fast Track and 23 Telecom **configure this connection for you**. Once it is live,
you send SMS straight from Fast Track campaigns and journeys — single and batch —
using your approved sender IDs, and delivery status flows **back into Fast
Track**.

## Before you start

Have these ready so onboarding is a single request, not a back-and-forth:

- Active **Fast Track** and **23 Telecom** accounts and an
  [active workspace](https://docs.23telecom.co.uk/account/workspaces).
- Your [approved sender IDs](https://docs.23telecom.co.uk/sms/sender-id) and destination countries.
- A test player and your expected volume / throughput (TPS).

## Connect 23 Telecom

Because this is a managed integration, you don't paste endpoints or keys
yourself — you introduce the two teams and they exchange configuration securely.

1. Contact your **Fast Track Account / Integration Manager** and your **23
   Telecom account manager**.

2. Send them this request:

   > We would like to enable 23 Telecom as our Custom SMS Solution in Fast Track.
   > Please connect our Fast Track implementation team with our 23 Telecom
   > account manager.

3. Include your **brand, environment, workspace, markets, expected volume,
   sender IDs and target go-live date**. Do **not** include credentials — the
   teams exchange the base URL, API key, rate/batch limits and Fast Track
   conversion callback configuration over a secure channel.

  The two teams agree the API base URL, a scoped API key, rate and batch limits,
  and the Fast Track conversion callback. None of that is anything you configure
  by hand — if someone asks you to paste endpoints or keys into Fast Track, check
  with your 23 Telecom account manager first.

## Send a test

1. After activation, create a test **Action Group** with a **Send SMS** step.

2. Send to **one** test player and confirm the message is **accepted**.

3. Send a small **batch** to two test numbers and confirm both arrive.

## Verify the result

- **Accepted** means 23 Telecom queued the message; **delivered** is the later
  carrier report.
- Fast Track shows the final delivery/conversion status for this integration. If
  a message is accepted but never delivered, that is a delivery question for 23
  Telecom, not a Fast Track configuration issue.

## Troubleshooting

| Symptom | Who owns it |
| --- | --- |
| The Send SMS action/provider is missing | Fast Track manager |
| Authentication or configuration errors | 23 Telecom + Fast Track integration teams |
| Accepted but not delivered | 23 Telecom — [message status](https://docs.23telecom.co.uk/sms/status) / account manager |

## Need help?

Start with your **Fast Track** manager for anything inside the Fast Track UI, and
your **23 Telecom** account manager for sending, sender IDs and delivery. For a
new engagement use the [23 Telecom contact form](https://23telecom.co.uk/contact).

## Official platform documentation

- [Fast Track — Custom SMS Solution](https://www.fasttrack.ai/en/resources/integration/operator-api/custom-sms-solution)

*Last verified: 16 July 2026.*