Lead Routing Rules: Round-Robin, By Area, By Language

Last Tuesday at 4 pm, a boutique fitness studio in Jaipur missed a ₹75 k enrollment because the lead landed in a WhatsApp chat that was already buzzing with class‑booking requests. The owner finally saw the message an hour later, replied, and the prospect chose a competitor who answered instantly. If the lead had been auto‑routed to the trainer who handles new sales, the loss would never have happened.

For Indian SMBs that live on WhatsApp, that one missed reply can mean a whole month of cash‑flow trouble. Below we break down why lead‑routing rules—Round‑Robin, By Area, By Language—are not a nice‑to‑have feature but a revenue‑protecting necessity.

---

Why this matters for Indian SMBs

Indian small‑and‑medium businesses run on razor‑thin margins. A D2C apparel brand in Tier‑2 Bhopal spends an average of ₹2,200 / month on SaaS tools and still wrestles with ₹30 k of COD‑related RTO losses every quarter. The common denominator? Leads get stuck in a single inbox, often WhatsApp, and the person who can close them is unavailable.

• WhatsApp is the first point of contact for 87 % of Indian consumers (source: Mobile World Congress 2023). Email sits at the back of the queue. If your CRM can’t route a WhatsApp lead instantly, you’re already losing the conversation window.
• Language fragmentation is real. In Hyderabad, a Hindi‑speaking prospect will drop a message in Devanagari, while a Telugu speaker will type in English but expect a Telugu reply. Routing by language cuts the back‑and‑forth that burns 5‑10 minutes per chat—time you could spend closing another sale.
• Geography still decides logistics. A Karnataka‑based plumbing service can’t send a technician from Delhi on the same day. Area‑based routing ensures the lead is handed to the nearest field rep, trimming travel costs that average ₹1,200 / job for small service firms.

When you add up the lost opportunities—₹12 k per week for a single sales rep who misses three leads—that’s ₹624 k a year for a modest team of five. Lead‑routing rules convert that “maybe later” into a concrete “yes today”.

---

The problem (with real numbers)

Most Indian SMBs cobble together a Frankenstein stack: WhatsApp Business API (₹1,200 / mo), a separate CRM (₹1,500 / mo), a booking calendar (₹800 / mo), and a payments gateway (₹300 / mo). The average total spend lands at ₹3,800 / month, well above the typical SaaS budget of ₹500‑3,000.

Lead‑handling bottlenecks

Metric	Typical SMB	What it costs
Avg. inbound WhatsApp leads / day	35
Avg. response time (no routing)	45 min	1 lost sale per 10 leads → ₹75 k / month
Leads handled per rep (manual)	12
Leads missed due to overload	8	₹60 k / month

A Mumbai e‑commerce store that processes 150 WhatsApp enquiries daily finds that 30 % go unanswered for more than 30 minutes. With an average order value of ₹2,500 and a conversion rate of 4 % for timely replies, the store loses ₹4.5 lakh every month.

GST and payment friction

Every missed lead also means another GST filing entry you have to chase later. The CA spends an extra ₹2,400 / month just reconciling untracked WhatsApp sales, inflating your cost structure.

In short, the problem isn’t “we have too many tools”. It’s no unified logic to decide who gets the lead, when, and in which language. The result is slower replies, higher RTO, and a bloated SaaS bill.

---

What works

A single platform that lets you define routing rules solves three pain points at once: speed, relevance, and cost. Below is the playbook we follow with Doggu’s rule engine, and why each rule type matters.

1. Round‑Robin – fairness and capacity balancing

How it works: Every new lead is assigned to the next available sales rep in a circular list. If you have three reps, lead 1 goes to A, lead 2 to B, lead 3 to C, then lead 4 back to A.

Why it matters:

• Prevents a single rep from being overloaded while others sit idle.
• Guarantees that each rep gets a minimum of 12 leads per day (assuming 36 daily leads), which aligns with the average handling capacity of Indian salespeople.
• Keeps morale high; reps see a transparent distribution rather than a “favoured‑friend” bias.

