A fixed ladder the engine walks when a step's target never appears: show the step's authored fallback explainer card → or, if the step is marked optional, skip it silently → otherwise skip it, log it as a skipped step and show a quiet 'skipped a step' note. Reaching the end of a tour (or a dangling reference) ends it cleanly; the engine can never wedge.
Also called: tour fallback · skipped a step · empty account tour
- 1Every data-dependent spotlight in the content (a pipeline card, an estimate row, a Gantt bar, a Send button) is authored `optional: true` with a `fallback`, so tours run top-to-bottom on a completely empty tenant
- 2Skipped step ids are written to the user's progress row as telemetry — which anchors keep going missing is visible
- 3Role-blocked steps are caught BEFORE navigating and render a centered explainer instead
The first walkthrough a builder takes is on day one — no leads, no estimates, no projects, nothing on the board to point at. That is exactly when a tour is most likely to highlight a button that does not exist yet, and one that dead-ends on step two is one nobody comes back to. When a control is missing — brand-new account, a role that cannot open that screen, a feature not switched on — the step teaches the same lesson on a plain card, says outright that the screen is empty because the account is new, and carries on to the end.
- Tours that only work on a populated account
- Tours that hang forever waiting for an element that will never exist
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →