A useful route.
With the reason attached.
Answer three questions. See which original sample rules apply and where a person should take over.
Fictional demonstration · original sample rules and dataAsk around → interpret advice → inconsistent next step
Agreed questions → visible rules → explained route
Describe a sample workflow
Use imaginary answers to explore the branching.
Your route appears here
Incomplete rules lead to clarification before any implementation route.
Why this route
Keep an alternative in view
Watch the 13-second walkthrough
Transcript: Describe a frequent data-connection task with unconfirmed inputs. The guide first routes to clarifying the process. Mark the inputs agreed: it suggests a sample connection pilot including support and monitoring. Switch to an occasional enquiry task: a small scoped form with a manual fallback appears. Each route explains its fictional rules.
Silent clip assembled from actual demonstration interaction states.
What this shows, checks and limits
Rules R1–R3 are original fictional business-process triage rules, not client-owned course-selection logic. The example prioritises unconfirmed inputs, separates routes by main need, and changes the next step by volume. All twelve valid answer combinations and incomplete/unknown values are checked. Real guidance requires an accountable rule owner, agreed exceptions, version control and human review; no recommendation about a real business is being made.
Have a similar workaround?
Bring one repeated task. We can discuss a useful, bounded first step.