Send from the portal
Pick a channel, write the message, send. No integration needed to get your first one out.
SDMP
One platform for every message you send
From a single OTP to a campaign of millions — sent from your browser or from your codebase, on carrier-grade infrastructure and one clean API.
01–06
Start in the browser. Finish in your code.
The portal and the API are the same platform, so nothing gets rebuilt when you outgrow the screen.
One REST API
A single, well-documented endpoint for every channel. First message in minutes.
Bind over SMPP
Submit at volume over a persistent bind, with delivery receipts on the same session.
Small-batch send
Paste or upload a recipient list, preview every row, and see exactly which ones failed.
Templates
Manage your WhatsApp templates and submit them for approval without leaving the portal.
A composer that knows the channel
It offers only what the channel can actually carry, so you find that out before you send, not after.
07–10
One thread per person, not per phone number
However someone reaches you, it lands in the same place, with everything that came before it.
-
07
One inbox, grouped by person
Not by number and not by channel. One thread per customer, however they got in touch.
-
08
Reply on any channel
They message on WhatsApp and ask for the invoice by email. Answer where it makes sense, in the same thread.
-
09
Session windows, handled
It knows when a WhatsApp window is open and picks free-form or template accordingly. Fewer rejections, lower cost.
-
10
Automatic channel fallback
Unreachable on RCS, delivered on SMS, without you writing the retry.
11–13
Your contacts, your fields
Bring the audience you already have, and describe it the way your business does.
11
Contacts with your own fields
Custom attributes on every contact, defined by you rather than by us.
12
Lists and tags
Segment the way you actually work. A list feeds straight into a campaign.
13
CSV import
Bring thousands of contacts in at once, with validation on every row.
14–17
See exactly what your messaging is doing
Every number on the page traces back to a message you can open.
14
Dashboard
Volume, delivery rate, spend and what needs your attention, on one screen the moment you sign in.
15
Message tracking
Every message you have sent, filterable, with its full journey — accepted, priced, routed, dispatched, delivered — and the reason when it was not.
16
Saved views
Build the view once, bookmark it, send the link to a colleague.
17
Export to CSV
Any report or message list, out to your finance or ops team in the format they already work in.
18–21
Set it running, then watch it work
The repetitive sending, and the conversations that follow from it, without a cron job of your own.
Campaigns
Bulk send paced to your throughput, with live progress and per-recipient status.
Scheduling and retries
Send at a time, on a repeat, and retry the failures that are worth retrying.
Workflows
Build a flow in the portal: send, wait for the reply, branch on it, call your own API.
One-call verification
Trigger an OTP flow and get the outcome back on the same request.
22–25
Built to be plugged into
The parts you only notice when they are missing: credentials you control, and callbacks you can debug.
22
Your own API tokens
Issue them, scope them, revoke them. No support ticket in the loop.
23
Webhooks that hold up
Signed, retried on a fixed ladder, parked when your endpoint goes down, and switched back on by you.
24
A delivery log you can act on
Every attempt, with its status, latency and the response we got back. Replay any delivery.
25
Rotate a secret without downtime
Both signatures go out during the changeover, so nothing breaks mid-swap.
curl -X POST https://api.sdmp.io/v1/messages \ -H "Authorization: Bearer $API_KEY" \ -H "Content-Type: application/json" \ -d '{ "channel": "whatsapp", "to": "+447700900123", "text": "Your order has shipped." }' # → { "id": "msg_9f2", "status": "accepted" }
26–29
Know what you are spending while you spend it
The numbers finance asks for, without a support ticket and without a spreadsheet.
26
Spend, as it happens
Current-period spend split by channel, message type and session window. Not a surprise at month end.
27
Invoices
Every invoice with its line items, grouped the way you need to read them.
28
Traffic and delivery reports
Volume and delivery rate over time, by channel, status and network.
29
Billed for what was sent
SMS segments are counted by the same rule that splits them on the wire, so the invoice matches the traffic.
30–36
The controls that keep you out of trouble
Consent, protection and compliance, in your hands rather than ours.
Opt-outs, honoured everywhere
One suppression list across every channel, enforced before anything leaves the platform.
Sender IDs
What is provisioned, its status per country, and a way to ask for more.
Your connections
Which channels are live for you, how healthy they are, and the throughput you have.
Traffic protection
Spots pumping, fraud and unusual spend on your account — and can stop it.
Alerts
Campaign finished, credit running low, traffic spiking. In the portal, by webhook or by email.
GDPR tools
Erase a message's content, or a person entirely, yourself.
Audit log
Who did what, and when. Sign-ins, tokens, settings changes, erasures.
Six channels, one integration
SMS
WhatsApp
Viber
RCS
Push
Email
One account, one API and one inbox across all of them. Add a channel without adding an integration.
Everything above is a highlight rather than the whole of it. Tell us what you need to do and we will show you the part of the platform that does it.