
TL;DR
- Lead routing decides who or what handles a new lead next. Most routing still runs on form fields and rep rotation, so the decision is made before anyone knows what the buyer actually wants.
- Rules-based routing breaks in four places. The form field is stale, the owner is offline, intent changes mid-conversation, and every lead lands in the sales queue.
- Zigment flips the order. An AI agent answers first, reads intent, urgency and sentiment from the conversation, writes that read to the CRM, then routes on it inside rules your team sets.
- Whoever receives the lead gets the whole thread, the intent read and the recommended next step, so nobody asks the customer the same question twice.
- Measure time to first reply, the share of handoffs that arrive with context, re-qualification rate and qualified-to-booked conversion. Round robin fairness tells you very little.
Firms that tried to contact a new lead within an hour were nearly seven times as likely to qualify it as firms that waited longer. That was the finding of a Harvard Business Review audit of 2,241 US companies in 2011, and most lead routing setups still lose that hour in the queue.
Lead routing is the process of deciding who or what handles a new lead next, whether that is a rep, a team, a branch, a dealership or an AI agent, and what context travels with it. Good lead routing matches each lead to the owner most likely to convert it, fast enough that the buyer is still interested when the reply lands.
This post walks through how Zigment routes a lead end to end, from the first message to the moment a salesperson opens the record. One scenario, every step, no abstractions.
How does traditional lead routing work?
Traditional lead routing reads a handful of fields from a form or an enrichment tool, then applies assignment rules in a fixed order. The rules are usually some mix of the four patterns below, and many RevOps teams run several of them at once.
| Routing method | What it reads | Where it goes | Where it struggles |
|---|---|---|---|
| Round robin | Nothing about the lead | The next rep in the rotation | Treats a ready buyer and a student the same |
| Territory or geography | Country, state, postcode | The rep or branch that owns the region | Breaks when the buyer types a city the form did not expect |
| Account-based | Company domain matched to an account | The existing account owner | Depends on clean lead-to-account matching |
| Score threshold | Points from form fields and page views | Sales above the line, nurture below it | A score built on clicks guesses at intent |
Every method in that table shares one assumption. The form tells you what the buyer needs. In conversational channels such as WhatsApp, web chat and Instagram, that assumption rarely holds, because the buyer explains what they want in their own words after the form is long gone.
Routing rules can only be as good as the fields they read, and form fields capture the least useful moment of the buyer's intent.
Where does rules-based lead routing break?
Rules-based lead routing breaks wherever the real buying signal lives outside a structured field. Four failure points come up again and again.
The form field is stale
A buyer picks "General enquiry" from a dropdown, then writes three messages about a specific car loan amount and a purchase date next month. The rule reads the dropdown. The intent sits in the chat transcript, unread by anything that assigns owners.
The owner is offline
Rotation assumes the next rep is available. A lead that arrives at 10:40 pm gets an owner on time and a reply the next morning.
Drift's secret-shopper test of 433 B2B companies found that only 7% replied within five minutes and 55% had not replied after five business days (Drift, 2017). Chili Piper's 2022 research put the share of B2B companies taking longer than an hour to answer a demo request at about 55%, with nearly 30% never answering at all (Chili Piper).
Intent changes mid-conversation
A patient who asks about consultation fees on Monday may ask about a second opinion and next week's slots on Wednesday. Static routing fires once, at creation. The lead keeps its day-one owner, even after its intent has moved.
Every lead enters the sales queue
Existing customers with a service question, applicants chasing a document and people who will never buy all enter the same queue. Reps spend their first minute on each one working out what it is. That minute, multiplied across a quarter, is the hidden cost of routing before you know what the lead is.
We covered the case for retiring the rotation itself in why agents should just work the lead. This post is the mechanism.
How does Zigment route a lead? A walkthrough
Zigment routes a lead once the conversation has started and the buyer has said what they want. An AI agent answers first, reads what the buyer says, writes that read into the CRM, and only then decides where the lead goes, inside rules the team has set once.
Most automated lead routing speeds up the rotation. Zigment changes the input the rotation reads, which is the conversation itself.
Here is that sequence for one automotive enquiry. Megan Carter sees a click-to-WhatsApp ad for a compact SUV and messages the dealer group at 10:40 pm on a Thursday.
- The agent answers in seconds. Zigment's agents engage the moment a lead arrives and qualify in the customer's own language, on whichever channel the buyer picked. Megan gets a reply while she is still holding her phone.
- The conversation captures the signals. Over a few messages, the agent captures model, budget, city, finance status, timeline and whether she has a car to exchange. The agent scores every message for intent, sentiment and urgency as it happens.
- The read lands in the CRM as fields. Zigment writes intent, objection, product interest and next best action back to the CRM record as structured data, in the fields the team already uses. A RevOps lead can sort, report and build on them like any other property.
- Zigment decides the route against your rules. Intent, model, location, finance status and exchange interest route Megan to the nearest dealership, with the whole conversation attached.
- The booking happens in the same thread. Megan already asked for a test drive, so she skips straight to booking. The agent confirms the slot, dealership and date in the thread against the dealer's live calendar, with a reminder before the visit.
- The salesperson opens the full thread. On Saturday morning, the dealership salesperson opens the record and sees what Megan wants, what she can spend and what she is trading in. Nobody asks her what she is looking for twice.
What makes step four possible is the Conversation Graph, Zigment's per-customer timeline of every conversation, form, click and call, with the meaning read from each one. The router reads that timeline instead of a single form. If Megan messages again next week on Instagram, the same thread continues and the same memory travels with it.
The routing decision should read what the buyer actually said.

