All guides

User guide

WhatsApp Sales — consent and rules

Record consent and decide who may be messaged — before any sending exists.

Screen: /en/account/whatsapp · Counts: opt-ins recorded this month

Read this first

Nothing can be sent from here, and nothing will be until Meta says so.

Sending requires a WhatsApp Business Account, Meta business verification and per-template approval — none of which can be created from code, and none of which AI Gate can grant or hurry.

The WhatsApp screen
The WhatsApp screen

So what is this? It is the half of the problem that is solvable in advance: the evidence and the rules, so that "may we message this person?" already has a tested, auditable answer before any transport is wired. The day Meta approves you, the hard compliance question is already settled.

This product is not on self-service purchase for that reason. Email info@aigate.me if you want it.

May we message them?

Enter a number and optionally a template name. The answer accounts for: a recorded opt-in, any opt-out, whether a 24-hour service window is open from their last inbound message, whether the template is approved, and whether the conversation has been handed to a colleague.

Use it as the gate in your own process today, by hand or through the sync endpoint.

Recording an opt-in

  • Phone number in E.164 form — +962790000011.
  • Consent wording — exactly what the person agreed to.
  • Evidence of consent — where and when, e.g. "Ticked at checkout, 12 Nov 2026".
An opt-in you cannot evidence is not an opt-in. Both fields are required for that reason.

Opt out is permanent and immediate. There is no re-opt-in button: that has to come from the person.

Inbound messages and the 24-hour window

Record a message they sent you opens the 24-hour service window, because that is what an inbound message does under Meta's rules. Record it when it happens, or the gate will give an answer that does not match reality.

Handing to a colleague

Hand it to a colleague stops everything automated for that contact and records who and why. A person has taken over; nothing should be competing with them. Return it to the usual rules reverses it.

Templates and Meta's process

Record each template, its language, body and Meta's decision. This records their decision only — choosing "Approved" asserts that they approved it, it does not grant approval. Even "approved" turns no sending on: there is no transport in this product.

Sync to your own system

An HTTPS endpoint and a shared secret. We tell your system about opt-ins, opt-outs, inbound messages and handoffs, signed with your secret.

We never forward the customer's own words. They are not ours to pass on.

What it does not do yet

Sending, obviously. Everything above exists so that the day it can, it will already be doing so lawfully.