Free Google Forms lead scoring template

It scores a form submission against a set of weighted rules. Each rule checks a field, equals, contains, ≥, ≤, or is not empty, and awards points if the rule matches. The total score maps to a tier (Hot ≥70, Warm ≥35, Cold under 35), and each tier suggests a Slack channel to route the response into. The point of scoring rather than pure if-then routing is to capture compound qualification, a lead might not have one specific high-value field, but several mid-value ones that add up.

Different model. The rule generator produces if-then routing where one rule wins and that's the destination. Scoring is additive, every matching rule contributes points, and the total decides the tier. Use scoring when qualification depends on many signals (B2B: budget AND company size AND role AND timeline); use if-then when one signal dominates (high-budget lead always goes to #vip regardless of anything else). The two compose well: score on signals, then route by tier.

(1) B2B sales qualification, budget tiers, company size, decision-maker role, timeline urgency. (2) SaaS trial conversion, plan interest, team size, integration mentions, intent signals. (3) Support triage, priority, plan, impact language. (4) Real estate lead, budget tiers using ₹ Crore notation, city tier, timeline, finance readiness. Each preset ships a matching sample submission so you can see the scoring in action immediately.

Field names are case-insensitive with whitespace trimmed. String matchers (equals, contains) are case-insensitive. Numeric matchers (≥, ≤) tolerate currency symbols and abbreviations: '$50,000', '50k', '₹1.2 Cr', '50L' all parse correctly. 'is not empty' is the catch-all, awards points whenever the field has any value, useful for intent signals like 'filled the use-case field'.

Hot at 70+ points, Warm at 35+, Cold below 35. These are starting defaults, calibrate them to your scoring rules' point totals. If your rules can only sum to 50 points, dropping the Hot threshold to 40 makes sense. We don't expose threshold editing in the UI because it's easier to think about by tuning point values per rule first; once your distribution is balanced, the defaults usually work.

Not in the page itself, refresh resets to the active preset. To keep a configuration: copy the JSON output (it includes every rule with field/mode/value/points). For production scoring on real submissions, RouteForms supports the same rule model, but a true scoring engine is on the roadmap, not in the current product. For now you'd implement it in Apps Script using the scoring JSON as the config.

Indirectly. The suggested route per tier is a Slack channel name, once you know the tier, route the response there. Wire it together: score the response (this tool), pick the channel for that tier, post via our /tools/google-forms-to-slack-generator or RouteForms. The scoring decides where; the script handles delivery.

Combine three kinds. (1) Hard qualifiers, budget over a threshold, decision-maker role, paid plan. High points, gating-style. (2) Intent signals, non-empty use case, specific integration mentions, urgency language. Mid points, accumulate across many leads. (3) Negative signals, competitor mentions, 'just researching' language, missing contact info. Optional negative weights if you want to surface them. Most good systems use 6-10 rules across these three buckets.