# Connect 23 Telecom to Salesforce Marketing Cloud

> Connect 23 Telecom to Salesforce Marketing Cloud Journey Builder through a managed custom-activity rollout scoped for your Business Unit.
> Source: https://docs.23telecom.co.uk/integrations/salesforce-marketing-cloud/
> Activation: Integration programme

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** | Managed custom activity |
| **Setup time** | Scoped with your managers |
| **Sends SMS** | Managed rollout — contact us |
| **Delivery status in Marketing Cloud** | Defined during rollout |
| **Who can configure** | Marketing Cloud admin + 23 Telecom |

  The 23 Telecom Journey Builder connection is available as a managed integration
  project. [Contact us](https://23telecom.co.uk/contact) to scope your Business
  Unit, sender IDs, markets, throughput and delivery reporting. Live sending
  begins after custom-activity release and tenant activation.

## What this connection does

The production design is a secure 23 Telecom **Journey Builder custom activity**
delivered as an installed package. 23 Telecom provides a managed integration
programme that scopes the Business Unit, hosted activity, credentials and
delivery-report mapping, then coordinates rollout with your Marketing Cloud team.

## Before you start

Prepare your **Business Unit**, Journey Builder environment, the data
extension / contact key and phone field, [approved sender IDs](https://docs.23telecom.co.uk/sms/sender-id),
markets, expected throughput and your DLR requirement. You'll also want an
[active workspace](https://docs.23telecom.co.uk/account/workspaces).

## Connect 23 Telecom

1. Ask your **23 Telecom account manager** and your **Marketing Cloud admin** to
   scope the managed rollout:

   > We'd like to activate 23 Telecom for SMS in Journey Builder. Please scope our
   > Business Unit and share the onboarding plan and rollout timeline.

2. Share the Business Unit, phone field, sender IDs, markets and throughput — not
   credentials.

3. Once the rollout slot is confirmed, the teams configure the custom activity
   and run a tenant test. Live traffic starts after activity release and tenant
   activation.

  The complete integration is a separate product: a hosted configuration UI
  (`config.json`, `customActivity.js`, Postmonger), a server-side execute
  endpoint, Salesforce signature validation, server-only key storage, idempotency
  per execution, delivery-report mapping into a Data Extension or Salesforce
  event, Installed Package registration and tenant UAT. During rollout, the teams
  add it via **Setup → Apps → Installed Packages → Add Component → Journey
  Builder Activity**, then place the 23 Telecom tile in the test journey.

## Verify the result

**Accepted** means queued; **delivered** is the later carrier report. During
rollout, delivery is confirmed in 23 Telecom [Message status](https://docs.23telecom.co.uk/sms/status) or
[Statistics](https://docs.23telecom.co.uk/sms/statistics). The Marketing Cloud delivery mapping is included
when agreed in the rollout scope and enabled after custom-activity release and
tenant activation.

## Need help?

- **Journey Builder / Marketing Cloud** — Salesforce support and your admin.
- **Activity rollout, sender IDs, delivery** — your 23 Telecom account manager, or
  the [contact form](https://23telecom.co.uk/contact).

## Official platform documentation

- [Build custom activities](https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/creating-activities.html)
- [Custom activity configuration](https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/custom-activity-config.html)
- [Register an endpoint](https://developer.salesforce.com/docs/marketing/marketing-cloud/guide/define-jb-extension-app-center.html)

*Last verified: 16 July 2026.*