The WhatsApp number the klien switches on, answered under your brand.
The WhatsApp connector lives inside Business OS. The klien grants Meta consent on the workspace you provisioned and points their WhatsApp Business Account at the operating layer. Inbound chats land on the chat desk, get grounded in the klien catalog, and go back out as replies under your partner brand, inside WhatsApp policy. You stay the operator on record. The klien keeps the number.
Runs under
Your partner brand, on the workspace you provisioned for the klien.
Serves
The klien team, with one desk for WhatsApp and every other channel they connect.
Talks to
The klien end customers, on the WhatsApp Business number the klien already owns.
The klien wires up their WABA. The operating layer does the rest.
A Meta consent dialog opens on the klien workspace. The klien selects the WhatsApp Business Account and phone number they own. The connector subscribes to the messages and statuses webhooks, registers the inbound URL, and the chat desk goes live. No tokens flow back to the partner UI. No klien data crosses tenant boundaries.
whatsapp_business_messaging
Receive inbound customer messages on the connected business number, and post replies through the official WhatsApp Cloud API. Reply flow only fires after the klien grants consent and the operating layer composes a grounded answer on the klien account.
whatsapp_business_management
Read the connected WhatsApp Business Account (WABA) id, phone number id, display number, and delivery status. Manage approved message templates so the operating layer can pick the right template inside or outside the customer-service window.
Free-form inside 24h, templates outside it.
WhatsApp Business Platform draws a hard line at the 24-hour customer-service window. The operating layer respects it on every send, so the channel stays in good standing for the klien.
Inside the 24h window
When the end customer messages the klien business number, WhatsApp opens a 24-hour customer-service window. Inside that window the operating layer can send free-form replies grounded in the klien catalog and policies.
Outside the window
Once the window closes, free-form messages are not allowed. The operating layer falls back to pre-approved templates registered on the klien WABA. Templates are picked by intent, not stuffed with content the klien did not approve.
No unsolicited outreach
The connector does not send cold messages. It does not scrape numbers, import lists from prospecting tools, or open conversations the end customer did not start. The channel is a service surface on top of klien-owned demand.
Template hygiene
Templates are submitted, reviewed, and versioned on the klien WABA. The operating layer reads the latest approved template, fills the variables from grounded klien data, and logs the chosen template id on every send.
Five surfaces, nothing else.
The connector pulls only what the chat desk needs to answer a thread. Contact book exports, status broadcasts, group metadata, and prospecting fields stay out of scope.
Account identifiers
WhatsApp Business Account (WABA) id, phone number id, display phone number. Used to render the connection inside the klien workspace and to address API calls under the right business identity.
Connection tokens
Cloud API access token issued by Meta when the klien grants consent. Stored encrypted at rest. Never returned to the partner UI. Used only for outbound calls from the operating layer.
Inbound chats
Sender WhatsApp id, message text, attachment or media URL, timestamps, message id, conversation context. The grounding layer reads these to compose a klien-faithful reply inside the same thread.
Outbound replies
Generated reply text, template id when used, send timestamp, Cloud API message id, delivery and read status returned by the webhook. Logged against the klien thread for the audit trail.
Webhook metadata
Event type (messages, statuses, template review), delivery time, HMAC SHA-256 signature verification result. Used to keep the desk in sync with the channel and to drop any tampered payload.
One klien WABA, one WhatsApp silo.
No partner can reach into another partner book. No klien can reach into another klien on the same partner book. The connector is engineered so the boundary holds at the database, not just at the UI.
01
The klien connects through their own WABA consent
The Meta authorization dialog opens inside the klien workspace. The klien picks the WhatsApp Business Account and number they own. The token comes back attached to that klien tenant, not to the partner, not to Laras, not to any other klien.
02
Tenant scope is enforced at the database layer
Every WhatsApp row carries the klien tenant id. Postgres row-level security blocks any read that does not match the active tenant. A partner cannot see another partner klien. A klien cannot see another klien on the same partner book.
03
No partner reads the raw token
The Cloud API token lives in the operating layer. Reply composition and send happen on the same surface that holds the klien catalog and policies. The partner UI shows status, volume, outcomes, never the secret.
04
Klien can disconnect in one click
A klien revokes the connection from inside their workspace settings, or from the Meta WhatsApp Manager directly. The token, webhook subscription, and cached identifiers are cleared within minutes. Past threads remain as business history under the klien tenant.
Not a blast tool. Not a scraper. Not a data resale layer.
No selling
The connector never resells, rents, or shares klien WhatsApp data with advertisers or data brokers. It exists to answer threads on the klien number, period.
No cold outreach
It does not import number lists from prospecting tools and it does not open conversations the end customer did not start. Inbound is the only trigger.
No partner export
The partner cannot download the klien customer book. Reporting shows volume, outcomes, and quality, never contact-level export.
No training on klien data
Klien threads are not used to train models. They are stored to ground the next reply on the same thread, and to keep the audit trail.
Sell the WhatsApp channel as a klien outcome, not a license you resell.
You set the price. Subscription, retainer, project, outcome. The operating layer runs quietly under your brand on the klien WABA, and the WhatsApp channel becomes something the klien wants to keep paying you for.
For the platform addendum used during Meta App Review, see the Privacy Policy and Data deletion references.