RedHub AIRedHub AI
Tool Gate · How it works

How the gate works

How the Speed-to-Lead Routing gate works

This tool grades an inbound-lead routing setup before you rely on it. It scores 6 weighted controls into a 0–100 number — then a gate that can only make the verdict worse.

The 6 weighted controls

01Instant acknowledgmentwt 22
02Assignment / ownershipwt 20
03Escalation if unclaimedwt 18
04After-hours coveragegate · at 0wt 15
05SLA defined & measuredwt 15
06Speed respects consentwt 10
PASS
score 75+
FIX
score 50+
BLOCK
below floor
Hard-block · worsen-only

Four setups get an automatic BLOCK regardless of the score: no after-hours path, an unowned inbox, a lead channel routing nowhere, or a fast first-touch that fires without consent. A great routing score can't save a setup that drops nights-and-weekends leads on the floor.

85/100
BLOCK

Why: Every routing rule is strong — score 85, a clear PASS on the numbers. But there's no after-hours coverage (0), and that's a hard-block gate: nights-and-weekends leads get no acknowledgment and no queue, so they're silently dropped. The verdict is forced to BLOCK regardless of the score.

Fix firstAfter-hours coverage — it's at 0. Nights-and-weekends leads get no acknowledgment and no queue, so they're dropped. Add an after-hours path before you rely on the routing at all.

A high score didn’t save it. The score is context; the gate is the answer — and it names the one thing to fix first. Grades the routing setup, not a person. 'Speed respects consent' is a readiness check, not legal advice — confirm consent and quiet-hours rules for your own outreach.