How to prevent unqualified leads from progressing through your application process using a multi-form workflow approach. This is applicable to webforms in the Sales or Info Manager Modules.
| ✓ | Yes, submission gating is achievable in FranConnect — not through a single form's built-in logic, but by combining multiple web forms, campaigns, and workflow automation. |
Why a single web form won't work?
FranConnect's dependent field logic (available on dropdowns, radio buttons, checkboxes, and multi-select fields) controls field visibility — it does not restrict section access or block form submission based on a response. The following is therefore not possible within a single form:
| ✗ | Blocking a lead from advancing to the next section based on a "No" answer |
| ✗ | Preventing form submission if prerequisite questions are answered negatively |
| ✓ | Showing or hiding fields based on a lead's response (dependent field logic — this works today) |
How it works — overview:
The solution uses a sequential multi-form approach:
|
Web form 1 Gatekeeper questions |
› |
Workflow Evaluates responses |
› |
Disqualified If lead answers "No" |
› |
Web form 2 sent If lead answers "Yes" |
Step-by-step configuration:
| 1 |
Create the gatekeeper web form (Form 1) Build a web form containing only your qualifying questions — for example, "Do you have all required entity documents?" Use a radio button or drop-down field mapped to a store-level field so the response is captured on the lead record. Keep this form short and focused on pass/fail criteria only. How to create a campaign in Sales → How to create a campaign in Info Manager → |
| 2 |
Send Form 1 via a campaign Deploy Form 1 to your leads using a FranConnect campaign. When the lead submits the form, their responses are written to their record and the workflow (Step 3) is triggered automatically. |
| 3 |
Configure a workflow to evaluate the gatekeeper response Create a workflow triggered on form submission. Add a condition that checks the value of the gatekeeper field on the store record. If the lead answered "Yes" (meets prerequisites), the workflow sends Form 2 via a follow-up campaign action. If the lead answered "No," the workflow takes no action — or optionally sends a disqualification notification. How to build a workflow with conditions – Sales Module → |
| 4 |
Create the full application web form (Form 2) Build your complete application form. This form is only delivered to leads who passed the gatekeeper step. For an additional layer of review, enable the Approval setting on this form so a team member must manually approve the submission before it is accepted.
|
Tips and limitations:
Tip
You can chain as many gatekeeper forms as needed by repeating this pattern. Each form submission triggers a workflow that evaluates the response and conditionally delivers the next form.
|
Limitation to note This approach gates progression between forms, not within a single form. A lead who does not qualify will still be able to submit Form 1 — they simply will not receive Form 2. If your use case strictly requires blocking submission within a single form, that is not supported by standard FranConnect web form functionality. |