Where does each kind of lead go?
Each lead goes where its intent says it should, and the destination is set by the rules your team writes. The table below shows the common routes for intent-led lead routing, using the patterns Zigment runs across automotive, banking and healthcare.
| What the conversation shows | Where it routes | What travels with it |
|---|---|---|
| Ready to act, slot requested | Booked directly against the live calendar | Confirmation and reminders in the same thread |
| Qualified, needs a local owner | Nearest dealership, branch or the right team | The whole conversation, not a summary |
| High value or frustrated | A rep, at the escalation threshold you set | Full thread, intent read, recommended next step |
| Compliance or clinical line in view | A licensed advisor or clinician, by policy | The whole conversation so nobody starts again |
| Interested, not ready, or gone quiet | Stays with the agent on the same thread | Follow-ups that adjust to what the lead said |
The last row matters most to RevOps. A lead that is not ready does not need an owner yet. It needs someone to keep the conversation going.
The agent does that on the same thread until the intent changes. When it does, the route changes with it. As one of Zigment's own product pages puts it, a hesitant buyer and a ready one hit the same rules and come out on different journeys.
Banking applicants reach the right lending team
Ethan Brooks taps an ad for a personal loan. The agent qualifies budget, product and intent inside the conversation instead of on a form, then hands the qualified applicant to the right team with the full transcript. When a licensed advisor is needed, the advisor gets the whole conversation rather than a summary, and branch visits or advisor slots are booked against the live calendar.
Healthcare cases reach the right clinician
Laura Bennett asks a fertility clinic about treatment options at midnight. The agent reads mood and urgency, answers from the clinic's approved clinical content, books the consultation when the intent is real, and routes the case to the right clinician the moment it crosses the line that needs one.
Intent-led lead routing sends each conversation to the destination its content earns, and keeps working the ones that have not earned one yet.
What does RevOps configure, and what runs on its own?
RevOps configures the rules once and the agents run the routing on their own inside them. That split is what AI for RevOps looks like in practice.
Your team writes Zigment's guardrails in plain English, covering thresholds, escalation paths and topics the agent will not touch. The agent acts freely inside those rules and never outside them.
- Rules and thresholds. You set when a thread escalates, for example when intent is high-value and sentiment turns frustrated. You can change a rule on a Tuesday afternoon without filing a ticket.
- Destinations. Teams, branches, dealerships, clinicians and calendars are the targets your rules point at. Zigment books slots, writes to the CRM and pings the right rep as actions inside the same conversation.
- Audit. Zigment logs and timestamps every signal, branch and action, and you can replay each one with the reasoning attached. When a sales manager asks why a lead went where it went, the answer is a lookup.
- Systems of record. Your CRM, calendar and other systems stay the source of truth, read and written live. Zigment sits on top of HubSpot and Salesforce, and also connects to Zoho CRM, LeadSquared and Bitrix24, with 60+ connectors and your own APIs as private apps.
Zigment is a Conversational Revenue Orchestration Platform for HubSpot and Salesforce stacks, so routing is one of several actions it orchestrates from the same conversation. The same read that picks the dealership also books the test drive, updates the CRM and schedules the follow-up. If you are weighing where that layer fits next to your router and CRM, our breakdown of the 2026 RevOps stack maps it out.
Lead routing best practices for RevOps teams
The best lead routing practices put the conversation before the assignment and the reason next to every route. Whether you run Zigment or another tool, these six hold up.
- Check account ownership first. An existing customer or an owned account should reach the person who knows the relationship before any rotation or territory rule fires.
- Engage before you route. Reply to every lead within minutes on the channel it came from, then route once you know what it is.
- Route on the intent the buyer states. What the buyer typed about budget, timeline and product beats the field they picked to get past the form. Our guide to scoring leads from conversation data covers the signal side.
- Send the thread with the lead. A handoff without the conversation forces the rep to re-qualify, which costs the buyer's patience and the rep's first minute.
- Write the route reason to the CRM. Store the intent read and the rule that fired on the record, so disputes become lookups and broken rules show up in reports.
- Re-route when intent changes. A lead's owner should follow its intent. Static assignment at creation is the single biggest source of stale ownership.
Which metrics show lead routing is working?
Lead routing is working when buyers get a fast first reply and owners receive leads they do not have to re-qualify. Track these five numbers before and after any change.
- Time to first reply, by channel and hour of day. The after-hours number is the honest one. Our roundup of speed to lead statistics shows which benchmarks hold up.
- Context-attached handoff rate, the share of routed leads that arrive with the conversation and intent read on the record.
- Re-qualification rate, how often the receiving owner has to ask the buyer questions the buyer already answered.
- Reassignment rate, how often a lead changes owner after the first route. High rates point at rules reading the wrong signals.
- Qualified-to-booked conversion, the rate at which routed, qualified leads turn into a booked meeting, test drive, visit or consultation.
On the outcome side, Zigment's published figures across customers are around 40% higher conversion from inbound demand and up to 80% less manual effort on lead handling. In one deployment, a global two-wheeler maker running across more than 20 countries cut its cost per qualified lead by 45% and doubled qualified lead volume.
The route was never the hard part
Assignment rules are easy to write. Knowing what a lead wants before you assign it is the part most stacks skip, and it is why the fastest rotation in the world still hands reps strangers. When the conversation comes first, the route mostly decides itself.
So here is the question worth taking to your next pipeline review. How many of last month's leads reached their owner with the buyer's own words attached? See how Zigment routes leads on intent for RevOps teams.