Vague WhatsApp
The 24-hour window, handled.
Meta gives you 24 hours to reply free-form. The composer counts down every conversation and swaps in an approved template the second the window shuts.
WhatsApp tools fall over in two places: the service window and template approvals. Those are the two WhatsApp was built around.
- A live countdown on every conversation
- Templates built, previewed and submitted to Meta in one screen
- Quality scores and rejection reasons in plain sight
- Campaign funnels down to the single message
A live countdown on every conversation
Templates built, previewed and submitted to Meta in one screen
Quality scores and rejection reasons in plain sight
Campaign funnels down to the single message
In detail
What WhatsApp does.
Capabilities that exist today.
The service window
A countdown, not a surprise.
Meta's rule is strict: 24 hours after the customer's last message, free text stops being deliverable. Most tools let your team type the reply anyway and watch it silently die. Here every conversation carries a live countdown. When the window closes, the composer blocks the dead send and offers your approved templates instead, so the message that leaves is one that arrives.
- A live countdown on every open conversation
- Free text blocked the moment the window closes
- Approved templates offered in its place
- Zero messages silently rejected by Meta
Templates
Approval without the spreadsheet.
Somewhere right now a team is tracking template approvals in a spreadsheet named final_v3. Here you build the template with header, body, footer and buttons, watch it render exactly as the customer will see it, and submit it to Meta from the same screen. Approved, pending and rejected states sync back, rejections arrive with Meta's reason attached, and the quality score sits alongside, green through red, before a pause catches you off guard.
- A live WhatsApp-style preview while you build
- Submit to Meta and sync status without leaving the product
- Rejection reasons surfaced where you can fix them
- Quality score per template, green through red
- Variables mapped to lead fields
Your visit tomorrow
Hi Arlene, confirming 10:30 at the Marina office.
Confirm · Reschedule
Campaigns
A thousand sends, one funnel.
Filter the audience on your own lead fields, for example city, source, or last response, and send an approved template to all of them. Delivery, reads and replies funnel down message by message, so a campaign is a graph you can read rather than a number you hope about. If it is going sideways, cancel it while that still matters.
- Audience filters on your own lead fields
- A delivery funnel with per-message detail
- Cancel a campaign that is still running
- An automatic welcome message on first contact
Better together
WhatsApp works with the rest.
Everything writes to the same customer record, so adding a second product does not mean a second migration.
A pipeline that fills itself.
See DataReplies that draft themselves.
See EmailThe whole suite
One login, one record, one bill.
Questions
WhatsApp, specifically.
Two places. The service window is enforced in the composer rather than left to your team to remember, and template rejections surface with Meta's reason attached instead of failing quietly.
Yes. Templates are submitted to Meta from inside the product, against your own number.
Meta rates your templates green, yellow or red based on how recipients react. A red score gets templates paused, so we surface it where your team will see it.
Yes, over sockets, so two people are never replying to the same conversation blind.
See WhatsApp on your own data.
Thirty minutes, your records, no slides.