The fastest way to lose a lead is to let it sit. A web inquiry lands in a shared inbox, everyone assumes someone else has it, and by the time anyone calls back the prospect has signed with whoever answered first.
The fix isn't working harder. It's a small amount of setup that decides, the moment a lead arrives, who owns it and what happens next. This guide walks through that setup step by step. It takes about an hour and works for teams of two as well as twenty.
Step 1: Get every lead into one place
Routing only works if leads arrive in the CRM, not in someone's inbox. Close the gaps:
- Website forms should post straight into the CRM as new leads. In Colurian, a web-to-lead form creates the lead directly from your website and records where it came from.
- Spreadsheets and event lists should be imported, not forwarded. Duplicate detection stops the same person from showing up twice.
- Phone and walk-in inquiries should be entered as leads by whoever takes them, even if the record has only a name and a number.
Add a Lead Source value to every path (website, referral, event, phone) so you can route and report on it later.
Step 2: Decide your routing logic on paper first
Before touching any settings, write down who should get what. Most small teams route on one or two things:
- Territory: state, region or country
- Product or service line: the type of work the lead is asking about
- Size: number of employees or estimated deal size
- Source: partner referrals to the partner manager, everything else to the general queue
Keep it short. Three or four rules that everyone understands beat fifteen that nobody can explain. And always decide who gets the leads that don't match anything. That catch-all is the most important rule you'll write.
A typical small-team plan looks like this:
| Priority | If the lead... | Assign to |
|---|---|---|
| 1 | Lead Source is Partner Referral | Partner manager |
| 2 | State is CA, OR or WA | West coast rep |
| 3 | Industry is Healthcare | Healthcare specialist |
| 4 | Anything else | Sales lead |
Step 3: Turn the plan into rules
In Colurian, simple routing is done with assignment rules: one rule per row of your plan. A few things to know about how they work:
- Rules run when a record is created, not when it's edited later, so changing a lead's details next week won't reassign it.
- They're checked in priority order and the first match wins. Put the most specific rules first (low numbers) and the broad ones last.
- Each rule can have up to three conditions, and all of them must match.
- A rule with no conditions matches everything. Give it the highest priority number, so it only catches what the other rules didn't.
- Each rule assigns to one person. If two people share a territory, split it with another condition.
Assignment rules test a set list of fields on each object. On leads that includes status, company, email and the event you met them at; on your own custom objects, any picklist, checkbox or text field. That makes them a good fit for routing cases, matters or applications as well as leads.
When your plan depends on something a rule can't test, like the lead source, the state or a list of states, build it as a record-triggered flow instead: it runs when a lead is created, checks each row of your plan in order, and acts on the first match. The plan on paper stays exactly the same.
Step 4: Make sure someone acts on it
Owning a lead isn't the same as calling it. Add one automation that turns a new assignment into a task:
- Create a flow that runs when a lead is created.
- Have it create a task for the lead's owner: "Call new lead", due today.
- Optionally send a templated email to the lead, acknowledging the inquiry and saying who will be in touch.
Now every new lead has an owner, a due date, and a confirmation the prospect actually received.
Step 5: Test it before it goes live
Make a few fake leads that should hit each rule, plus one that should hit the catch-all, and check that each lands with the right person and creates its task. If you use a sandbox, build and test the rules there first, then deploy them to production.
Then delete the test leads, so they don't skew your reports.
Step 6: Watch the numbers for a month
Build one small report and check it weekly:
- New leads by owner, to see whether the load is fair
- Leads with no activity after 48 hours, the ones slipping through
- Leads by source and conversion rate, to see which channels are worth more time
If one person is drowning, adjust a condition. If the catch-all is getting half the leads, your rules are too narrow.
Common mistakes
- No catch-all rule. Leads that match nothing stay with whoever created them, which for web forms is often nobody useful.
- Routing on fields people don't fill in. If half your leads have no state, routing by state will send them all to the catch-all. Make the field required on the web form.
- Too many rules. If you can't explain the routing in a sentence, simplify it.
- No follow-up task. Assignment without a next step is just a different inbox.
The short version
Get every lead into the CRM, write your routing on paper, turn it into a few priority-ordered rules with a catch-all at the end, and attach a follow-up task to every new lead. An hour of setup, and no inquiry waits on someone noticing it.
Want to see it on your own leads? Book a 30-minute demo and we'll set up your first routing rules on the call.
