Google Forms lead routing calculator
Estimate how much revenue slow lead routing may be costing you. Monthly leads, average value, response delay, missed-lead %, team size — out comes missed revenue, response-time risk, recommended routing rules, and a suggested Slack channel structure. Different lens from the response time calculator: that one models speed, this one models lead distribution and leakage.
Honest guesses are fine. The result updates as you tune the inputs.
How many form submissions arrive per month.
Revenue per closed lead. Use LTV for subscription products.
Submission → first human touch today. Most teams underestimate this.
Share of leads that go cold or get dropped today, wrong queue, missed notification, weekend submissions, the inbox-full problem.
How much of today's leakage instant Slack routing would catch. 70-90% is typical when the right person sees the lead in real time.
per month — 50 leads leaking through at the current setup.
That's $300,000 per year of revenue you don't realise is missing.
from 40 leads instant Slack routing would catch.
Annualised, that's $240,000 back on the table.
down from 1 hr today.
Well below the 30-minute drop-off.
leads instant routing won't catch on its own, usually downstream qualification or follow-up issues, not the notification layer.
What's left to fix after the routing wiring is solid.
Model: today's leakage = monthly leads × missed-lead %. Routing improvement % is the share of that leakage instant Slack routing eliminates. Numbers are estimates for prioritising the work, they don't replace measuring your actual funnel.
Why this is a different question from 'how fast can we be?'
The response time calculator asks: what if every lead got contacted faster?The conversion multipliers from the HBR 5-minute study drive the math. The output is — given your current speed and close rate — the additional revenue from going faster.
This calculator asks a complementary question: what about the leads we never contact at all?The submissions that arrive on a Sunday, the high-budget enquiry that lands in a junior rep's inbox while they're on PTO, the support ticket that fans out via shared email and gets silently dropped. Speed doesn't fix any of those — routing does.
Most teams have both problems. Use the response time calculator for the speed lens; use this one for the leakage lens. They add up, but they don't overlap.
What instant Slack routing actually prevents
- Submissions in a shared inbox. A form posts to
leads@; six people see it, none of them are sure they're the owner. The lead sits. Routing names the owner before the submission is even read. - Weekend / off-hours leads.Submissions arriving Friday at 7pm don't get human attention until Monday at 9am — 60+ hours of intent decay. Instant Slack routing puts a notification in front of someone who's on-call (or a subteam ping where any member can grab it).
- Wrong-segment routing.A VIP enterprise lead lands in the same queue as a hobbyist enquiry. Both wait the same amount of time. Conditional rules send the VIP straight to a senior rep's channel and let the hobbyist follow the standard cadence.
- Silent delivery failures. Hand-rolled scripts or Zaps that break quietly mean the lead never reaches Slack at all. A delivery log + failed-streak alerts surface the gap before it stacks up for weeks.
What each number is for
- Currently missed— the size of the problem at today's setup. Use it to build the business case for the work.
- Recovered with routing— the realistic upside. This is the number to compare against the cost of any routing tool you're evaluating.
- Response time after routing— orientation, not precision. Use the response time calculator if response speed is your actual focus.
- Residual leakage— what routing won't solve. Often points at downstream problems: qualification, follow-up discipline, the team being short-staffed. Worth naming before declaring victory on the routing project.
Lightweight lead routing for teams using Google Forms
Most lead distribution software is built around Salesforce, sales-ops teams, territories, and complex CRM workflows. For teams that still capture leads through Google Forms, that's overkill — what you actually need is the response in the right Slack channel before the lead goes cold.
- Route by budget, service, location, urgency, or lead type, without building a CRM workflow.
- Send each lead to the right Slack channel using IF-THEN rules — first match wins, with a fallback channel for everything else.
- Keep delivery logs and retry failuresso a Slack outage or a wrong channel name doesn't silently drop revenue.
- No Apps Script to maintain. The routing rules live in a dashboard, not in a script your last engineer wrote.
- Fallback channels and owner / team assignment are built in — every rule can target a person, a sub-team, or a channel, and unmatched leads still land somewhere.
The recovered-revenue number this calculator shows is achievable when leads land in the right Slack channel within seconds of submission. Use the Lead Routing Rules Generator to draft the rule set that gets you there.
Frequently asked questions
What does this calculator estimate?▾
The dollar value of leads that go cold because nobody saw the submission in time, and how much of that loss instant Slack routing would recover. The model is simple: today's leakage = monthly leads × missed-lead %, recovery = that leakage × the routing improvement %. The output is monthly and annualised loss and recovery numbers, plus a projected response time.
How is this different from the lead response time calculator?▾
Different lens on the same problem. The response time calculator asks 'what if every lead got contacted faster?', it uses conversion-rate multipliers from HBR's 5-minute window data. This calculator asks 'what if no lead got dropped at all?', it works from a missed-lead percentage you enter. Teams whose problem is slow follow-up should use the response time tool; teams whose problem is leads landing in the wrong inbox or arriving on weekends should use this one.
How do I estimate my missed-lead percentage honestly?▾
Three rough proxies, pick the one that's easiest. (1) Audit a week of submissions and count how many got a same-day response, the inverse is your leak rate. (2) Compare form submissions to deals booked in your CRM over the same window; the unexplained gap is leakage. (3) Survey your sales team for a gut number, they usually know within ±10 points. Industry baselines: outbound prospecting tools cite 20–35% leakage for inbound leads not handled in under an hour.
What's a realistic 'routing improvement %' to enter?▾
70–90% for most teams. Instant Slack routing eliminates the failure modes that cause most leakage, submissions sitting in a shared inbox, the assigned rep being out, weekend leads waiting until Monday, leads from the wrong segment going to the wrong queue. What it doesn't fix: a rep who sees the Slack ping and ignores it for 4 hours. If your bottleneck is human capacity rather than triage, dial the improvement number down.
Why is 'response time after routing' an output, not an input?▾
Because instant routing collapses triage time, the response time after routing is mostly determined by your team's time-to-first-touch from a notification, not by your current speed. The calculator estimates the post-routing time as roughly 10% of the current (the human-touch portion), scaled by the improvement input. If you want a precise response-time forecast, use the response time calculator, that tool models the curve more carefully.
Does this assume a specific tool?▾
No, the calculator is tool-agnostic. The numbers apply to any routing setup that gets a Google Forms submission to the right Slack channel instantly: RouteForms, a hand-rolled Apps Script, Zapier with Paths. We exist on this site, so the CTA is RouteForms, but the math doesn't depend on us.
Does this work for non-sales workflows?▾
Partially. For support tickets, the right output is SLA misses recovered, not revenue. For booking workflows, it's no-show or missed-booking recovery. The dollar figures only mean something when leads convert to revenue with a known average value. The 'response time after routing' output is universal.
Is this a guarantee?▾
No, it's a planning model. Your real numbers depend on the actual share of leakage that's a routing problem (vs. qualification, follow-up discipline, or product fit), how good your routing rules are, and whether the team treats Slack pings as priority. Treat the output as a ceiling for the work, not a contract.
Route leads before they go cold
RouteForms sends Google Form leads to the right Slack channel with routing rules, delivery logs, retries, and fallback channels.
Keep reading
The complementary tool, models the speed lens (conversion multipliers from HBR data), not the leakage lens.
Generate the IF-THEN routing rules that turn the recovered-revenue number into actual deliveries.
If qualification is nuanced, score multiple signals into tier-based routing rather than a single rule.
If you're calculating leakage across multiple clients, plan the routing setup before configuring anything.