Categories Whatsapp Marketing

WhatsApp Lead Management: Route Every Enquiry to the Right Team and Follow Up Automatically

WhatsApp lead management: route every enquiry and follow up automatically

Short answer: to route WhatsApp enquiries to the right person automatically, let a chatbot ask the first one or two questions with buttons, tag the chat with the answer, and have routing rules send it to a team queue based on that tag. Round robin spreads each queue across agents. Follow-ups to leads who go quiet run as an automation that stops the moment they reply, using a normal message while Meta’s 24-hour window is open and an approved template after it closes. Qualified leads go into your CRM from the chatbot itself, so sales works where it already works.

This is the setup Moustache Escapes, the hostel and hotel chain, runs on CampaignHQ. We’ll use it as the worked example. Last updated: 21 November 2026.

Why WhatsApp leads wait so long for a reply

When a team says its WhatsApp leads are slow, the problem is usually on the business side, not the customer’s. Every enquiry lands in one shared queue. Sales, support, the front desk and the accounts team all look at it, and each assumes someone else will pick up the chat that isn’t clearly theirs. A lead asking about a group booking sits behind ten guests asking for the Wi-Fi password.

The second cause is the first message itself. Most enquiries now start from a click-to-WhatsApp ad, a website button or an Instagram link, and those arrive as pre-filled text like “Hi, I want to know more” or just “Hi”. So a rule that reads the customer’s words to decide where the chat goes has nothing to read. Teams that route on keywords find most chats fall through to a default queue, which puts them back where they started.

The fix is to stop routing on what the customer typed and start routing on what the customer chose.

Sort first, then qualify

Before a bot asks a single qualifying question, it should work out what kind of conversation this is. Moustache Escapes does this with its first message. Their chatbot runs day and night and asks the customer to choose between a new booking, an existing booking and something else. If you are building one from scratch, start with our guide to the WhatsApp chatbot for business. Each path does a different job.

Existing guests get their routine answers from the bot, such as check-in times, directions and booking changes, and reach a person only when the bot can’t help. “Something else” catches the conversations that quietly clog a sales queue, including people asking about jobs. New-booking enquiries are the only path that gets qualified, and the only one that becomes a lead.

That order matters more than the questions. If you qualify everyone, existing customers get asked about their budget and travel dates, and your CRM fills with leads that aren’t leads. Sorting first keeps the sales queue for sales.

The same shape works outside travel. An EdTech team splits new admissions, current students and fee queries. A real estate developer splits site visits, existing buyers and channel partners. Keep it to three or four choices on buttons, because a customer who has to type an answer often doesn’t.

Route on the tag the bot sets, not the words

Once the customer taps a choice, the bot tags the chat or the contact. Routing rules then read the tag. On CampaignHQ a rule can match message text, a regex, a conversation tag or a contact tag, and send the chat to a team queue or a named agent. With tags doing the work, a few rules cover everything:

Tag set by the bot Queue How chats are shared
new-enquiry Sales Round robin across the sales team
existing-customer Support Round robin, and the same agent again if the customer comes back
vip or high value Priority Senior agents only
language: Hindi Hindi desk Agents who reply in Hindi
no tag Default A named owner who clears it daily

Two settings decide whether this feels fast to the customer. Round robin stops one agent from collecting every new chat while others sit idle. Sticky assignment sends a returning customer back to the agent who spoke to them last, so they don’t have to explain themselves twice. And the default queue needs a named owner. Without one it becomes the old shared inbox again.

When the bot hands a chat to a person, the full conversation and the answers it collected go with it. The agent opens the chat already knowing the dates, the property and the group size. You can see how these rules are set up on our agent routing page, and how this compares with moving reps off personal numbers in WhatsApp CRM for sales teams.

Form not loading? Open it on our site.

Send qualified leads to your CRM from the chat

This is the step most WhatsApp setups skip, and it is the reason Moustache Escapes moved to us from another WhatsApp platform. They run their own in-house systems, and they needed a partner who would wire WhatsApp into them rather than ask them to work inside a separate tool.

Their chatbot asks the booking questions, and when a new-booking lead finishes, the flow makes an API call that creates the lead in their CRM. Their sales team then works the lead in the CRM they already use. When they message a lead from the CRM, it goes out through the CampaignHQ API on the same WhatsApp number. Webhooks push inbox conversations back into the CRM, so the chat history sits on the lead record. The CampaignHQ inbox is kept for the conversations that need an agent, not for every lead.

