Legal Intake Quiz Funnel: Progressive Questions Before Secure Intake

A legal intake quiz funnel should orient a prospective claimant with a few coarse questions, then transfer the person to a firm-controlled secure intake before collecting sensitive facts or documents. The quiz may identify a broad matter category, preferred next step, and whether the person is ready to continue. It should not diagnose a claim, decide legal qualification, or send claimant facts through advertising tools. The handoff should preserve source and consent history while keeping unknown answers distinct from questions the person did not answer.

Give the public quiz one limited job

A public quiz sits between an advertisement or educational page and the firm's intake system. Its useful job is to reduce confusion at the entrance. It can tell a visitor what will happen next, direct the visitor to the appropriate firm-controlled path, and confirm whether the visitor wants to continue now or later.

That is a smaller job than legal intake. Intake may eventually require identities, dates, narratives, records, conflict information, and case-type evidence. A public quiz should stop before those details. The boundary matters because advertising pages and measurement tools may have different access controls, retention settings, vendors, and data uses than the firm's intake environment.

The safest design starts by writing two lists. The first list contains the few coarse inputs the public step needs for routing. The second contains everything reserved for secure intake. If a question does not change the immediate path, remove it from the quiz.

Draw the field boundary before writing questions

The quiz should move from low-detail orientation to a clear handoff. It should not become a shorter copy of the secure intake form.

Stage	Appropriate information	Boundary and system behavior
Educational landing page	Page identifier and approved campaign identifier	Explain the process without collecting claimant facts. Keep sensitive values out of the page URL.
Public quiz start	Acknowledgment that the visitor wants to begin	Record only an approved coarse event such as quiz_started. Do not attach free text or personal details.
Broad routing	General service or matter category at the level approved by firm counsel	Use a short controlled list plus an "I am not sure" option. Do not infer a diagnosis, injury, or legal conclusion.
Readiness	Continue securely now, request an approved contact path, or stop	Make each choice clear. Do not treat continued navigation as consent to unrelated uses.
Secure handoff	Handoff identifier, source record, applicable consent record, and destination	Strip campaign query strings before the sensitive step. Transfer through a firm-controlled domain or approved subdomain.
Secure intake	Identity, detailed facts, documents, conflict information, and case-type evidence	Apply firm access controls, retention rules, provenance, and human review. Keep this information out of ad-platform events.
Attorney or authorized staff review	Conflict analysis, engagement, qualification, legal conclusions, and advice	These are human decisions under firm policy. The quiz never advances or rejects a matter on legal grounds.

The phrase "broad matter category" requires discipline. A controlled choice should help select a workflow without asking the visitor to reveal the sensitive event itself. If the firm cannot define that distinction confidently, the public step can offer an even simpler choice such as continuing to general secure intake or contacting the firm through an approved channel.

Use progressive questions that earn the next step

Progressive disclosure means asking only what the current screen needs. A practical public sequence may contain four screens.

1. Set expectations. State that the quiz offers general routing and does not create an attorney-client relationship or provide legal advice. Tell the visitor that sensitive information will be requested only after the secure handoff.
2. Choose a broad path. Present the small set of firm-approved categories. Include "I am not sure" so a person is not forced to make a legal classification.
3. Choose what happens next. Let the visitor continue to secure intake, use an approved contact option, or leave. Explain what the destination will collect before the person proceeds.
4. Confirm the handoff. Identify the firm-controlled destination and provide a plain link or button. Do not place sensitive facts, answers, or contact details in the destination URL.

Conditional logic should remove irrelevant questions, not create an invisible scoring system. A response can choose the next informational screen. It should not silently label a person as qualified, unqualified, valuable, or unlikely to sign. If the firm uses eligibility rules later, authorized staff should approve those rules, see the supporting record, and control the resulting decision.

The public quiz should also have an explicit stop path. A visitor who does not want to continue should be able to leave without completing a required field or sharing contact information. The firm can measure the coarse stop stage without recording why the person stopped.

Preserve unknown, unanswered, and declined as different states

Required choices can make a quiz appear complete while reducing the accuracy of the record. A person may not know which category applies. Another person may skip the question. A third may understand it and decline to answer. Those are different states.

• Known response: the visitor selected an available answer.
• Unknown: the visitor actively selected "I am not sure."
• Unanswered: the visitor did not submit a response.
• Declined: the visitor chose not to provide an optional response.

