How can a business capture leads from multiple channels?

By funneling every channel website forms, WhatsApp, and email into a single CRM. Each lead is automatically tagged by source and category, then routed to the right team member, so nothing is missed regardless of how the customer reaches out.

How do you route WhatsApp enquiries to the right department?

An automatic welcome menu greets the customer and asks what they need (Products, Services, Careers, etc.). Their reply auto-assigns the chat to the correct department and logs it in the CRM as a new lead.

Can incoming emails be turned into CRM leads automatically?

Yes. The CRM can auto-create a lead from every incoming email, tagged by which address it was sent to (e.g. product@, service@). An assignment rule then routes each lead to the right department owner.

What CRM is best for managing multi-channel leads?

The right CRM depends on your needs, but the key is one that centralizes leads from every channel, tags them by source and category, assigns owners automatically, and keeps a full follow-up history. This case study uses Zoho CRM.

How do you make sure no lead is ever missed?

By ensuring every channel writes to one central CRM, running integrations in a fail-safe way (if one system is down, the others still work), and giving the whole team one dashboard where every lead is visible, tagged, and assigned.

Business Automation

How I Built a Lead Management System That Captures Every Enquiry Website, WhatsApp & Email (Case Study)

A Case Study Website, WhatsApp & Email, Unified

Most businesses don't lose customers because their product is bad. They lose them because an enquiry slipped through a crack an email nobody opened, a WhatsApp message sent to the wrong person, a form submission that landed in an inbox on a busy day and was never seen again.

That was the exact problem I set out to solve for one of my clients a government-approved electrical contractor with a growing business and enquiries coming in from every direction. This is the story of how we went from scattered, easy-to-miss enquiries to a system where every single lead is captured, tagged, and routed to the right person automatically.

The Problem: Leads Were Falling Through the Cracks

My client is a growing company with a wide offering electrical contracting, power liaisoning, substations, panels, and a full catalogue of electrical products. Enquiries came in from everywhere:

The website → quote requests, contact forms, product enquiries
WhatsApp → customers messaging the business number directly
Email → customers writing to different addresses like product@ and service@

On paper, having many channels sounds great. In practice, it created a real business risk:

A website form might email one inbox that only one person checked.
A WhatsApp message could sit unread, or reach someone who wasn't the right person to answer it.
An email to a general address might never be routed to the department that could actually help.

There was no single place where the team could see every lead. No way to know if something had been missed. And in a business where a single project can be worth lakhs, a missed enquiry isn't a small thing it's lost revenue.

The brief was simple to state and interesting to solve: make sure no lead is ever lost, and make sure every lead reaches the right department automatically.

The Core Idea: One Destination, Many Doors

The insight that shaped the whole solution was this: you can't force every customer to use one channel but you can make every channel lead to one destination.

Customers will always reach out however is convenient for them. So instead of fighting that, I designed a system where all three channels website, WhatsApp, and email funnel into a single source of truth: the CRM (Zoho CRM, in this case).

Diagram showing leads from Website, WhatsApp, and Email flowing into a CRM, where every lead is automatically tagged, assigned, and routed to the correct department. — Capture every lead from your website, WhatsApp, and email, then automatically tag, assign, and route it to the right department.

Every lead, no matter how it arrives, ends up in one place tagged by where it came from, tagged by what it's about, and assigned to the person who should handle it. The key challenge was that each channel needed a different technique to get there. Here's how I approached each one.

Channel 1: The Website Tagging at the Source

The website was the most straightforward, because I controlled the code end to end.

The site (built on Next.js) already had working API routes for its forms quote, contact, partner, and career. Each one sent an email on submission. My job was to extend these without breaking what already worked.

I added two things to each route, running alongside the existing email not replacing it:

Create a lead in the CRM, tagged with the category the form already knew (a product quote is tagged "Products," a service enquiry "Services," and so on).
Send an instant WhatsApp notification to the relevant department, so the right person knows a lead just came in.

The important engineering decision here was resilience. These three actions email, CRM, and WhatsApp run in parallel and independently. If the CRM is briefly unreachable, the email still sends and the customer still sees a success message. No single failure can break the submission. That "fail-safe, not fail-together" design is what makes it trustworthy in production.

Because the website form already knows the category, routing here is automatic and invisible. The customer just submits everything else happens behind the scenes.

Channel 2: WhatsApp Letting the Customer Route Themselves

WhatsApp was more interesting, because when someone messages a business number directly, there's no form and no code in between to tag the enquiry. The message just arrives.

The elegant solution was to let the customer categorize themselves through an automatic welcome menu.

The moment a customer messages the business WhatsApp number, they instantly receive:

Welcome! Please reply with a number so we can
connect you to the right team:

1 Products (Panels, Transformers, Wires, Lighting)
2 Services (Contracting, Liaisoning, MEPF, AMC)
3 Become a Partner
4 Careers / Jobs
5 Something Else

When they reply with a number, the conversation is automatically assigned to that department's team member and simultaneously logged in the CRM as a new lead, tagged with its source and category.

This solved three problems at once:

One number for customers to remember, instead of many.
Self-routing the customer's own choice sends them to the right person, no manual sorting.
Nothing missed every conversation becomes a tracked lead in the CRM.

The lesson here: when you can't tag a lead from the outside, design an interaction that lets the lead tag itself.

Channel 3: Email Using the Address as the Category

Email was the third puzzle. My client already used category-based addresses product@, service@, liaisoning@, and so on. The challenge was that emails were being read by people, but not captured as trackable leads.

I used a two-part approach:

Part A Every email becomes a lead. I configured the CRM to automatically create a lead from incoming email, tagged by which address the customer wrote to. An email to product@ becomes a lead tagged "Products"; an email to service@ becomes "Services." The address the customer chose effectively becomes the category for free.

Part B Every lead gets an owner. Then, using assignment rules inside the CRM, each lead is automatically handed to the correct department person based on that tag. A "Products" lead goes to the products team member; a "Careers" email goes to HR.

The neat part is that this required almost no change to how customers already behaved. They kept emailing the same addresses they always had but now every one of those emails becomes a tracked, owned, follow-up-able lead instead of a message that might get buried.

The Result: One Dashboard, Zero Missed Leads

Once all three channels were wired up, the transformation was clear.

Before: enquiries scattered across inboxes and phones, no visibility, no accountability, and a real risk of leads quietly disappearing.

After: every lead from the website, WhatsApp, or email lands in the CRM, automatically:

Tagged by source (where it came from)
Tagged by category (what it's about)
Assigned to an owner (who's responsible)
Stored with full history (so nothing is forgotten)

The whole team now works from one dashboard. Management can see every lead, its source, and its follow-up status at a glance. And the answer to "did we miss anything?" changed from "we're not sure" to "no it's all here."

What I Took Away From This Project

The most valuable lesson from building this wasn't technical it was about matching the solution to how each channel actually works.

For the website, I could tag leads in code.
For WhatsApp, I designed an interaction so leads tag themselves.
For email, I used the address the customer already chose as the category.

Three completely different techniques, all converging on one goal: a single, reliable home for every lead.

That's the kind of problem I love working on where good systems thinking matters as much as good code, and where the real win isn't a feature, but a business that stops leaking opportunities.

If you're running a business where enquiries come from everywhere and you're not confident every one is captured and followed up, this is exactly the kind of system that fixes it. And if you'd like to talk through your own setup, I'm always happy to.

Curious whether a system like this would fit your business?

Book a free 30-minute call. We'll look at the enquiries eating up your team's day and find the ones worth automating first. No jargon, no pressure.

Schedule a call →