If your team lives in a CRM, this split saves a lot of tab switching. Reps don’t copy phone numbers between tools, nobody re-types what the customer already told the bot, and your CRM’s reporting counts WhatsApp leads like any other source. If you don’t run a CRM, the contact profile in CampaignHQ holds the same answers and the inbox is where sales works. For the integration side, see WhatsApp CRM integration in India.

We built Moustache’s chatbots with their team, met their teams and stayed on a shared WhatsApp group with them until it went live. That part isn’t software, but it is usually why an integration like this works.

Following up leads who go quiet

Plenty of leads answer two questions and then stop. Most of them haven’t decided against you. They got busy, wanted to check with someone, or were comparing two options. A follow-up brings a good share of them back, as long as it arrives at the right time and stops the moment it isn’t needed.

Timing on WhatsApp is shaped by one Meta rule. When a customer messages you, a 24-hour customer service window opens. Inside it you can send any normal message. Once it closes, you can only start a conversation with a template that Meta has approved. So plan the follow-ups in two parts.

The first nudge goes inside the window, a few hours after the lead stops replying. It can be a plain, personal message that picks up exactly where they left off, like the dates they mentioned or the question the bot was asking. This is the follow-up that works best, and the one most teams miss, because by the time a person notices the chat the window has closed.

Later nudges, a day or several days on, have to be approved templates. Keep them few and give each one a reason to reply: an answer to the question they asked, availability for their dates, or a direct line to a person. Use email for the longer material, such as a brochure, a fee structure or a property guide. Moustache sends offers to leads on both WhatsApp and email, and each channel does what it is good at.

Every follow-up sequence needs exit rules. Stop when the lead replies, when they book, and when an agent has taken over the chat. A lead who gets an automated “just checking in” after already talking to your sales team trusts you less, not more. In CampaignHQ, an automation can start from a tag the bot set, wait, branch on whether the lead replied or read the last message, and switch between WhatsApp and email in the same flow. For how many template messages you can send in a day, see WhatsApp message limits per day.

What you need to run this

All of this needs the WhatsApp Business Platform, the API, rather than the WhatsApp Business app on a phone. The app has no routing rules, no chatbot builder and no way to post a lead into your CRM. You can keep using the app on the same number through coexistence, so owners who like replying from their phone don’t lose that. Our WhatsApp Cloud API guide covers what the API is, and WhatsApp Business API providers in India compares the ways to get it.

Then build in this order. Write down the three or four reasons people message you and make them the bot’s first choice. Decide which of those becomes a lead and the questions that qualify it. Set one tag per path and one routing rule per tag. Connect your CRM if you have one. Add the follow-up automation last, once you can see where leads actually stop. If your enquiries start on Instagram, the same pattern applies there, as covered in Instagram DM automation for hotels and hostels.

Frequently asked questions

Can I automatically assign WhatsApp chats to different agents?

Yes, on the WhatsApp Business API with a team inbox. Routing rules send each new chat to a queue or a named agent based on the message, a regex, or a tag on the chat or contact. Round robin then shares each queue’s chats across its agents. The WhatsApp Business app on a phone can’t do this.

Can one WhatsApp number serve both sales and support?

Yes. Customers message one company number, and the chatbot’s first question decides which team gets the chat. Each team sees its own queue, and supervisors see every conversation on the number.

How do I follow up a WhatsApp lead who stopped replying?

Send the first follow-up within 24 hours of their last message, while you can still send a normal message. After that, use an approved template. Run it as an automation with exit rules so it stops when they reply, book or start talking to an agent, and move longer detail to email.

Can a WhatsApp chatbot send leads to my CRM?

Yes. On CampaignHQ a chatbot step can call your CRM’s API with the answers the lead gave, and webhooks can push the conversation into the CRM as well. Your team can also send WhatsApp messages from the CRM through our API, on the same number.

Should the chatbot qualify every person who messages us?

No. Sort first and qualify only new enquiries. Existing customers, partners and job seekers should get their own paths, or your sales queue and CRM fill with conversations that were never leads.

Next step

If your team answers WhatsApp enquiries from one shared queue today, send us the three or four reasons people message you, and we’ll sketch the routing and follow-up for your number on a call. If you run your own CRM, bring that along too.

Or start a 7-day free trial, no credit card needed.

Prefer to talk first? See how it works, or start a 7-day free trial, no credit card needed.

Written by CampaignHQ Team