Quick question for RevOps folks: how do you know your lead routing actually worked yesterday? Not errors, I mean leads that just quietly didn’t get an owner or a follow-up. Do you check by hand, have a script, or find out from reps?
Reps will definitely let you know if something is wrong, but we use secondary flows that check things proactively:
A flow that checks that assignment happened 30 minutes after an MQL
A flow that checks that accounts followed a contact’s ownership change
A flow that alerts us if someone isn’t followed up on after 1 business day (and pings the rep assigned)
Also whenever we make changes, we spot check several records — there’s no substitute for human eyes on it
Adding to Paul’s point: I’d also watch the outcome side, not just the assignment. A lead can get an owner and still go quiet, so a simple daily view of “created yesterday, owned, but zero activity logged” catches the ones that look fine in routing. Median time to first touch is a good single number to trend too, because when routing quietly breaks it’s usually the first thing to drift.
Backing up both here:
Build a check loop into the playbook for any gaps in assignment rules
Build a check loop for gaps/delays into the actions needed, and measure how these change over time. If sales consistently misses the same things, maybe that step is in the wrong place vs sales not following a process
Good point on trending it over time. If the same gap keeps showing up week after week, it’s usually the handoff that’s wrong rather than the rep. Do you review those repeat misses with the team, or mostly watch the number?
This is super helpful, thanks all. Quick summary for anyone who finds this later:
Check owner assignment within ~30 min of MQL
Check ownership changes carried over to the account
Flag “owned but zero activity” after 1 business day
Trend median time to first touch, since it drifts first when routing breaks
If the same gap repeats week after week, fix the handoff, not the rep
Follow-up for Paul S.: who maintains those secondary flows, and have any of them ever quietly stopped working themselves? And does anything watch the steps outside HubSpot, like forms or enrichment before the lead lands?
On the steps before the lead lands: the quietest failures we’ve had were leads that never reached the CRM at all - a form webhook or an enrichment call failed, and nothing inside the CRM could show it. A daily count of form submissions vs new CRM records from that source catches it. If the numbers don’t match, you look before anyone asks where the leads went.
The longest one sat unnoticed overnight. The call from our site assistant into the CRM started failing, but the assistant still told the visitor “got your details”, so there was no error anywhere to see. We only caught it the next day, when the newest CRM record turned out to be older than the latest conversation. The daily count is automated now. The bigger fix was making the assistant wait for the CRM to confirm before it says anything was saved.
That's a great example akostiuk , thanks for sharing it. The assistant saying "got your details" while the write failed is the scariest version, because the visitor thinks they're done too. Comparing the newest CRM record with the latest conversation is a smart way to catch it. Mind if I DM you a couple more questions? I'm researching exactly this kind of break.
for the pre-crm part i’d log every form submit somewhere outside the crm (even just a sheet via webhook) and diff it against new crm records once a day. anything in the log with no matching record got dropped somewhere
