@Atlas on WhatsApp
One number per store, one conversation. Ask @Atlas a question from your phone and get the same answer the web chat would give.
The WhatsApp channel runs the same @Atlas orchestrator as the web chat, against the same store context, billed against the same credit ledger. It is a text surface: today the webhook processes text messages and nothing else.
Prerequisites
Before you start
- A BoostEcom account (sign up free) on a paid plan:
every reply spends credits, and the channel asks the same
ai.usepermission the web chat does. - A WhatsApp Business Account (WABA) on Meta, with a phone number and a system-user access token. The channel is wired with those credentials; there is no SMS-code flow.
- A store in your organisation. Routing is per store: one WABA number maps to one store.
Step 1
Connect the number to your store
Open your store's Settings → Connectors and find the WhatsApp card. It asks for the values Meta gives you:
| Field | Where it comes from |
|---|---|
| Phone number ID | Meta → WhatsApp → API setup |
| Access token | A system user token with whatsapp_business_messaging |
| Verify token | A string you choose; you paste the same one into Meta |
| Business account ID | Meta → WhatsApp → Business account |
| App secret | Meta → App → Settings → Basic (used to verify signatures) |
The card shows you the webhook URL to paste into Meta's callback configuration, and your verify token is what Meta echoes back to prove the endpoint is yours. Tokens are AES-256-GCM encrypted at rest and are never shown again after saving.
If you do not bring your own number, messages route through a platform fallback number shared across stores. The card tells you which of the two is active.
Step 2
Send your first message
Message the number you connected. @Atlas replies in the same thread, in plain text.
"Audit my best-selling product page and tell me the top three conversion wins."
The reply is generated by the same orchestrator the web chat uses, with the store's memory and rules loaded, and it is charged to the organisation's credit balance like any other turn. If the balance is empty, the channel says so rather than answering for free.
Step 3
Which store answers
Routing is by number, not by command: each WABA phone number is bound to exactly one store, and every message on that number reaches that store.
There is no in-message store switching. To ask about a different store, message the number bound to it, or use the web chat, where the store picker is one click.
Step 4
What works, what doesn't
| Feature | WhatsApp | Web chat | |---|---|---| | Text messages | ✅ | ✅ | | Voice notes | ❌ not processed | ✅ | | Image / PDF attachments | ❌ not processed | ✅ | | Multi-turn conversation | ✅ same thread | ✅ | | Web search | ✅ | ✅ | | Shopify / Klaviyo / MCP tool calls | ❌ web chat only | ✅ | | Live voice call with @Atlas | ❌ | ✅ | | Workflow editor + canvas | ❌ | ✅ | | Streaming responses | ❌ one final message | ✅ token-by-token |
The streaming row is a WhatsApp limitation: the protocol has no partial message update. The rest are simply not built yet: this table listed voice notes, attachments and store tool calls as shipped until 2026-09-05, and none of the three were.
Step 5
Disconnect the number
Same place: Settings → Connectors → WhatsApp → Disconnect. The encrypted credentials are removed and the number stops routing. Conversation history stays in your BoostEcom account.
Privacy
What WhatsApp sees
- Message bodies, which is the minimum for delivery. WhatsApp encrypts them end to end between you and the business number.
- Delivery and read receipts on your messages.
- Nothing about your store, organisation, credit balance, or any other BoostEcom data: that stays server-side.