Lead routing for small teams

Lead routing for small teams using Google Forms

Route Google Form leads to the right Slack channel by budget, service, location, urgency, or lead type — without building Apps Script or buying enterprise lead routing software.

  • IF-THEN rules in a dashboard
  • Delivery logs + automatic retries
  • Fallback channels built in
Build it in two clicks

Build your first lead routing workflow

Generate the IF-THEN rules with the Lead Routing Rules Generator, then quantify the revenue impact with the missed-lead calculator. Both tools feed straight into RouteForms.

Anti-enterprise

Lead routing software without the enterprise setup

Most lead routing software is built around Salesforce, sales-ops teams, territories, and complex CRM workflows. RouteForms is for small teams that still collect leads through Google Forms and need those leads routed to the right Slack channel fast.

  • Route by budget, service, location, urgency, or lead type
  • Send each lead to the right Slack channel
  • Keep delivery logs
  • Retry failed sends
  • Use fallback channels
  • Avoid maintaining Apps Script

Built for agencies, recruiters, coaches, real estate teams, support teams, and small SaaS teams — anyone whose lead flow runs through a Google Form rather than a CRM intake.

How it works

From form submission to the right Slack channel

  • 1. Connect your Google Form.Paste the form's edit URL into RouteForms; install the Apps Script trigger we generate (90 seconds).
  • 2. Create routing rules.IF Budget ≥ 50,000 → #vip-leads. IF City = Mumbai → #mum-team. Build the rules in a dashboard, not in code.
  • 3. Send each response to the right Slack channel. First matching rule wins. Everything else lands in the fallback channel you pick.
  • 4. Track delivery logs and retry failures. Every submission, every Slack response, every retry — visible per form, with one-click resend.
Why this matters

Lead routing solves the “one inbox for everything” problem

Most teams start with a single Slack channel — #leads, and route every form response into it. That works for the first 50 submissions a month and breaks somewhere around 200. By the time you're at 1,000:

  • Hot leads are buried under tire-kickers
  • The wrong agent sees the wrong lead and nobody owns the response
  • Support questions land in sales and silently never get answered
  • Friday evenings have 50 unread messages and Monday morning has 200
  • Nobody can tell whether the last lead came in

Lead routing is the fix. Send high-budget leads to a sales channel, demo requests to SDRs, support questions to CS, urgent items to on-call. Each team only sees what they should see, and the routing happens automatically the moment a response lands.

Real estate

Typical form fields
  • Budget · number / short-answer (currency)
  • City · dropdown
  • Property Type · dropdown. Residential / Commercial / Rental
  • Timeline · dropdown
Common routing rules
  1. #1 IF Budget greater than or equal 100000 #vip-leads
  2. #2 IF Budget greater than or equal 50000 #hot-leads
  3. #3 IF Property Type equals Commercial #commercial-desk
  4. #4 IF City equals Austin #austin-team
  5. #5 IF Timeline equals Within 30 days #urgent-leads

High-budget leads bypass the general queue and land in front of a senior agent within seconds. Commercial enquiries get their own desk. City-based teams only see what's theirs.

Inbound sales

Typical form fields
  • What are you trying to do? · paragraph (free text)
  • Team size · dropdown — 1, 2-10, 11-50, 50+
  • Budget · dropdown. Under $1k, $1k-10k, $10k+
Common routing rules
  1. #1 IF What are you trying to do contains demo #sdr-inbox
  2. #2 IF What are you trying to do contains pricing #sales-pricing
  3. #3 IF Budget equals $10k+ #enterprise-leads
  4. #4 IF Team size equals 50+ #enterprise-leads
  5. #5 IF What are you trying to do contains support #cs-inbox

Free-text intent fields use contains for keyword routing. The first matching rule wins, so put 'enterprise-flagged' rules above the demo and pricing rules if you want size and budget to win when both fire.

Recruiting

Typical form fields
  • Role · dropdown
  • Location · short-answer
  • Years of experience · number
  • Compensation expectation · currency
Common routing rules
  1. #1 IF Role contains Engineering #hiring-eng
  2. #2 IF Role contains Design #hiring-design
  3. #3 IF Role contains Marketing #hiring-marketing
  4. #4 IF Location contains Remote #hiring-remote
  5. #5 IF Years of experience greater than or equal 10 #senior-pipeline

Engineering, design, and marketing each have their own hiring channel. Remote candidates get a parallel channel so the remote-only roles see them first. Senior candidates ping a dedicated pipeline.

Marketing agency

