What is quiz lead routing?
Quiz lead routing is the deterministic decision that maps a completed response to an operational action such as owner assignment, a review queue, an automated follow-up sequence, or no action. It happens after answer capture and scoring but before the CRM or notification workflow performs the action.
The route is an operational decision, not a hidden synonym for the score. Preserve the supplied answers, calculated score, qualification band, route decision, decision reason, rule version, and later human status as separate fields so the action can be reconstructed and challenged.
Related: Set the qualification thresholds before routing · Define the post-decision CRM handoff contract
Choose one of four route outcomes
Write the entry evidence and exclusion rule for every outcome before implementation. This table is a reusable policy template, not a universal sales model.
| Outcome | Use when | Minimum evidence | Do not use when |
|---|---|---|---|
| Automatic sales route | Fit and readiness rules pass | Valid contact, score or band, context, active owner | Ownership, permission, or suppression is unresolved |
| Manual review | Evidence conflicts or is incomplete | Auditable response and review reason | The record is invalid or prohibited |
| Nurture | Relevant but not sales-ready | Segment and permitted follow-up state | Requested result delivery is confused with marketing permission |
| Suppress or no action | Test, duplicate, invalid, withdrawn, or prohibited state | Stored suppression reason | Silence would hide a recoverable operational failure |
Related: Keep result delivery and marketing permission separate
Use a seven-step routing decision method
Validate the completion and required contact fields first. Calculate the score and band from a versioned rule, then check disqualifying facts separately from the number. Check duplicate, test, consent, and suppression state; resolve an active owner or queue with a named fallback; create exactly one route decision using a stable completion key; and expose a recovery path when the action cannot complete.
Collect only information that has a declared use. ICO guidance says personal data should be adequate, relevant, and limited to what is necessary. Its data-minimisation page is currently under review following UK legislation, so recheck it and obtain qualified advice before relying on it for a specific legal decision.
- Validate completion and the minimum usable contact fields
- Calculate the score and band from a versioned rule
- Evaluate disqualifiers separately from the numeric score
- Check duplicate, test, consent, and suppression state
- Resolve an active owner or fallback queue
- Create one route decision from a stable completion key
- Record failures in an observable recovery path
Related: Prevent retries from creating duplicate lead actions
Sources: ICO, Data minimisation principle
Apply the routing decision tree in order
If the completion is invalid, stop and request correction. If it is a test or suppressed record, store the reason and take no sales action. If fit or readiness evidence conflicts, send it to manual review. If both pass and an owner can be resolved, route once to sales. If the lead is relevant but not ready and follow-up is permitted, use the appropriate nurture path. Otherwise, store a no-action decision rather than inventing a route.
Order matters. A later positive score must not override an earlier blocking state, and failure to resolve an owner must not silently assign a random person.
Related: Test every score cutoff and tie case
Worked example: a 17-of-20 services lead
A services quiz records a 17-of-20 score, a valid business email, an implementation window of 30 days, and an eligible region. The record is not suppressed and the territory table resolves an active owner. It may be routed automatically with the relevant answers and rule version attached.
If the same record lacks a region, it belongs in manual review, not a random owner's queue. If the person asks only for a result and has not agreed to promotional follow-up, the requested result and any marketing sequence remain separate decisions. This example is illustrative and is not a reported product test or performance benchmark.
What should the route record contain?
Store completion ID, person or contact ID, supplied answers needed by the recipient, calculated score, qualification band, route decision, decision reason, rule version, owner or queue, decision time, action status, and retry count. Keep observations, calculations, operational inferences, and later human status distinct.
Google Analytics defines recommended lead-generation events such as generated, qualified, disqualified, working, converted, and unconverted leads. Treat an analytics event as evidence that a workflow step occurred, not as the authoritative CRM state. Record route decisions, action attempts, successful handoffs, and later outcomes separately, and deduplicate with stable completion and action identifiers.
Related: Define denominator-safe funnel metrics
Sources: Google Analytics, Recommended events
Keep the participant-facing promise accessible and accurate
Explain required fields, expected formats, and validation errors in text. Do not promise an immediate human response unless the routing service level can support it. W3C form guidance provides a practical baseline for clear labels, requirements, formats, and correction instructions that remain available to assistive technologies.
A routing delay should not erase the participant's result or imply that a salesperson has already reviewed it. Preserve recoverable state and give a clear next-step message without moving keyboard focus unexpectedly.
Related: Run the complete accessibility checklist
Sources: W3C, Form instructions
Block release until the route policy is testable
A release is ready only when the visible result, stored decision, owner resolution, downstream action, measurement, and recovery behavior agree.
- Each route outcome has explicit entry and exclusion criteria
- Score, disqualifiers, permission, suppression, and ownership are separate checks
- The same completion cannot create duplicate tasks
- Every unresolved owner has a named fallback queue
- Sales receives the minimum context needed to understand the decision
- Measurement distinguishes decisions, attempts, successes, and later outcomes
- A correction owner and rule-version rollback path are documented
Evidence
How to reproduce the method
Reproduce the policy with the four-outcome table, ordered decision tree, versioned route record, synthetic score and blocking-state cases, owner-resolution evidence, stable completion key, action logs, and recovery queue. The method separates participant observations, calculations, route inferences, transport state, and later sales outcomes.
Limitation
Where this conclusion stops
This method does not prove that a quiz score predicts revenue, replace human judgment in regulated or high-impact decisions, grant permission for marketing, or define a lawful basis for a particular organization. Faster routing cannot repair an invalid qualification model, missing ownership coverage, or insufficient sales capacity.
Sources and verification
What this guide relies on
- Google Analytics, Recommended events
- W3C, Form instructions
- ICO, Data minimisation principle
- The Lead Quiz Review editorial methodology
Sources and method checked October 2, 2026. External standards are linked to their primary publishers. Request a factual correction.