Connect 23 Telecom to Salesforce Marketing Cloud
Copy page
| 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 |
What this connection does
Section titled “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
Section titled “Before you start”Prepare your Business Unit, Journey Builder environment, the data extension / contact key and phone field, approved sender IDs, markets, expected throughput and your DLR requirement. You’ll also want an active workspace.
Connect 23 Telecom
Section titled “Connect 23 Telecom”-
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.
-
Share the Business Unit, phone field, sender IDs, markets and throughput — not credentials.
-
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.
Verify the result
Section titled “Verify the result”Accepted means queued; delivered is the later carrier report. During rollout, delivery is confirmed in 23 Telecom Message status or 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?
Section titled “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.
Official platform documentation
Section titled “Official platform documentation”Last verified: 16 July 2026.