Team lead follow up

Team lead follow-up fails differently than solo follow-up. A solo agent drops leads from overload; a team drops them from diffusion — four capable people each assuming someone else has it, a report that says “contacted” meaning one text nine days ago, and no single throat to choke when the lead closes with a competitor. The fix is not more enthusiasm at the Monday meeting. It is a structure with three parts: one owner per lead, an automated base layer nobody has to remember, and cadence numbers someone actually reads.

Why shared leads die

Psychologists call it diffusion of responsibility; team leads experience it as the lead everyone saw and nobody called. Shared visibility without assigned ownership creates a bystander pipeline — and layering more people onto it makes it worse, because each addition lowers everyone else’s felt obligation. The failure hides well, too: activity exists, dashboards show motion, and only a cohort question — of last month’s leads, how many got a fifth touch? — exposes the rot. Teams routinely respond by buying more leads, which scales the leak rather than the revenue. The tell is in the language your meetings use: if reports say “we reached out” instead of a name, a date and a next step, ownership is already ambient, and ambient ownership is none.

The single-ownership rule

Every lead has exactly one owner at every moment, assigned by your routing rules within seconds of arrival, with two clocks attached: a response SLA, and a reassignment trigger that moves a neglected lead to a new owner with its history intact. Ownership is what makes follow-up auditable — “did we follow up” becomes “did Priya follow up,” a question with an answer and a lesson. Note the asymmetry that trips teams: visibility should be shared while ownership stays singular. Everyone can see every thread; one name is accountable for moving it. And write the reassignment rule down before you need it, including what the losing agent hears and when — a lead quietly taken back without a stated trigger reads as punishment, while the same transfer under a published SLA reads as the system working.

Automation is the floor, not the ceiling

Under the human layer, run the mechanical one: an instant first response the moment a lead lands, then nurture sequences that keep honest, useful touches flowing over the weeks a lead spends deciding. In Canada that layer must be consent-aware from capture — which messages a contact may receive is a data question, and the CASL machinery should enforce it without an agent thinking about it. What automation must not do is impersonate diligence: sequences buy coverage and surface intent, and the moment a contact re-engages, a human owns the next move. The division of labour — and when a paid human caller enters it — is the subject of ISA vs automation.

Cadence, measured

How many touches, how fast, for how long has an evidence base — our follow-up cadence answer covers it — but a team only needs three numbers watched weekly: median first-response time, share of open leads with a next action scheduled, and touches per lead in the first two weeks. In BrokerFold’s CRM those fall out of normal work, because the touches happen where the record lives: nurture runs from the platform, Gmail sync lands email on the contact, push notifications chase the SLA, and each contact’s behaviour timeline shows the listing views and searches that mean call now. Follow-up stops being a virtue the team hopes for and becomes a system the team reads.