Lead Capture Step

Published July 25, 2026 • Updated August 1, 2026

Use the Lead Capture block when qualified responses should become contactable leads. The form can appear in the flow before the outcome or open from an outcome action after participants see their result.

Unlike standard question blocks, Lead Capture is a dedicated form step. It can sit in the normal sequence, act as a Jump Logic destination, and use hard-gate or soft-gate behavior depending on how much friction your flow can support.

Best used for

When to choose another block

Setup flow

1. Add Lead Capture from the Question Blocks palette.
2. Place it after the questions that qualify, segment, score, or personalize the participant.
3. Choose which fields to show and mark only the required fields you truly need.
4. Decide whether consent should be shown or required before submission.
5. For Teams automation, configure a purpose-specific permission, choose one target audience and required permission, then turn on Automatically add consented leads.
6. Choose the gate behavior: Hard gate, Soft gate, or None.
7. Customize the title, description, submit label, skip label, and consent copy.
8. Turn on notifications when your team should receive new lead emails.
9. Preview the flow and confirm the form appears at the right moment, either in sequence or from an outcome action.

Settings reference

Available fields

Name and Email are enabled and required by default. Optional fields include Phone, Company, Appointment date, Appointment time, Street address, Address line 2, Country, State / Province, City, and ZIP / Postal code.

Each enabled field can be marked required independently. Keep the form short unless the extra fields directly improve follow-up quality or operational handoff.

Gate behavior

Copy and consent

Operational consent and marketing consent are separate choices. Enabling Lead Capture or requiring operational follow-up consent does not authorize automatic marketing audience membership.

Use the unified Contact permissions and Audience section to add a required purpose-specific follow-up permission and, when appropriate, a separate optional permission. Both cards use the controlled purpose list: results delivery, feedback follow-up, support request, quote or consultation request, appointment follow-up, resource delivery, marketing, and custom. Selecting Custom reveals a required custom purpose name in addition to the exact agreement wording; that name is retained in response and contact audit evidence. The optional permission defaults to Marketing for existing and new blocks but can be changed to match the agreement being presented. After at least one permission exists, Teams accounts can select one active audience and enable Automatically add consented leads. With one permission, Add contact when shows the only qualifying permission as a summary. With both permissions, it becomes a selector that references the required or optional permission card. QuizFlow Labs adds the lead only when the published block still targets that audience, the account still has Teams automation access, a valid email was captured, and the respondent accepted that exact versioned permission. Audience membership does not grant permission for another purpose. Duplicate submissions reuse the existing contact and audience membership.

Pro accounts can review eligible consent evidence and add the lead manually from the response screen. Basic accounts do not have lifecycle audience access.

The default copy is built around results delivery:

• Title: Before you get your results...
• Description: Tell us where to send your personalized results.
• Submit label: Get my results
• Skip label: Skip for now
• Consent label: I agree to receive updates.

Lead Capture consent applies to the lead form action you describe. It is not automatically a substitute for separate service-contact, optional marketing, reminder, privacy acknowledgement, or industry-specific consent. When choices must remain independent, collect them as separate consent fields in a Custom Form, often after a reusable Content Page.

For a low-friction result flow, place separate choices before a Soft gate and make the skip label explicit—for example, View my result without contact. Test that skipping still provides the limited result promised in the surrounding copy.

Adjust the copy to match the reason you are asking for contact details. If the quiz offers a quote, consultation, download, or product recommendation, the form should say that plainly.

Notifications and answer detail

Turn on lead notifications when your team should receive an email each time a lead is captured. You can set the notification email, identify the client name, and decide whether answer detail is included.

Each attempted Lead Capture email appears under Dashboard → Notifications → Recent deliveries with its sent or failed status. This history begins after unified delivery tracking is enabled; older provider emails may not be available for backfill. Lead Capture alerts are not retried from the Notification Centre because QuizFlow Labs does not retain participant answers or contact details in the delivery record.

• Use summary answer detail when the recipient only needs the main context.
• Use full answer detail when sales, intake, or support teams need the complete submission.
• Keep privacy expectations in mind when deciding how much detail to send by email.

Analytics and limits

Lead Capture creates a lead when the form accepts valid contact details and any required consent. A captured lead uses one response from the account's monthly allowance. If the visitor later completes the quiz, completion updates that response without consuming a second unit.

Submissions and leads can differ when visitors skip the form, route around it, abandon after sharing their contact details, or complete a quiz without lead capture. Read Lead Definition for reporting details and Usage Limits for monthly response behavior.

UX guidance

• Place Lead Capture after value is established, not before the participant understands why contact details are needed.
• Keep fields minimal. Every extra field adds friction.
• Ask for phone only when it is genuinely needed for follow-up.
• Align the title and submit label with the promised result or next action.
• Use soft gate when conversion quality matters but completion rate also matters.
• Use hard gate when the result, quote, or follow-up cannot happen without contact details.
• Confirm the outcome message still makes sense for participants who skip a soft-gated form.

Logic and routing

Lead Capture can be the next step in the normal flow or a destination from Jump Logic. Routing into lead capture is forward-only, just like other question destinations.

After the form, participants continue to the configured next step, usually Outcomes, where you can show personalized copy, action rules, and next steps.

Opening a Lead Capture form from Outcomes

In Outcomes, add an action and set Button action to Open a lead form. The action can use either the button or card presentation.

• The selector lists existing Lead Capture blocks from Questions. When there are multiple forms, each option includes its block position and title, such as Step 4: Business Address.
• The Outcomes summarizes the selected form's description, enabled fields, and consent requirement.
• Use Edit in Build Flow to change the form. Completion always references that original block, so there is no duplicate form configuration to keep synchronized.
• Opening and submitting the outcome form are tracked automatically. Successful submissions appear in the Leads view.

This pattern is useful when you want to show the result first and let interested participants choose a consultation, quote request, download, or follow-up form afterward.

Troubleshooting

Tips

• Ask for contact details after the participant has received enough context to trust the exchange.
• Keep the enabled fields aligned with the next action.
• Use consent copy that matches the communication you plan to send.
• Test hard-gated and soft-gated behavior before publishing.
• Check analytics after campaigns to compare submissions, leads, completion CTA leads, and skipped forms.
• If outcome copy references lead data, make sure the required lead fields appear before completion.