Route Leads to the Right Person in Your CRM

Write a small routing table that assigns each type of inquiry to a named role, add a fallback queue for anything that does not match, name a coverage owner for absences, and set an escalation timer your business chooses. Test the rules with sample leads before turning them on. Routing is a set of business decisions first; the CRM only carries them out.

Why routing breaks

Leads usually go missing in small businesses for ordinary reasons: the person who handles quotes is on vacation, a new service was added without updating anyone's inbox, or an inquiry does not fit any category and sits unread. Routing rules fix this by making the decisions explicit.

Step 1: the routing decision table

Keep it short. Three to six rows are enough for most small teams.

If the inquiry is about	And	Route to	Backup
New residential quote	Inside service area	Estimator	Office manager
New commercial quote	Any	Owner	Estimator
Existing customer issue	Any	Office manager	Owner
Partnership or vendor pitch	Any	General inbox, low priority	None
Anything else		Fallback queue	Office manager

Use roles rather than personal names so the table survives staff changes. Keep a separate list of who currently fills each role.

Step 2: the fallback queue

Every routing system needs a place for inquiries that match no rule. The fallback queue is checked by a named person on a schedule you set. Its contents also show where your rules are incomplete. If the same kind of inquiry keeps landing there, add a row.

Step 3: coverage owner

Decide who covers each role when that person is away, and how coverage is switched on. Some teams update routing manually before a vacation; others use shared queues. Whatever the method, write it down and test it once.

Step 4: escalation timer

Choose how long an inquiry may sit unacknowledged before someone else is alerted. The right number depends on your business. A restaurant catering inquiry might need attention within hours; a B2B partnership inquiry can wait longer. The timer should trigger a notification to the backup, not an automated message that promises something to the customer.

Hypothetical example: a two-location cleaning company

A fictional cleaning company serves two towns and has three staff who handle inquiries. Before routing, all web leads went to the owner's email. After mapping, they route residential quotes by town to each location lead, commercial quotes to the owner, and anything else to a shared queue the office manager checks twice a day. They set a business-hours escalation timer that alerts the owner if a new quote is not acknowledged. During testing they discover that leads without a town field went nowhere, so they make the field required with a clear label and send unmatched ones to the fallback queue. For multiple locations or countries, see routing Florida and Jamaica inquiries.

Implementing in your CRM

Most CRMs support some form of assignment rules, round-robin, queues or workflow automation, but features and plan limits differ widely. Check your own CRM's documentation for how it assigns records and what happens when a rule fails. Avoid building rules that depend on a feature your plan does not include. Source: HubSpot Knowledge Base: Deduplication of records.

Test before switching on

Create one sample lead per row, using made-up details.
Confirm each lands with the correct role and backup.
Submit a lead that matches no rule; confirm it reaches the fallback queue.
Simulate an absence; confirm coverage works.
Leave a test lead unacknowledged; confirm the escalation alert fires.
Check that duplicates are not created; see preventing duplicate leads.

Frequently asked questions

Should AI decide the routing?

AI can help classify messy inquiries, but the routing table itself should be a business decision. If AI suggests a category, route uncertain cases to the fallback queue rather than guessing.

How often should rules change?

Review them when you add a service, a location or a team member, and whenever the fallback queue fills with the same kind of inquiry.

What about after-hours leads?

Decide whether they wait for the next business day or go to an on-call role, and tell customers honestly what to expect in the confirmation message.

Next step

Draft your routing table with roles and backups. Rithm's AI marketing automation work often starts with this exact table, or send us your draft for feedback.

Sources and further reading

HubSpot Knowledge Base: Deduplication of records, relevant when routed leads may already exist in the CRM.

Editorial note: this planning guide was drafted with AI assistance for Rithm Digital and created on September 25, 2026. Examples are hypothetical. It is general marketing-operations guidance, not legal, medical, tax or financial advice. Prices refer only to Rithm's published Small Business Launch & Growth offer.