Protocol Reusable scenarios
Two neutral scenarios expose where each funnel builder is strong
One scenario checks lead qualification and whether visitor answers stay connected to follow-up. The other checks selling a digital product through checkout and upsells. We document access, blocked steps, sources, and dates.
Scenario A: B2B service qualification
A B2B service company needs a funnel that asks about needs, team size, urgency, and budget, routes strong-fit prospects to booking, gives other visitors a useful next step, stores the qualification context, and sends relevant follow-up.
Workflow checkpoints
- Create the multi-step page or interaction.
- Add conditional routing, scores, formulas, or outcomes where supported.
- Send strong-fit leads to booking and other visitors to a useful alternative.
- Inspect whether answers and scores stay on the contact record.
- Trigger the correct follow-up for each route.
- Confirm analytics, campaign context, and handoff data.
Scenario B: digital product sales and checkout
A creator sells a specific digital product. The route needs a sales page, checkout, a relevant order bump, one upsell, confirmation, delivery handoff, recovery or follow-up, and measurable revenue events.
Workflow checkpoints
- Build the offer page and checkout.
- Add the order bump and post-purchase offer.
- Connect payment processing without inventing a test transaction.
- Verify confirmation, customer record, and delivery handoff.
- Verify follow-up and abandoned-order behavior where documented.
- Confirm revenue reporting and attribution boundaries.
Current launch limitations
This edition does not claim hands-on testing. It records current official documentation and vendor statements, checked August 28, 2026. Tested labels will only appear after a scenario is completed and documented with plan access and blocked steps.