WhatsApp Inbox Pipelines: Route Customer Messages Automatically
Decide what happens to every incoming WhatsApp message: recognise your own intents, open orders and tickets automatically, reply with the order number or ticket reference, and hand the rest to a person — from ready templates for shops, service businesses and software teams.
WhatsApp Inbox Pipelines
A pipeline decides what BIZA does with each WhatsApp message a customer sends to one of your business numbers. It classifies the message into intents you define, runs an ordered list of routes, and leaves anything it is unsure about in the inbox for a person. Every number you connect can run its own pipeline: a sales number that takes orders, a support number that files issues.
1. Start from a template
Open CRM → WhatsApp Inbox → Pipelines and pick a template. Each one is a complete pipeline — intents, routes and replies — copied into your workspace, where you edit it freely.
| Template | Built for | What it does |
|---|---|---|
| Shop & restaurant orders | Retail, restaurants, food | Claude matches the ordered items to your products and opens an order on the billing counter; the customer gets the order number and total, and can ask where their order is. Ambiguous items go to a person instead of being guessed. |
| Service business | Agencies, consultancies, government-services offices | Enquiries become leads, requests from known customers start a service case, documents attach to the open case, every message is acknowledged. |
| Issue tracker | Software and product teams | Bug reports get a Claude triage (severity, what happened, next step), become a service case or a lead, notify support and acknowledge the sender. |
| Blank | Anything else | Classifies with the default intents and keeps everything in the inbox until you add routes. |
2. Bind your numbers
On the pipeline's Numbers tab you see every WhatsApp Cloud number connected to your account. Choose the pipeline each one uses; a number left unbound falls back to the workspace's default pipeline. New numbers on your WhatsApp Business account appear automatically after their first message.
3. Teach it your intents
The Intents tab holds the classifier profile: one or two sentences about what your business does, and the list of intents the AI may choose from — each with a key, labels in English and Arabic, a description and examples. Add fields to extract (delivery address, requested time, affected product area) and routes can use them.
Messages are read in English, Arabic, Malayalam, Hindi and mixed scripts; summaries are produced in English and Arabic.
4. Routes: when this, do that
Routes run top to bottom for every classified message. Each route is a when (intent, whether the message is actionable, whether the sender is a known customer, minimum confidence) and a then:
- Create a record — a lead, a service case, a note on an open case, a support ticket, a billing-counter order.
- Ask Claude — a triage or extraction step with your own instructions. Claude can analyse only, propose actions for a person to approve, or act on its own within the actions you allow.
- Reply on WhatsApp — a message template with placeholders such as the sender's name, the summary, or a ticket number created by an earlier route. Replies go out inside WhatsApp's 24-hour customer-service window from the number that received the message.
- Notify the team, assign to a person, or leave for a person in the inbox.
- Call your endpoint — post the classified message, signed, to an HTTPS endpoint of your own; it can answer with a reply to send or a record to link.
Drag routes to reorder them, mark any route as needing approval, and stop the routes below it when it matches.
5. Replies: automatic or approved
Per pipeline, replies send automatically (the default), wait for approval in the inbox, or are off. Approval-gated replies and Claude's proposals show up on the message in the inbox with Approve and Reject buttons.
6. Test before you go live
The Test tab classifies a message exactly like a real one and lists the routes that would fire, with the reply rendered — nothing is saved or sent.
7. See what happened
Every message in the inbox shows which pipeline and routes handled it, the records they created, Claude's analysis, and anything waiting for approval. The pipeline's Runs tab keeps the full history.
8. Your own integrations
Register HTTPS endpoints under Endpoints with a signing secret (stored encrypted, never shown again). Each call carries X-Biza-Timestamp and X-Biza-Signature: v1=HMAC-SHA256(secret, "<timestamp>.<body>"). Respond with JSON { "reply_text": "…", "link": { "entity_type": "…", "id": "…" } } to send a WhatsApp reply or link a record of yours.
Frequently asked questions
Does it need the WhatsApp Cloud API? Receiving works with either the Cloud API or the browser bridge; automatic replies need a Cloud API number.
Will it create records from small talk? No — "thanks" and "ok" are filtered before the AI runs, and templates only act on messages classified as actionable. Anything uncertain stays in the inbox.
Can I stop a route from acting without deleting it? Yes — switch it off, or set it to require approval.