Who Owns This Lead? Routing Rules That Stop Fall-Through

Who owns this lead? One person, named, the moment it lands

A plumber's phone buzzes early with a Facebook message about a burst pipe. Nobody replies. Both partners glanced at it, both assumed the other had it, and by mid-morning the job's booked with a rival. That's not a people problem. That's a routing problem.

Here's the fix in one line: every enquiry gets one named owner the instant it arrives, a clock starts, and if that owner goes quiet the lead escalates to someone else. No shared-inbox limbo. No 'I thought you had it'.

This post gives you the routing framework — the single-owner rule, first-touch versus round-robin, a written response-time target, and what escalates when it's missed.

Key takeaways

• One owner per lead — assign it on arrival so nobody assumes someone else replied.
• First-touch or round-robin — pick one on purpose for your team size.
• Written response target — a real, measurable window, not 'as soon as we can'.
• Auto-escalation — the lead moves the second the target is missed.

Why a shared inbox quietly loses jobs

A shared inbox loses jobs because there's no record of who looked. Three people can open the same enquiry, each assume a teammate is handling it, and the lead sits unanswered until the customer books elsewhere.

The mechanical failure is diffusion of responsibility. When a task belongs to everyone, it belongs to no one. A group chat, a shared Gmail and a Facebook page checked 'when someone gets a sec' all fail the same way.

Assign ownership and the maths changes. The moment a name is stamped on the lead, one person is accountable — and everyone else knows to leave it alone unless it escalates.

Speed matters here too, because the first business to reply usually wins the callback. We wrote about that in the 60-second rule on speed-to-lead, and it only works if someone actually owns the reply.

First-touch or round-robin: which suits a two-person team?

For a two-person team, use first-touch ownership: whoever replies first owns the lead, and the system locks it to them so the second person doesn't double-handle it. It's the simplest rule that stops the 'you call them / no you call them' loop.

Round-robin — where leads take turns across staff automatically — earns its keep once you've got three or more people who can all quote. It spreads the load evenly and stops one person hoarding the easy jobs.

Here's what we'd do:

• Solo or two-person: first-touch, with a hard rule that the owner is locked in on first reply.
• Three to ten people: round-robin by role or service type, so a bathroom reno doesn't land with the person who only does maintenance calls.
• Territory-based teams: route by suburb or postcode first, then round-robin inside that patch.

Don't overthink it. A rule you'll actually follow beats a clever one you won't.

Write a response-time target you can measure

Set a clear response window and put it in writing: 'Every new enquiry gets a first reply promptly during business hours.' A target you can't measure is a wish, not a target — so pick a window your team can actually hit and hold each other to it.

Split it by hours. Business hours might be a quick first reply. After-hours can be an automatic acknowledgement now — 'Got your message, we'll confirm first thing' — and a human reply first thing in the morning.

The acknowledgement buys you time and stops the customer shopping around. It's the difference between a lead that waits and a lead that rings the next name on Google.

Map your enquiry channels to owners and targets:

• Phone → missed calls auto-text back straight away, owner assigned.
• Web form → owner assigned by service type, with a set reply window.
• Facebook / Instagram DMs → owner assigned, same window.
• Google Business Profile messages → owner assigned, same window.

If a missed call is where you leak most, auto-texting back before they ring a rival plugs the biggest hole first.

What escalates when the target is missed

Escalation is the safety net: if the owner hasn't replied inside the target window, the lead automatically reassigns and pings a backup. This is the single rule that turns a good intention into a system.

Without it, a target is just a number nobody enforces. With it, a lead that's been sitting too long stops being one person's problem and becomes the team's.

Build the ladder:

1. Owner assigned, clock starts.
2. Reminder to the owner at the halfway point of the target window.
3. Reassign to a backup when the target's blown, with a notification.
4. Flag to the owner/manager if the backup misses too.

Escalation also fixes the after-hours gap. The lead that came in late isn't forgotten — it's queued, acknowledged and owned by the time the first person's on the tools.

This is the same discipline that stops deals dying mid-pipeline. If yours vanish after the quote, finding where your pipeline leaks and automating the quote follow-up close the two most common gaps.

Don't stop at the first reply

Ownership doesn't end at 'hello'. The owner carries the lead through to booked or lost, so there's always one person accountable for the next step — the quote, the follow-up, the confirmation.

A lead that isn't ready to book yet still needs an owner and a plan. That's what a 90-day nurture plan for the lead who isn't ready is for — keeping the enquiry warm without anyone having to remember to chase it.

The result? Fewer enquiries lost to silence, and a clear answer every time to the question that started this: who owns this lead.

How IgniteOS does this for you

IgniteOS puts every enquiry — phone, web form, Facebook, Instagram, Google — into one shared inbox where each lead gets a named owner the moment it lands, so nobody assumes someone else replied.

Automations run the routing for you: assign by channel, service type or territory, start the response-time clock, remind the owner, then reassign to a backup the second the target's missed. Missed calls auto-text back and land as an owned lead, not a voicemail nobody checks.

Start with the automate follow-up page to see the routing and escalation in action. Prefer to see what a fragmented tool stack is quietly costing you first? Our calculator puts a typical replaced stack at about $18,000 a year. When you're ready, the 14-day free trial includes free migration and a setup session — no per-seat fees, cancel anytime.

Frequently asked questions

What is a lead management process?

A lead management process is the set of rules that decide who handles each enquiry, how fast they must reply, and what happens if they don't. At its core it's three things: one named owner per lead, a written response-time target, and an automatic escalation that reassigns the lead the moment the target is missed.

Why does a shared inbox lose leads?

A shared inbox loses leads because there's no record of who looked. Several people open the same enquiry, each assumes a teammate is replying, and the lead sits until the customer books elsewhere. Assigning one named owner the instant a lead arrives removes the ambiguity — one person is accountable, everyone else leaves it alone unless it escalates.

Should a small team use first-touch or round-robin routing?

Use first-touch for a solo or two-person team: whoever replies first owns the lead, locked in so nobody double-handles it. Switch to round-robin once three or more people can all quote — it spreads leads evenly and stops one person hoarding easy jobs. You can see both set up on our automate follow-up page.

What response time should you set for new enquiries?

Set a clear window and write it down — a quick first reply during business hours works well. After hours, send an automatic acknowledgement now and a human reply first thing in the morning. The exact figure matters less than making it measurable and adding an escalation that reassigns the lead the moment the target is missed.