# Connect 23 Telecom to MoEngage

> Add 23 Telecom as a custom SMS connector in MoEngage through guided activation covering request mapping, delivery callbacks and a launch test.
> Source: https://docs.23telecom.co.uk/integrations/moengage/
> Activation: Guided setup

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** | Custom connector · guided |
| **Setup time** | Arranged with your managers |
| **Sends SMS** | Yes — after guided activation |
| **Delivery status in MoEngage** | Project-specific |
| **Who can configure** | MoEngage admin + 23 Telecom |

  Your 23 Telecom account manager configures the custom connector with you and
  confirms the tenant-specific request, response and delivery mapping before
  launch. No API credential is exposed on this page.

## What this connection does

MoEngage supports a **custom SMS connector**. In a short activation session, 23
Telecom confirms the exact request, response and delivery-callback mapping for
your tenant, then completes the launch test with your team.

## Before you start

Prepare your MoEngage account, an [active workspace](https://docs.23telecom.co.uk/account/workspaces),
[approved sender IDs](https://docs.23telecom.co.uk/sms/sender-id), markets, expected volume and a test
number. The connector lives under **Settings → Channels → SMS → Sender
Configuration → Add Sender → Add custom service provider**.

## Connect 23 Telecom

1. Ask your **23 Telecom account manager** to schedule the connector activation:

   > We'd like to activate 23 Telecom as our custom SMS connector in MoEngage.
   > Please schedule the configuration and launch test for our tenant.

2. Share your sender IDs, markets, volume and a test number — not credentials.

3. During activation, the teams configure the custom provider, confirm the
   mapping and send a test.

  The activation session verifies the `POST` request and
  API-key header, JSON vs raw body behavior, the `Moesms_destination` /
  `Moesms_message` / sender mapping, whether a scalar or nested body is needed,
  a stable idempotency value, parsing the flat `message_id`, the **Send test SMS**
  result, and the **Track sms delivery** callback mapping. Delivery callbacks are
  included when the tenant supports the required correlation mapping; delivery
  status is always available in 23 Telecom.

## Verify the result

**Accepted** means queued; **delivered** is the later carrier report. Confirm
delivery in 23 Telecom [Message status](https://docs.23telecom.co.uk/sms/status) or
[Statistics](https://docs.23telecom.co.uk/sms/statistics). When the tenant supports the required correlation
mapping, the activation also enables the MoEngage delivery callback.

## Need help?

- **Custom connector fields** — MoEngage support.
- **Activation, sender IDs, delivery callback** — your 23 Telecom account manager, or the
  [contact form](https://23telecom.co.uk/contact).

## Official platform documentation

- [Configure a Custom Connector for SMS](https://help.moengage.com/hc/en-us/articles/360061107691-Configure-Custom-Connector-for-SMS)

*Last verified: 16 July 2026.*