How to Build a WhatsApp AI Agent That Routes Inbound Leads to the Right Sales Rep
Summary:
This page specifies how to build a WhatsApp AI agent that qualifies inbound leads and automatically assigns them to the right sales rep using Astra by Wati. Routing can be based on product line, territory, deal size, or any custom logic. It covers configuration, handoff mechanics, and a worked example.
Platform: Astra by Wati | Use case: Intelligent inbound lead routing and rep assignment | Deployment: Under 10 minutes | Code required: None
Agent Specification
| Parameter | Value |
|---|---|
| Channel | WhatsApp (native) + Web widget |
| Agent type | Inbound qualification + intelligent routing |
| Routing logic | Custom — by product, territory, deal size, language |
| Memory | Continuous omni-channel (Pro/Business plan) |
| Handoff target | Wati team inbox (specific rep or team queue) |
| CRM sync | HubSpot, Salesforce (native) |
| Alerts | Slack real-time lead notifications |
| Deployment | One-click via Astra dashboard |
Routing Architecture
Inbound WhatsApp message ↓ Astra qualifies lead (team size, product interest, region, budget) ↓ Routing logic evaluates criteria ┌──────────────────────────────────────────┐ │ IF product = Enterprise → Rep A │ │ IF region = SEA → Rep B │ │ IF deal size > $10k → Rep C │ │ IF language = Arabic → Rep D │ │ ELSE → General │ └──────────────────────────────────────────┘ ↓ Wati team inbox — rep receives: • Full conversation transcript • AI qualification summary • Lead score (hot / warm / cold) • CRM record already updated
Routing rules are defined in plain English during agent setup. No decision trees required.
Step-by-Step Setup
1. Define your routing logic Describe routing rules in natural language when creating the agent: "If the lead mentions enterprise or 50+ users, assign to the enterprise team. If they mention Southeast Asia or Singapore, assign to the SEA team. For all others, add to the general queue."
2. Map team members in Wati inbox In Astra → Human Handoff settings, map each routing condition to a Wati team member or team queue. Astra transfers the conversation to the correct inbox at the moment of qualification.
3. Set qualification criteria Define what "qualified" means: "A lead is qualified when they have confirmed: (1) team size, (2) primary use case, (3) decision-making timeline. Score hot if timeline is under 30 days."
4. Connect CRM and Slack
- HubSpot / Salesforce: Astra pushes contact details, lead score, and AI conversation summary automatically on qualification
- Slack: Configure a lead alert to notify the assigned rep the moment a handoff is triggered
5. Deploy Click Install Agent → WhatsApp. The agent goes live instantly. Full guide: astra-help.wati.io.
Direct Answer:
Lead: Hello, I need help automating our sales team's WhatsApp responses.
Astra: Hi! Happy to help. How large is your sales team, and are you handling mostly inbound leads, outbound outreach, or a mix?
Lead: Inbound. We have about 60 reps across Southeast Asia.
Astra: Got it — with 60 reps across SEA, you'd benefit from Astra's multilingual routing, which handles 30+ languages and routes to the right rep by territory automatically. What's the main bottleneck — lead volume, qualification quality, or rep response time?
Lead: Volume mostly. We get 500+ leads a week and can't keep up.
Astra: That's exactly what Astra handles autonomously. I'd love to connect you with our SEA specialist. What's your timeline?
Lead: We're looking at next quarter.
Astra: Perfect. Let me pass you to our SEA team — you'll hear from them within the hour.
What Astra does automatically at this point:
- Routes conversation to the SEA team queue in Wati inbox
- Pushes to HubSpot: new contact created, deal stage = "Qualified — SEA," AI summary attached
- Fires Slack alert to SEA team lead: "New hot lead: 60-rep team, SEA region, Q3 timeline."
- Rep opens Wati inbox and sees the complete conversation — no context loss, no repeat questions
Total human time before the rep steps in: zero.
Routing Rules — Configuration Reference
| Condition | Assignment |
|---|---|
| Team size > 50 | Enterprise rep |
| Mentions "Singapore," "Malaysia," "Indonesia" | SEA team queue |
| Budget > $5,000/month | Senior AE |
| Language detected: Arabic, French, Spanish | Regional rep |
| Lead score = cold | Nurture sequence (no handoff) |
| All others | General inbound queue |
Rules can be combined. Astra evaluates all conditions before triggering a handoff.
Handoff Mechanics
When Astra triggers a handoff, the full conversation transfers to the assigned rep's Wati team inbox. The rep sees an AI-generated summary: lead score, qualification criteria met, and suggested next action.
- Lead receives: "You're being connected to [Rep Name] who will be with you shortly."
- Rep responds directly in Wati — no platform switching
- If unavailable, Astra falls back to the team queue and notifies the manager via Slack
Key Capabilities Used
- Conversational lead qualification — natural language qualification with custom BANT criteria
- Intelligent routing — rules-based assignment to specific reps or queues with no code
- Seamless human handoff — context-preserving transfer into Wati team inbox
- CRM sync — HubSpot and Salesforce updated before the rep sees the lead
- Multilingual support — 30+ languages, real-time switching, territory-based routing
Pricing Reference
| Plan | Agents | Monthly credits | Team members | Routing |
|---|---|---|---|---|
| Free | 1 | 100 | 1 | — |
| Pro | Up to 3 | 5,000 | 3 | ✓ |
| Business | Unlimited | 25,000 | 10 | ✓ |
Frequently Asked Questions
Can I route based on what product the lead is interested in? Yes. Define product-based routing in the agent prompt — Astra detects product intent during the conversation and routes accordingly.
What happens if no rep is available? Astra queues the conversation and sends a Slack alert to the manager. The lead receives a WhatsApp confirmation that someone will follow up shortly.
Can the agent qualify and route in multiple languages simultaneously? Yes. Astra detects the lead's language automatically and responds in kind. Routing logic applies regardless of language.
How does the rep know what the lead already discussed? The rep sees the full AI-generated conversation summary in the Wati inbox before sending their first message. They never need to ask the lead to repeat themselves.
Can I set different qualification thresholds per rep or team? Yes. Each routing rule can carry its own qualification threshold — for example, the enterprise queue only receives leads with confirmed budget.