Connect 23 Telecom to Optimove

Setup type	Native · managed
Setup time	Scoped with your managers
Sends SMS	Managed rollout — contact us
Delivery status in Optimove	Defined during rollout
Who can configure	Optimove admin + both teams

Status: Integration programme

The 23 Telecom Optimove connection is available as a managed integration project. Contact us to scope your tenant, sender IDs, markets, throughput and delivery reporting. Live sending begins after adapter release and tenant activation.

What this connection does

Optimove provides an official, public SMS Aggregator API (the “OptiText” vendor protocol). 23 Telecom delivers the connection through a managed integration programme: our teams scope the tenant, adapter, security model and delivery-report mapping, then coordinate rollout with Optimove.

Before you start

Prepare so onboarding is one request:

• Your Optimove tenant / brand, an active workspace, approved sender IDs, markets and expected volume / TPS.
• A test audience and whether you need inbound replies.
• Whether you want scheduled, triggered / real-time, or both.

Connect 23 Telecom

1. Tell your Optimove Customer Success Manager and your 23 Telecom account manager that you want to activate the managed 23 Telecom SMS Aggregator connection:

   We’d like to activate 23 Telecom for Optimove SMS. Please scope our brand and share the onboarding plan and rollout timeline.

2. Share your tenant/brand, markets, sender IDs, volume/TPS and execution mode — not credentials — so we can scope your brand.

3. Once the rollout slot is confirmed, the teams configure the connection and run a test campaign together. Live traffic starts after adapter release and tenant activation.

Keep the Secret Key off email and tickets

Optimove shows its aggregator Secret Key once. Never send it in a normal email or support ticket — the teams agree a secure channel. You never paste 23 Telecom endpoints or keys into Optimove yourself; the connection is managed.

How it works

Under the hood the Optimove SMS Aggregator protocol uses a tenant Base URL, an API Token and a one-time Secret Key, an aggregator handshake, HMAC-SHA256 over the raw body, batched campaign transmission, retries on 429/5xx/network failures, and delivery reports (Delivered, Failed, Unknown). During the managed rollout, 23 Telecom implements and operates that adapter while your Optimove admin retains the platform credentials.

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 Optimove delivery-report path is included when agreed in the rollout scope and enabled after adapter release and tenant activation.

Need help?

• Optimove SMS configuration — your Optimove CSM.
• Adapter status, sender IDs, delivery — your 23 Telecom account manager, or the contact form.

Official platform documentation

• SMS Aggregator API
• Handshake endpoint
• Campaign transmission webhook
• Delivery report endpoint

Last verified: 16 July 2026.