WhatsApp Business
The conversation that closes comes back to the ad that opened it.
WhatsApp is where your customers actually talk. Apointo receives the interaction through the Twilio WhatsApp adapter, ties the thread to its original click, and confirms outcomes through the same direct-confirm path every other source uses.
Conversations happen where attribution cannot see
The customer clicks the ad, saves your number, and buys three days later inside WhatsApp. Google Ads counted a click. Nobody connected that click to the revenue, so bidding optimizes on forms while sales close in chat.
The thread joins the ledger
Message events arrive alongside every other source and get matched to their click history. When the sale closes in the chat, you confirm it once; the conversion carries its original identifiers, and delivery logs prove what each platform received.
import { app } from '@vizuh/apointoo-sdk/adapters/notification/twilio-whatsapp'- 01Ad click lands on a wa.me link
- 02Capture keeps the click context
- 03The conversation opens and its events reach Apointo
- 04Outcome confirmed when the thread closes
- 05Delivery receipts land in the same ledger as every channel
Connect the Twilio WhatsApp adapter for message events.
Capture keeps the click context from wa.me landing links.
Confirm the outcome when the conversation closes.
Retractions follow the same rules as every other channel.
| From | Apointo |
|---|---|
| New inbound conversation tied to a click | lead_captured |
| Qualified inside the thread (your rule) | qualified_lead |
| Sale confirmed in chat | sale_paid |
| Reversed sale | refund_retraction |
Do you read my conversations?
No. Only structured events needed for matching travel into Apointo: contact reference, event type, and time. The chat itself stays in WhatsApp.
Which provider carries the messages today?
Twilio, through the shipped adapter. The confirmation path works with any backend that can call it.
What does Beta mean here?
The message-event path ships and runs; conversation-outcome confirmation depends on your workflow. The page documents what exists, not what is planned.