RouteForms
Start free
Workflow recipe

Send Google Forms lead alerts to Slack

Every form lead in the right Slack channel within seconds. Tiered by budget, mentioned with intent-appropriate urgency, recorded with delivery status, the shape of a sales-ready lead intake pipeline.

Start free →
  • Routing rules pick the right channel per lead
  • Mentions tuned for the channel's urgency
  • Delivery log + retry on failure
TL;DR

The short answer

Capture lead-qualifying fields (budget, source, timeline, role) in your Google Form. Define routing rules in RouteForms, high-budget leads go to a hot-leads channel with @here, standard leads go to #leads. Every submission posts within seconds. Delivery log records the destination; one-click retry if Slack rejects.

The fields that drive routing

Four signals worth capturing

  • Budget (number or dropdown), the single highest-signal field for tier routing. Use ≥ 100000 for VIP, ≥ 50000 for hot, fallthrough for standard. Currency formatting like $50,000 and ₹50,000 compare correctly.
  • Source (dropdown). Pricing / Demo / Blog / Search etc. Pricing-page leads convert at a higher rate than blog leads at the same stage. Route by source separately or in combination with budget.
  • Timeline(dropdown) — “Within 1 month”, “1-3 months”, “Researching”. Active timeline + high budget = maximum urgency. The “researching” bucket can route to a nurture channel instead.
  • Role (text or dropdown). VP / Director / IC. Decision-maker presence changes the urgency of the alert. Role contains "VP" + budget tier compounds nicely.
Setup

From form to channel in five steps

  1. 1
    Build the Google Form with routing fields
    Add Budget, Source, Timeline, Role as the qualifying fields. Mark the high-signal ones required; let optional ones stay optional to keep submission friction low.
  2. 2
    Create Slack incoming webhooks for each channel
    Typically three: #vip-leads, #hot-leads, #leads. Each webhook is channel-specific (setup steps). Copy each URL.
  3. 3
    Wire the form into RouteForms
    Sign up (Free plan), add the form, paste your primary webhook (#leads) as the default destination, install the Apps Script.
  4. 4
    Add routing rules
    Specific first. Budget ≥ 100000 → #vip-leads above Budget ≥ 50000 → #hot-leads. Fallthrough goes to #leads. Our rule generator ships these as the “Lead by budget” preset.
  5. 5
    Test with a real submission, verify delivery
    Submit a high-budget test response, should land in #vip-leads with @here. Submit a low-budget one, should land in #leads with no mention. Check the delivery log to confirm.
What lands in the channel

The message shape that actually gets attention

The default lead-alert message uses a Block Kit shape from the template generator: header with bell icon, mention line tuned to the channel, fields as a labelled list, context footer with the source.

:bell: *New lead*
<!here>
*Name:* Priya Mehta
*Email:* priya@acme.com
*Company:* Acme Co.
*Budget:* $50,000
*Source:* Pricing page

Channel: #hot-leads · Open in CRM

For more nuanced shapes (high-value with @channel, support-style with on-call subteam mention), the notification templates page ships nine ready-to-copy variants.

Where this fits in the lead intake stack

Slack is the alert layer, not the system of record

  • RouteForms: the delivery layer. Form → routing rules → Slack channel. Records every post in a per-form delivery log.
  • Slack: the alert layer. Sales team sees the post, reaches out within the 5-minute window.
  • CRM: the system of record. Either Google Sheets via Forms' native integration (cheap, basic), or a real CRM via a separate Apps Script post. RouteForms doesn't replace the CRM; it speeds up the human signal.

Industry-by-industry routing patterns are at /google-forms-lead-routing , real estate, education, healthcare, SaaS each have a recommended channel structure.

FAQ

Frequently asked questions

What's the right Slack channel structure for lead alerts?▾

Most teams use a tiered setup: #leads for everything, #hot-leads for high-intent (budget over a threshold, or pricing-page source), and optionally #vip-leads for the highest tier. Routing rules pick the right channel per submission. The tiered structure means the sales team can scan #leads casually but pays attention to #hot-leads immediately.

Which form fields should I capture to make routing work?▾

Four high-signal fields cover most lead workflows: Budget (or company size), Source (pricing / demo / blog), Timeline, and Role. Budget and source decide tier; timeline filters urgency; role identifies decision-makers. Our /tools/google-forms-lead-scoring-template ships preset scoring rules using these signals.

Should I use @here, @channel, or no mention?▾

@here for hot-leads channels, wakes whoever's currently online without paging the offline team. @channel for #vip-leads if you really need everyone (be conservative, channel mentions get muted fast if used too often). No mention for #leads where the team will scan periodically. The template generator at /tools/slack-message-template-generator ships these as presets.

How fast does the alert arrive in Slack?▾

Within a couple of seconds of the form submission under normal conditions. Google Apps Script's form-submit trigger fires within ~1 second, RouteForms processes the routing rules and posts to Slack. The result is comfortably inside the 5-minute window that the HBR research links to peak conversion (see our /tools/lead-response-time-calculator for the revenue model).

Can the sales team route follow-ups from Slack?▾

Slack doesn't connect back to the form, the lead alert is one-way. For two-way workflow (claim a lead in Slack and have it sync to a CRM), you'd need a Slack app with interactive components or a CRM with native Slack integration. RouteForms's role is the delivery + routing layer; CRM integration is downstream.

What if a lead alert fails to post to Slack?▾

RouteForms records the failure with Slack's status code in the delivery log. Click Retry once Slack-side is healthy (most failures are revoked webhooks or rate-limits). Paid plans get an email when a failure streak starts, so you know to look without watching the log. The lead is never silently lost, it sits in the log with a clear status.

Should I store the lead in a CRM as well as posting to Slack?▾

Yes. Slack is the alert layer; the CRM is the system of record. The honest pattern is to wire RouteForms to Slack for the live alert, and either (a) use Google Forms's native Sheets integration as a CRM-of-last-resort, or (b) add a separate Apps Script trigger that posts to your CRM's API. Don't try to make Slack the system of record.

Do high-budget leads really convert at higher rates?▾

Yes, in most B2B sales models, the HBR 'Short Life of Online Sales Leads' work and subsequent vendor studies consistently find higher close rates on higher-budget leads. The routing rule pattern (budget over threshold → hot channel) lets the sales team prioritise without manual triage; the calculator at /tools/lead-response-time-calculator estimates the revenue impact.

Wake the sales team within seconds

RouteForms routes every lead to the right channel with the right mention. Free for 30 responses a month.

Start free →See pricing

Keep reading

Lead routing by industry

The broader hub, recommended channel structures for real estate, education, healthcare, SaaS.

Read →
Routing rules in depth

Operators, ordering, defaults, how the rule engine picks the destination.

Read →
Route by answer, recipes

Concrete rule recipes for dropdowns, scales, free text, file uploads, currency answers.

Read →
Best Google Forms to Slack tools

All the real options for delivering Google Form responses to Slack, ranked by fit.

Read →