Do not convert all four states into an empty string or a default category. The secure intake should receive the state that actually occurred. A known coarse routing choice may preselect a path for confirmation. An unknown response should route to a general workflow or human queue. An unanswered optional item should remain unanswered.

This distinction also improves measurement. The team can see whether a question is confusing without inspecting sensitive narratives. A high unknown rate may indicate that the labels use internal legal language. A high abandonment rate at one screen may indicate unclear instructions or an accessibility problem. Neither metric proves anything about claim quality.

Make errors understandable and recoverable

A progressive quiz must remain usable with a keyboard, screen reader, zoom, and common input methods. Every control needs a visible label. Instructions should appear before the field they govern. Focus should move predictably, and a validation error should identify both the problem and how to correct it.

The W3C guidance for error identification calls for detected input errors to be identified and described in text. Its guidance on labels or instructions explains that labels or instructions should be provided when content requires user input. In practice, do not rely on a red border, placeholder, or icon alone. Place a short text message beside the field, connect it programmatically to the control, and move focus to an error summary when submission fails.

Validation should protect the workflow without trapping the visitor. Preserve completed answers after an error. Offer a clear back action. Do not impose a short timer. Test at narrow widths and high zoom. If a contact format is optional, do not block a secure handoff merely because the visitor chose another approved path.

Build a clean handoff into firm-controlled intake

The handoff should create continuity without carrying sensitive data through the browser address bar or advertising system. The public workflow can create a random, short-lived handoff identifier that points to server-side routing context. It should not encode a name, phone number, medical fact, narrative, or quiz response.

Before the secure intake page loads, remove campaign query strings and prevent them from being copied into later intake URLs. Carry approved source attribution in a governed server-side record. Record which public content and consent language the visitor saw, the version of that language, the action taken, and the time. Keep consent records separate from marketing measurement so the firm can evaluate the authority and scope of each consent.

The ABA comments to Model Rule 1.18 explain that a person who communicates information unilaterally without a reasonable expectation that a lawyer is willing to discuss forming a relationship may not be a prospective client. The same comments also warn lawyers not to receive more disqualifying information than reasonably necessary when considering whether to represent someone. Firm counsel should determine the wording, collection boundary, conflict procedure, and retention treatment for the firm's jurisdiction and practice.

Keep advertising measurement coarse

An advertising platform does not need claimant facts to show whether people reach the secure intake boundary. Use an allowlist of coarse events such as landing_view, quiz_started, handoff_to_secure_intake, and secure_intake_completed. Event names, URLs, parameters, and user-defined data should contain no claimant narrative, sensitive category, document detail, or legal assessment.

Meta's Lead Ad Terms place obligations on the advertiser's collection and use of lead data. Meta's official Conversions API guidance describes a direct connection between an advertiser's marketing data and Meta's systems. Those sources do not replace a firm's legal and privacy review. They make the data boundary a configuration issue that should be documented, tested, and monitored.

Use a server-side event allowlist rather than allowing form fields to become event parameters automatically. Block full page URLs from measurement after the handoff. Review tag-manager changes before release. Scan network requests in a test environment to confirm that no secure-intake field values leave for an advertising endpoint.

Campaign quiz routes should normally use noindex unless the firm separately approves them as stable public educational pages. The guide you are reading can be indexable because it explains the system. A campaign-specific quiz with temporary copy, parameters, and routing logic has a different purpose.

Put human owners at every decision boundary

The quiz needs named owners even though it does not make legal decisions. Intake operations can own the routing taxonomy and exception queue. Privacy or compliance staff can approve data boundaries and measurement. Firm counsel can approve prospective-client language, consent, conflicts, qualification rules, and retention. Engineering can enforce the allowlist, URL stripping, access controls, and audit record.

Test the whole path with synthetic records before release. Confirm keyboard completion, error recovery, unknown and unanswered states, source attribution, consent versioning, query-string removal, event allowlisting, secure-domain transfer, and the staff exception queue. Then repeat the network test after every analytics or form change.

A useful legal intake quiz funnel ends early by design. It makes the next step understandable, gives the visitor control, and delivers a clean source record to secure intake. The firm's people and governed intake system handle the sensitive facts and the legal decisions that follow.

Book a demo →