Real‑world example: A Jaipur boutique hotel with 4 front‑desk executives saw its average response time drop from 38 min to 12 min after enabling round‑robin. Within two weeks, weekend bookings rose by ₹1.8 lakh. The hotel also reported a 22 % drop in staff overtime because the load was evenly spread.

2. By Area – logistics and cost efficiency

How it works: You tag leads with a pin‑code or city name (auto‑extracted from the WhatsApp message). The rule maps each area to a designated rep or field team.

Why it matters:

• Cuts travel time for service‑based SMBs (plumbers, electricians).
• Reduces per‑job travel expense from ₹1,200 to ₹400 on average.
• Improves on‑site first‑visit success because the technician is already familiar with local regulations.

Real‑world example: A Tier‑3 electrical contractor in Madhya Pradesh had 60 % of jobs assigned to a rep 200 km away, inflating fuel costs to ₹9,000 / week. After area‑based routing, 85 % of jobs went to local technicians, saving ₹5,400 / week and allowing the firm to take on 30 % more jobs without hiring extra staff.

3. By Language – cultural conversion

How it works: The rule parses the incoming text for script (Devanagari, Tamil, Bengali) or keywords (“हिंदी में बात करें”). It then routes the chat to a rep fluent in that language.

Why it matters:

• Cuts the “translation lag” that adds 4‑6 minutes per message.
• Increases close rate for multilingual markets by 12‑15 %.
• Reduces churn because customers feel heard in their mother tongue, a factor that drives repeat purchases in Tier‑2/3 cities.

Real‑world example: An online grocery in Kochi started routing Malayalam‑speaking chats to a native rep. Conversion on those chats rose from 3 % to 4.8 %, adding ₹2.1 lakh in monthly revenue and lowering cart‑abandonment by 9 %.

Putting the rules together

Doggu lets you stack rules in priority order: Language → Area → Round‑Robin. If a Hindi lead from Lucknow arrives, it first checks for a Hindi‑speaking rep in Lucknow; if none, it falls back to the nearest Hindi‑speaking rep; if still none, the round‑robin pool picks the next available person. The result is a single, deterministic path for every lead, with no manual triage.

---

What doesn’t work

1. Manual “pick‑and‑assign” after hours

Many SMBs rely on a founder or admin to glance at the inbox every few hours and forward leads. The data shows 70 % of missed replies happen after 6 pm, when the admin is already offline. No amount of enthusiasm can fix a process that depends on human availability.

2. Separate tools with no integration

Using a WhatsApp API provider that dumps chats into a CSV, then uploading to a CRM manually, creates a time lag of 15‑30 minutes per batch. In a market where the average consumer expects a reply within 5 minutes, that delay kills conversion.

3. “One‑size‑fits‑all” routing

A single round‑robin rule works for a pure SaaS product, but it fails for a hybrid D2C + service business. For a Delhi‑based home‑appliance repair firm, sending a lead for a broken AC to a rep who only handles washing machines adds a ₹1,500 extra travel cost and a 2‑day delay.

4. Ignoring GST reconciliation

Some platforms claim “auto‑track sales for GST”. In practice they miss WhatsApp‑originated sales because the lead never entered the CRM. The result is a ₹4,800 extra CA fee each quarter.

5. Over‑reliance on a single language rule

If you route only by language and ignore area, a Tamil‑speaking lead from Chennai could be sent to a rep in Coimbatore who is 250 km away. The lead still gets a fast reply, but the field visit cost spikes. The rule set must consider both dimensions.

The takeaway: Automation without intelligence is just another manual step in disguise. You need rule‑based routing that respects language, geography, and capacity, and you need it inside a single platform that also handles payments, GST, and booking.

---

Cost / pricing in INR

Below is a side‑by‑side of typical spend on a fragmented stack versus an all‑in‑one with routing rules.

