Where it breaks today
Mass messaging with no way to answer
Blast tools report deliveries and clicks, then drop every reply into an inbox nobody staffs.
A recipient who wants to talk has to find a phone number somewhere else, and most do not bother.
Opt-outs live in the messaging tool, so the dialler keeps calling people who asked you to stop.
Attribution stops at the click, so nobody can show which campaign produced which conversation.
How whtapis runs it
What this team gets
Template library
Approved WhatsApp templates with variables, media and buttons, versioned per market and language.
Click-to-call back
A call button in the message that drops the recipient into your queue over WhatsApp voice.
Progressive dialler
Outbound voice over your own DIDs or ours, with answering-machine detection and retry rules.
Consent ledger
One opt-out record honoured by WhatsApp, SMS and the dialler simultaneously.
A/B on copy and channel
Split the segment by template, send window or channel order, and read the result per arm.
AI first response
An AI agent answers the first reply instantly and hands warm conversations to people.
Reported per campaign
Sends, reads, replies, calls, conversions
Reported per segment
Response rate and cost per conversation
Compliance
Opt-out latency and template approval status
The measures the platform reports on. Targets are set with you during onboarding.
The team using it
Campaign managers, and the agents who answer.
A campaign that invites a reply needs someone on the other end. Both roles work in the same console.
Placeholder frames — drop your own photographs in.
Other use cases