Most businesses know this failure: a lead arrives, and nobody is sure where it went. It is in someone's inbox, in a Facebook notification nobody opened, or in a spreadsheet a contractor keeps. This post walks through the lead routing layer that fixes it: one place every lead lands, and an alert that reaches the person who can act, on the channel they actually read. It also covers the part most automation posts skip: why we install only part of it.
If you came here from our contact form, the enquiry you send there runs through a small version of this layer on our own site. The last section says exactly what happens to it.
I am Manoj, and I lead implementation at MithTech, a team of Frappe specialists in Bengaluru. We install open-source business systems (Frappe/ERPNext, Medusa, n8n, Chatwoot) for organisations that have outgrown spreadsheets and do not want to rent their operations from a SaaS vendor.
Where do leads come from, and why do the sources never agree?
Almost every business we work with captures leads from some mix of these:
Website forms. The enquiry form, a pricing calculator, a downloadable guide, a newsletter box. Often each one emails a different address, and at least one has been silently failing since a DNS change nobody connected to it.
Paid ads. Meta Lead Ads and Google lead forms collect a name and a number inside the ad platform. They sit there until someone exports a CSV. An ad lead goes cold in minutes; a CSV export happens weeks later.
Bought and extracted lists. Trade-show scans, directory lists, a list from an industry body, LinkedIn exports. Structurally the same as an ad lead (a name, a number, a context), but it arrives as a file rather than an event, so it usually lands in a different pipeline, if it lands anywhere.
Inbound conversations. WhatsApp messages to the business number, a Chatwoot chat, a phone call. These are the highest-intent contacts a business gets, and the least likely to become a record anywhere.
The pattern is the same everywhere: four sources, four destinations, four people assuming someone else picked it up. Nobody designed it; it built up one integration at a time.
How should lead routing be structured?
The fix has two halves, and the order matters more than the tools.
Half one: write it down before you tell anyone
Every source is converted to the same shape (name, contact, context, source, attribution) and written to one durable store first. In our stack that is a Frappe CRM Lead, an ERPNext Lead where the customer already runs ERPNext, or a database table when the website is the system of record.
This is not fussiness. On our own site, the contact route writes the lead to Postgres and only then fans out to notifications. We learned that the hard way: an earlier version made the record a side effect of the notifications, so when every channel failed at once, the enquiry returned an error and could be lost. The lead is the row. Everything else is an alert about the row.
Half two: notify in parallel, never in sequence
Once the record exists, the notifications go out independently and at the same time. Not a chain, a fan-out. If the CRM webhook is down, the push alert still goes. If one channel rate-limits you, the email still goes. Each channel reports success or failure on its own, and those results are written back onto the lead, so weeks later you can see that the CRM push failed on the fourteenth and nobody noticed.
Which notification channel is right for which team?
This is where most automation advice goes wrong. It presents a menu and implies you want all of it. You do not.
What is lead routing?
Lead routing is the layer between where an enquiry arrives and where it is worked. It converts every source (website forms, ad platforms, bought lists, inbound chats) into one record in a single system, then alerts the right person on the channel they actually read. Capture is rarely the problem; routing is.
| Frappe CRM / ERPNext Lead | The durable record and assignment | Self-hosted, no licence fee | Anyone with more than one person on enquiries |
| WhatsApp alert to your team | Telling the team a lead arrived | Business API: per delivered message, by category | Teams that live in WhatsApp |
| WhatsApp to the lead | Messaging the lead | Business API: per delivered message, by category | Businesses that follow up on WhatsApp |
| ntfy | Instant phone push, no vendor | Free, self-hostable | Owner-operators who want to know now |
| Chatwoot | One reply queue across channels | Self-hosted | High enquiry volume with a support function |
| Audit trail and fallback | Existing | Everyone, as a backstop |
Frappe CRM / ERPNext Lead: the record
The destination, not a notification. This is where the lead is assigned, where its status moves, where follow-up is logged, and where you eventually count conversion by source. If you install one thing from this post, install this.
Right for: anyone with more than one person handling enquiries.
WhatsApp: the channel people actually read
For many businesses in India, the UAE and Southeast Asia, WhatsApp is where work happens. A lead alert in a WhatsApp chat the sales team keeps open all day gets picked up in minutes. The same alert in email gets picked up when someone next clears their inbox.
Two uses get confused constantly:
- Alerting your own team that a lead arrived.
- Messaging the lead to follow up.
Both go through the WhatsApp Business API with a verified business number. Meta charges per delivered message, priced by category (marketing, utility, authentication, and service for replies) and the recipient's country. Template messages have been charged that way since 1 July 2025. Replies inside an open 24-hour customer-service window, and utility templates sent inside it, have been charged since 1 October 2026, with a free monthly tier for replies (Meta's pricing page, checked 14 October 2026). Any message you start outside that window has to be an approved template. So a team alert is cheap, but it is not free and it is not template-free, unless the person receiving it has messaged the number in the last 24 hours. Then it counts as a reply: no template, and no charge while the free tier lasts.
Start with the team alert. It is one template and delivers most of the value. If you want WhatsApp messages logged against the customer or lead in ERPNext, Polygin, run by MithTech, does that: it logs each message on the ERPNext record that already has that phone number. It does not create Leads by itself; creating the lead stays the job of the routing layer.
Right for: teams that live in WhatsApp, which in our client base is most of them.
ntfy: the alert nobody has to pay for
ntfy is a self-hostable push notification service: a topic, an HTTP POST and a phone app. No per-message cost, no vendor account, no approval process. We use it for the lead alert on our own site.
It is the least glamorous item here, and it repays its setup time quickly: a few minutes of work gives an owner a phone buzz for the events they care about (a high-value enquiry, a failed payment, a stock-out) without another subscription.
Right for: owner-operators and small teams who want to know now and do not want another bill.
Chatwoot: when the lead wants to talk, not wait
If a real share of your enquiries are people who want an answer within minutes, a shared inbox that brings website chat, WhatsApp, email and Instagram into one queue is worth more than any routing sophistication. Setup is in our Chatwoot self-hosting guide.
Right for: businesses with high enquiry volume and a real support function.
Email: the one you keep, and stop relying on
Email remains the audit trail and the fallback. It should not be the main alert for anything time-sensitive.
Right for: everyone, as a backstop.
The glue: n8n
Between the sources and the destinations sits a workflow layer. We use n8n because it is self-hostable and the workflows stay yours (its licence is source-available "fair-code", not OSI open source; setup is in our n8n guide). It does the unglamorous work: polling the Meta Lead Ads API every few minutes, converting a trade-show CSV into the same shape as a form submission, de-duplicating against existing leads by phone number, enriching from a company database, and assigning the lead by territory or product.
De-duplication matters more than it sounds. A person who filled a form, clicked an ad and messaged on WhatsApp is one person, and a CRM showing three of them is a CRM your sales team stops trusting.
Should a business connect every lead source at once?
No. Automation projects rarely fail because the tools break; they fail because a team is asked to change how it works in eleven ways at once. Fix the one gap where leads currently die, install the record plus the one channel the team already reads, run it for a month, and add the next thing only when someone asks for it.
Why do we install less lead routing than we could?
We have never installed all of this for one client, and we would push back on anyone who asked us to.
The failure mode is not that the tools do not work. It is that someone builds routing with eleven integrations, a team of six is asked to change eleven habits at once, and within a quarter they are back to the WhatsApp group and the spreadsheet, with an expensive system running alongside, unmaintained and out of date.
So the sequence we run is:
- Find where leads actually die. Usually one gap: ad leads never leave the ad platform, or WhatsApp enquiries never become records. Fix that first.
- Install the record and one channel. The CRM, and whichever channel the team already reads all day. Nothing else.
- Run it for a month. Watch what people actually do, not what they said in the workshop.
- Add the next thing only when someone asks for it. A request from the team is evidence of need. A slide from us is not.
A ten-person distributor often stops at step two and is well served. A large manufacturer with several regional sales teams and territory rules needs the full routing, and gets there over months, not at launch.
What happens to an enquiry sent through our contact form?
For an enquiry sent through the contact form on this site:
- It is written first to a database record on our site (Postgres), with last-touch attribution: the page you sent it from and the channel that brought you.
- Then, at the same time and independently: a Frappe CRM Lead is created through a webhook, a push alert goes to the team through ntfy, a copy goes to our forms inbox, and an email goes to the team.
- Each of those four reports back on its own, and the results are stored on the lead record. If every channel fails but the record was saved, the form still tells you your enquiry was received, because it was.
No CSV, no export, nobody assuming someone else picked it up.
Frequently asked questions
Do I need the WhatsApp Business API for lead notifications?
To send WhatsApp messages from a system, yes, whether the message goes to your own team or to the lead. Messages you start outside a 24-hour customer-service window must use approved templates. Meta charges per delivered message by category: templates since 1 July 2025, and replies inside the window since 1 October 2026, after a free monthly tier (Meta, checked 14 October 2026). If you want an alert with no per-message cost, a push service like ntfy does the job.
Can Meta Lead Ads go straight into ERPNext or Frappe CRM?
Yes. Meta offers a webhook for real-time lead delivery, and where that is awkward to set up, a workflow that polls the Lead Ads API every few minutes is fast enough. Either way the lead arrives as an event rather than an export, which is the whole point. If you are still exporting CSVs, start there.
What happens to leads if one integration goes down?
Nothing, if the system is built in the right order. The durable record is written first, and the notifications fan out independently afterwards, so one dead channel cannot take the others with it or lose the lead. Write the per-channel results back onto the lead so a silent failure is visible later.
How do you stop the same person appearing three times in the CRM?
De-duplicate on phone number when the lead comes in, before it is created, and merge the context into the existing record rather than creating a second one. A CRM full of duplicates is one the sales team stops trusting, and that is harder to recover than the duplicates themselves.
Is ntfy worth setting up when we already have email?
For anything time-sensitive, yes. It is a self-hostable push notification with no per-message cost and little setup, and it reaches a phone immediately rather than waiting for someone to clear their inbox.
How long does this take to implement?
It depends on the sources, the system you already run and how clean your contact data is. The record plus one alert channel is a small piece of work on an existing system; multi-source routing with de-duplication, enrichment and territory rules is a larger project and should be reached step by step, not at launch. For a price range on your scope, use the estimator.
Where should you start?
If you want this pointed at your own sources, tell us where your leads currently get lost. That one answer usually decides the whole first phase.
Comments & ratings
No comments yet. Start a new discussion.
Manoj · Published on 24 August 2026
Worked with us? Leave a Google review