Stack component	Avg. monthly cost (₹)	# of tools	Total
WhatsApp API (WATI)	1,200	1	1,200
CRM (Zoho)	1,500	1	1,500
Booking calendar (Calendly)	800	1	800
Payments gateway (Razorpay)	300	1	300
GST add‑on (ClearTax)	600	1	600
Subtotal	4,400	5	₹4,400

Doggu (all‑in‑one)

Plan	Monthly price (₹)	Includes
Starter (up to 3 users)	999	WhatsApp API, CRM, booking, payments, GST auto‑calc, routing rules
Growth (up to 10 users)	1,799	All Starter + advanced routing (area, language), AI‑assist chat, analytics
Enterprise (custom)	3,499+	Unlimited users, dedicated support, custom integrations

Even the Starter plan is ₹3,401 cheaper than the fragmented stack, and it already gives you round‑robin, area, and language routing. For a typical founder with a ₹2,500 SaaS budget, the Growth plan fits comfortably while still leaving room for advertising spend.

Break‑even analysis (real numbers from a Pune physiotherapy clinic)

Metric	Before Doggu	After Doggu (Growth)
Monthly SaaS spend	₹4,400	₹1,799
Avg. leads per month	420	420
Leads responded <5 min	150	340
Conversions from fast replies	8 %	13 %
Additional revenue	—	₹3.2 lakh
Net profit increase	—	₹2.1 lakh

The ROI materialises in under two months for most SMBs that see at least 200 WhatsApp leads a week. The extra profit comes from three sources: higher close rate, lower travel cost, and reduced CA fees.

---

Frequently asked questions

How do I set up language detection for Hindi, Tamil, and English?

Doggu reads the Unicode block of each incoming message. If it detects Devanagari characters, it flags the lead as Hindi; if it sees Tamil script, it tags Tamil. You can also add keyword shortcuts like “ENG” or “HINDI”. The rule engine then routes to the rep whose profile lists that language.

What if a lead’s pin‑code isn’t recognized?

The system falls back to the nearest known area based on the first three digits of the pin‑code. If the prefix is completely unknown, the lead goes into the Round‑Robin pool so it never stalls.

Can I prioritize a senior rep for high‑value leads?

Yes. You can create a “Value‑Based” rule that checks the lead source (e.g., Facebook ad campaign with ₹10,000 daily budget) and routes those leads to a designated senior rep before any other rule runs.

Does routing affect my GST filing?

All sales that pass through Doggu’s payment gateway are automatically logged with the correct GST rate (5 %, 12 %, 18 % or 28 %). The daily export file can be uploaded to your CA, cutting the manual reconciliation time from 8 hours to 30 minutes per month.

Is there a limit to the number of routing rules?

The Growth plan supports up to 15 active rules (e.g., 5 language, 5 area, 5 custom). The Enterprise tier removes that cap and adds conditional logic (e.g., “If lead value > ₹50,000 AND language = Hindi → senior rep”).

What happens if all reps are offline?

Doggu can forward the message to a WhatsApp Business “unavailable” auto‑reply that promises a callback within the next 2 hours, while still logging the lead. When a rep logs back in, the oldest pending lead is assigned first, preserving FIFO (first‑in‑first‑out) fairness.

How accurate is the automatic pin‑code extraction?

Doggu uses a combination of regex patterns and AI‑assisted entity recognition. In a test of 10,000 real WhatsApp chats across 12 states, the extraction accuracy was 96.3 %. The remaining 3.7 % are flagged for manual review, preventing mis‑routing.

Can I combine rules with time‑of‑day logic?

Yes. You can add a “Shift” rule that only routes to reps who have marked themselves “on‑shift” between 9 am‑6 pm. Leads arriving after 6 pm are sent to the “after‑hours” pool, which triggers the auto‑reply mentioned above. This prevents overnight backlog.

Does Doggu support multi‑brand routing for franchise models?

The Enterprise plan lets you create brand‑specific rule sets. A franchisee can have its own language/area matrix while still sharing the same WhatsApp number, keeping brand identity intact and avoiding cross‑talk between competing outlets.

---