Typical form fields
  • Client · hidden field per client form
  • Source campaign · hidden field
  • Lead score / qualification · depends on form
Common routing rules
  1. #1 IF Client equals Acme Co #acme-leads (in Acme's Slack)
  2. #2 IF Client equals Bright Studios #bright-leads (in Bright's Slack)
  3. #3 IF Client equals NorthStar #northstar-leads (in NorthStar's Slack)

Each rule's Slack webhook URL can point at a different workspace, so one RouteForms account fans out into many client Slacks. On the Agency plan, client workspaces group everything by client too, submissions, delivery logs, billing visibility.

Course / bootcamp operator

Typical form fields
  • Course interest · dropdown. Data Science / Full Stack / Marketing
  • Budget · short-answer (currency)
  • Background · paragraph
Common routing rules
  1. #1 IF Course interest contains Data Science #counselor-ds
  2. #2 IF Course interest contains Full Stack #counselor-fs
  3. #3 IF Course interest contains Marketing #counselor-mktg
  4. #4 IF Budget is empty #follow-up-needed
  5. #5 IF Background contains career change #career-switchers

Each course has its own counselor channel; empty-budget responses go to a follow-up queue rather than a counselor; career-switchers get a tailored funnel.

Clinic / appointment booking

Typical form fields
  • Department · dropdown
  • Urgency · dropdown. Routine / Soon / Urgent
  • New or returning · dropdown
Common routing rules
  1. #1 IF Urgency equals Urgent #urgent-triage
  2. #2 IF Department contains Dental #dental-desk
  3. #3 IF Department contains Pediatric #pediatric-desk
  4. #4 IF New or returning equals New #new-patient-intake

Urgent requests jump the queue regardless of department. Department-specific desks handle their own bookings. New-patient onboarding has a separate channel because it has different paperwork.

Setup

Build one of these in 5 minutes

The shape is the same whatever the vertical:

  • Connect the form.Sign up to RouteForms, paste your default Slack webhook, and copy the pre-filled Apps Script into the form's script editor. The Google Forms to Slack guide walks through this end-to-end.
  • Open the Routing rules tab on the form. Available on Solo and Agency plans. Click Add rule.
  • Pick a field: use the exact question title from your form. Pick an operator. Type a value if the operator needs one. Paste the Slack webhook URL for the destination channel and a label like #hot-leads.
  • Reorder with up/down arrows so the most specific rules sit on top, the first matching rule wins.
  • Test with the simulator. The Routing rules tab includes a live simulator pre-filled with your most recent real submission. Try edge cases before going live.
  • Watch the delivery log.Every Slack post gets recorded with the matched rule and Slack's HTTP response. Filter to Failed for anything to retry.
FAQ

Frequently asked questions

What is Google Forms lead routing?

Lead routing is the process of sending each Google Form submission to a different destination, usually a Slack channel, based on what the respondent typed. Instead of every response landing in one inbox, high-budget leads go to a sales channel, support questions go to support, urgent items go to on-call, and so on.

Do I need code to set up lead routing?

No. RouteForms lets you define IF-THEN rules in a dashboard. Each rule names a form field, an operator (equals, contains, greater than, etc.), a value, and a destination Slack channel. The first matching rule for a given submission wins.

How many routing rules can I have?

Solo plan supports 10 rules per form. Agency plan is unlimited. The Free plan has 0 routing rules, every response goes to the default Slack channel.

Can I route by budget or price range?

Yes. The numeric operators (greater than, greater than or equal, less than, less than or equal) tolerate currency symbols and commas, so a respondent typing '$50,000' or '₹50,000' compares correctly against a rule value of 50000.

Can I route by city, region, or country?

Yes. Use equals (for dropdown / multiple-choice fields) or contains (for short-answer / paragraph fields). Comparison is case-insensitive.

What if no rule matches?

The submission goes to the form's default Slack channel, what you set on the Slack tab. If you haven't set a default, the submission is recorded with status SKIPPED so you can review it and decide what to do.

Can multiple agents see the same lead?

If you want one submission in two channels, point two webhooks at the same form (one rule each). By default, only the first matching rule fires, that keeps Slack noise down and routing predictable.

How is this different from Zapier Paths?

Zapier Paths does the same job but sits on Zapier's Professional tier and charges per task. RouteForms includes IF-THEN routing on every paid plan starting at $7/month flat, with unlimited responses. The dashboard, simulator, and delivery log are all shaped around this one workflow.

Build your first routing workflow

Free plan covers 30 responses a month. Solo unlocks routing rules from $7 — enough for any of the setups on this page.