Bots
The client bot runtime and how to onboard a client to WhatsApp.
Repo: Backpack-Ops/bots. One Vercel deployment answers for every client. See ADR 13 for the architecture and the behavior contract.
Onboard a client bot
- Persona: write
config/<client>.mdwith plain business facts. Nothing else reaches the bot. - Env on the bots project:
BOT_<CLIENT>_WEBHOOK_TOKEN(random),BOT_<CLIENT>_ACCOUNT_ID(iese account id). - iese: create an Agent Bot (outgoing url
https://<bots-domain>/api/bots/<client>?token=...) and attach it to the client’s inbox. Shared env CHATWOOT_URL + CHATWOOT_API_TOKEN must be set once. - WhatsApp channel (client side, start early, verification takes days): Meta Business Manager account, business verification, a phone number not currently on WhatsApp, then connect a WhatsApp Cloud API channel to the iese inbox with the number’s token.
- Test with BOT_DRY_RUN=1: POST a fake message_created payload, read the reply in the response.
Verified behaviors (2026-07-21)
Grounded answers from persona facts only; unknown questions answered honestly with handoff; upset customers get one sentence and a human; wrong webhook token 401s; conversations owned by humans (status open) are never answered.