A lead is owned by the one person whose name is on it, and nobody else. In a small team the simplest way to get there is a shared queue: new enquiries land in a queue the whole team can see, and the first person free claims one, which puts their name on it. From then on that person replies, follows up and either moves it forward or hands it back on purpose.
Why “the team owns it” means nobody does
Picture a shared inbox at a four-person firm. An enquiry arrives at 10:40. Everyone sees it. Everyone also sees that everyone else can see it, so each person quietly assumes someone with more context will pick it up. At 16:00 it is still sitting there, read by all and answered by none.
Psychologists call this diffusion of responsibility: the more people who could act, the less each one feels it is theirs to do. Nobody is being lazy. The problem is that the enquiry never had a name on it.
A lead with an owner fixes that, because “is anyone on this?” becomes a question with a yes or no answer.
Two ways to give a lead an owner
Assign it. Someone, usually whoever runs the day, reads each new enquiry and puts a person’s name on it. This works when one person is reliably around to do the sorting, and it lets you match enquiries to the right person (the plumber gets the boiler job, the partner gets the big contract).
Queue it. New enquiries go into a shared queue. Anyone in the queue can claim one, and claiming it makes them the owner. This works when the team is small, everyone can handle most enquiries, and you do not want sorting to wait on one person’s calendar.
Most small teams end up with a mix: a queue for general enquiries, and a direct owner for anything from an existing customer, which goes to whoever already looks after them.
How a shared queue works, step by step
- Make one queue per kind of work. “New enquiries” is enough to start. Add a second only when there is a real split, such as sales and support.
- Add the people who can take that work. A queue is a list of members, not a department. Someone can belong to more than one.
- Send new leads to the queue. The lead’s owner is the queue, not a person, until somebody claims it.
- Claim, then act. A member opens the lead and claims it. Their name replaces the queue as owner, and the next step is now theirs.
- Hand back on purpose. If the owner cannot take it forward (wrong specialism, going on leave), they release it to a queue rather than letting it sit under their name.
Rules that keep a queue honest
A queue only works if it is short. A few house rules help:
- Nothing sits in the queue overnight. Whatever is left at the end of the day gets claimed by somebody before they log off.
- Claim means reply. Claiming a lead and then not touching it is worse than leaving it, because it now looks handled. If you claim it, you send the first reply.
- Release, never abandon. If a lead is not right for you, put it back in the queue with a note on why, so the next person does not start from zero.
- One owner at a time. Two people “keeping an eye on” a lead is the shared inbox problem again, just smaller.
How this works in GuardenerAI
An admin creates queues, adds members and picks which kinds of records each queue can hold, leads included. On any lead, the Owner can be a person or a queue. When a lead is owned by a queue you belong to, an Accept button appears on it; clicking it makes you the owner. Only one person can win a claim, so two people clicking at once never both end up owning it. The owner of a lead sees Release to queue, which hands it back to a queue of their choice, and each change of owner shows in the lead’s Activity history.
When someone leaves or a queue is being retired, an admin can use Reassign all to move everything a queue holds to a person or another queue in one go.
The honest limits: GuardenerAI does not assign leads automatically or share them out in turn, and nobody gets an alert when a lead lands in a queue. Leads that arrive from your website form start with no owner at all, so someone needs to send them to the queue or to a person. Build that into the day: check new leads at fixed times and claim or route each one.
Measure it with two questions
Once a week, look at the leads that came in and ask:
- How many had no owner for more than a working day? That is your queue leaking.
- How many were claimed but got no reply the same day? That is “claim means reply” slipping.
You do not need a report for this. Last week’s leads and five minutes on a Friday is enough to see where things stall.
This TEDx talk is about the idea behind the shared inbox problem.
Frequently asked questions
Should the business owner own every lead in a small firm? Only if they also have the time to reply to every one within the hour. If they do not, a queue lets the rest of the team pick up enquiries while the owner keeps the ones that need them.
Is round-robin better than a queue? Taking turns spreads the work evenly but ignores who is actually free right now. In a team of three to ten people, a queue where whoever is free claims the next enquiry is usually faster.
What happens to the lead after it is claimed? The owner replies, qualifies it and either turns it into a customer or marks it lost. For the reply itself, see how fast to reply to an enquiry; for deciding which leads are worth the most time, see what lead qualification is. Our speed-to-lead playbook has a follow-up cadence for after that first reply.
Written with these teams in mind: field services , healthcare practices , professional services .