Channel
The official Cloud API, your own number, one shared inbox
Connect your existing WhatsApp Business number through Meta's official Cloud API and answer it from a shared inbox — with templates, delivery receipts, and an assistant that can reply on its own inside the limits you set.
- Keep your existing business number
- The only channel with approved message templates
- One customer, one contact — enforced by the database
- Captures the ad a lead came from, on the first message
We reply in under an hourOr message us on WhatsApp
A screenshot of the running product. The names and numbers are invented; the software is not.
01 / 05
The official API, not a phone in a drawer
This is Meta's WhatsApp Cloud API. Your business keeps its number, your account stays inside Meta's policies, and nothing depends on a handset staying charged and logged in on a desk somewhere. Access tokens are encrypted at rest with AES-256-GCM, and every inbound webhook is verified against its raw bytes before a single row is written.
- Your existing WhatsApp Business number, migrated rather than replaced
- Tokens encrypted at rest; nothing readable sits in the database
- Webhook signatures checked on the raw payload, not the parsed one
02 / 05
The 24-hour window, and the one way past it
WhatsApp lets you reply freely for 24 hours after a customer's last message. After that the window closes and only an approved template will send. This is the single rule that catches businesses out, so the product handles it rather than explaining it: the composer knows which state a conversation is in, and a review request sent out of window falls back to a template automatically instead of silently failing.
03 / 05
Templates, from submission to delivery
Create a template, submit it to Meta for approval, and watch its status change without leaving the app. Variables are checked before sending, so a template does not fail at the last hop because a placeholder had no value. This is the only channel where templates exist at all — Messenger and Instagram have no equivalent, which is why broadcasts are WhatsApp-only.
- Submit and track approval status in the app
- Variables validated before the send, not after it fails
- Per-recipient delivery ladder: sent, delivered, read, replied
04 / 05
One customer, one record
A message from a number you already have resolves to that contact rather than creating a second one — and that is enforced by a unique index in the database, not by code that has to remember. The same holds for contacts you import from a CSV, add by hand, or who book through your public booking page.
05 / 05
Ads that start conversations, measured properly
When someone taps a Click-to-WhatsApp ad, Meta attaches the click id to their first message and never sends it again. That single delivery is captured and frozen against the contact, so when the deal closes months later the conversion can be reported back to the ad that caused it — and Meta optimises for buyers instead of clicks.
Questions
WhatsApp, specifically
What runs on this channel
The capability behind it, and the scenarios that name it explicitly.
- FeatureOmnichannel messagingFive channels, one conversation history
- Use caseThe enquiry that arrives at 11pmAnswered now, not at nine tomorrow
- Use caseThe 3am rescheduleMoved, confirmed, and nobody was awake
- Use caseThe voice note in Urdu at midnightIt listens, understands, and can reply the same way
- Use caseThe customer who sends a photoIt looks, describes, and routes it to the right person
- Use caseQualifying before anyone picks upThe three questions you always ask, always asked
Ready to answer every customer in one place?
Bring WhatsApp, Messenger and Instagram together with AI that actually helps. Talk to us and we'll get you set up.
We reply in under an hourOr message us on WhatsApp