Product / Service Finder

Published July 28, 2026 • Updated August 2, 2026

Product / Service Finder turns participant answers into ranked, explainable recommendations. It uses a reusable Recommendation Catalog, one or more Finder Question blocks, and a Personalized Recommendations results block.

How the parts work together

• Recommendation Catalog: Workspace-level decision logic containing customer needs, recommendable options, actions, and fit rules.
• Finder Question: Collects one criterion, such as goal, budget, experience level, or service need.
• Personalized Recommendations: Securely ranks eligible offers and presents the strongest matches with optional match strength and reasons.
• Product Cards: Manually merchandises fixed offers; it does not calculate a match.

Recommendation Catalogs are separate from the Asset Library. The Asset Library stores reusable files, images, and links. A Recommendation Catalog stores structured decision logic and may reference Asset Library images.

Build a finder

1. Open Recommendation Catalogs from the dashboard and choose whether the experience recommends products, services, or packages.
2. Under Purpose, describe the one customer decision this catalog should support.
3. Under Customer needs, add at least one focused question with two or more answer options.
4. Under Options, add at least two active products, services, or packages. For visual results, choose an image from the Asset Library and provide descriptive alt text.
5. Under Rules, choose how strongly every relevant answer fits each option and add a short participant-facing reason. Use exclusions only for genuinely incompatible choices.
6. Set each option's action to a website URL, booking page, or no action.
7. Use Test & publish to walk through customer answers and review ranking, exclusions, and explanations.
8. Publish the catalog to create an immutable version.
9. Open a Flow and add a Finder Question for each customer need you want to ask.
10. Add Personalized Recommendations after those questions.
11. Choose the result count, minimum match strength, and whether to show strength and reasons.
12. Under When no recommendation qualifies, customize the explanation and optionally route participants to a Content Page, Lead Capture, booking step, another Flow step, an external URL, or graceful completion.
13. Preview the full path and force a no-match scenario, then save and publish the Flow.

Recover from no match

A no-match result is a valid decision: matching completed, but every offer was excluded or fell below the configured minimum strength. Use one focused recovery action so participants can keep moving instead of reaching a dead end.

• Send participants to an earlier question when reviewing an answer could produce a better match.
• Use Lead Capture when a person should review the request manually.
• Use a Content Page to explain alternatives, eligibility, or next steps.
• Use Booking or Appointment Selection when a conversation is the best path forward.
• Use an external URL for support or a resource hosted elsewhere.
• Finish gracefully when the normal Flow outcome is the right conclusion.

QuizFlow Labs treats service failures differently. If matching cannot load, participants see a retry action and keep their existing answers; the configured no-match action is not shown.

Manage archived catalogs

Open Recommendation Catalogs, then use the Active and Archived views in the catalog library. Both views can be searched by catalog name or description. Archiving keeps a catalog available for existing Finder configurations while removing it from the active workspace view.

Use Restore catalog to return an archived catalog to the Active view with its draft, published version, criteria, and offers intact. An archived catalog can also be permanently deleted from the Archived view. QuizFlow Labs blocks deletion while the catalog is referenced by a current draft or published Flow, so remove or replace those Finder blocks first. Permanent deletion removes the catalog and its saved versions and cannot be undone.

Duplicate a catalog

Choose Duplicate on an active catalog to create an independent draft copy. The copy includes the source catalog’s description, matching criteria, offers, images, and draft rules, but it does not copy published-version history or change any Flow connected to the source. Review, rename, test, and publish the copy before using it in a Finder.

Matching behavior

Strong fits rank above good, neutral, and poor fits. An explicit exclusion removes an incompatible offer. A criterion marked Required compatibility also removes offers that do not define compatibility for the participant's selected answer.

Ties are deterministic: match strength, score, offer priority, and catalog order are applied in sequence. Published Flows keep using the catalog version they reference until the builder intentionally selects a newer published version.

Update a Flow to a newer catalog version

When a Flow uses an older catalog version, the builder shows Catalog updates available. Choose Review update to compare criteria and offer changes before anything is modified.

The assistant updates every Finder Question and Personalized Recommendations block linked to that catalog together. It refreshes response modes, choices, Budget Range configuration, and catalog-version references while preserving your custom question wording. The update changes only the current Flow draft until you save and publish it.

If the latest catalog removed a criterion used by the Flow, the assistant blocks the upgrade. Restore or replace that criterion in the catalog, publish another version, and review the update again. QuizFlow Labs never silently upgrades a published Flow or leaves its Finder blocks on mixed catalog versions.

Security and privacy

Matching runs on the QuizFlow Labs server. Public Flow definitions contain catalog and version references, but not internal offer names, SKUs, vendors, fit weights, exclusion rules, or catalog administration data. Finder requests contain only Flow answer option identifiers needed for matching.

Analytics

Block Performance records recommendation impressions, no-match states, recovery clicks, retries, and offer interactions. Recovery events include only the destination type and stable target identifier—not custom copy, URLs, answers, or catalog rules—so you can measure how many participants continue safely after no match.

Troubleshooting

• No catalog appears: publish a Recommendation Catalog with at least one valid customer need.
• No recommendations appear: confirm offers are active, review exclusions and required compatibility, then lower the minimum match strength if appropriate.
• A recovery action cannot be published: reselect its destination; the original Flow step may have been removed.
• A question has old options: select the current published catalog and criterion again, then save the Flow.
• The catalog changed but the Flow did not: publish the catalog and intentionally update the Finder blocks to the new immutable version.
• The update assistant is blocked: the latest version removed a criterion used by a Finder Question. Restore it or intentionally remap that question before upgrading.
• An offer image does not appear: confirm the image is still available in the Asset Library, save the catalog, publish a new catalog version, and update the Finder blocks to that version.