WhatsApp and SMS are where buyers actually reply. Both run on the same thread as the call, with templates registered before a single send and delivery visible per message rather than per campaign.
WhatsApp Business API · DLT registered · Consent state on the contact
Template out, free-form back. Inside the session window a reply is just a message; outside it the right template goes out on its own. A rep should never have to work out which of those they are in before they can answer somebody.
An unregistered sender ID does not fail loudly. It fails at the carrier, hours later, as a delivery report nobody reads. Sender IDs, headers and templates are registered up front, and the ones still pending are visible rather than assumed.
Sent, delivered, read and failed, per recipient rather than per campaign.
An opt-out is recorded once and respected on every channel afterwards.
Quiet hours and regional rules applied before anything leaves the queue.
Every message threaded onto the contact your reports already use.
Either works. We can provision one during onboarding, or connect the account you already have if you would rather keep that relationship direct.
An approved template goes out instead of a free-form message, and the platform picks it rather than making a rep remember the rule. Once they reply, the window opens and normal messages resume.
We file the headers and the content templates. The principal entity registration has to be in your own name — that is the regulator's requirement rather than ours — and we walk you through it once.
Meta and carrier fees are billed at cost and itemised. The platform fee is per user and does not change with how many channels you switch on.
No. The same rule as voice: only approved plays run, and the channel changes the format rather than the approval requirement.
AI communication platform that connects your calls, learns what wins, and runs across your channels.
sales@hyperdial.io