One article, many situations
A single page has to cover every plan and platform, so the customer reads six paragraphs that are not theirs.
Interactive video for support
Answer it once, on video.
Turn the questions your team retypes every week into guided video that asks what the customer is stuck on and routes them to the fix.
Screenshot needed — help centre article with an embedded interactive walkthrough and a branching troubleshooting prompt
The deflection gap
Help articles cannot ask a clarifying question
Most tickets are a question the documentation already answers, in a section the customer could not tell applied to them.
Video demos the happy path
A recorded walkthrough shows the case that works and stops where the customer actually got stuck.
Deflection is invisible
You can count tickets, but not the customers who read the page and still opened one.
What changes
The walkthrough starts triaging
Three things a support video does once the interactions sit on the timeline.
Triage
The video asks before it explains
Open with the question an agent would ask first, and show only the branch that matches the answer.
- Branch by plan, platform, or error message in the first ten seconds
- Skip the setup steps a returning customer has already done
- Hand off to a form or a rep when the answer is out of scope
Resolution
The fix is done in the frame
Put the link, the download, and the setting next to the step that needs it rather than in a list underneath.
- Attach downloads and deep links to the exact moment they apply
- Confirm the customer completed the step before moving on
- Offer the contact route only after the self-serve path has failed
Screenshot needed — support walkthrough with a deep link hotspot and a file download attached to one step
Signal
You see where people get stuck
Read the branch customers take and the step they abandon, which is the paragraph the article gets wrong.
- See which branch the majority of viewers select
- Find the timecode where viewers stop or rewatch
- Route the unresolved viewers into a ticket with their answers attached
Screenshot needed — drop-off report for a support walkthrough showing branch selection and abandon timecode
What gets measured
The three numbers a support lead asks for
- Resolution, without a ticket
- Counted from viewers who finished the branch they chose and never opened a contact form.
- Drop-off, per step
- Attributed to the timecode customers abandoned, so you know which instruction fails.
- Escalations, with context
- Measured on tickets that arrive carrying the answers the customer already gave.
Example walkthrough
A troubleshooting path that forks on the error
The walkthrough opens by asking which message the customer is seeing, then plays only the branch that resolves it, with the settings link attached to the step.
Screenshot needed — interactive troubleshooting walkthrough branching on an error message
Support use case directory
Where a walkthrough beats a page
Each of these is a different moment in the support conversation.
Onboarding walkthroughs
Guide new accounts through first-run setup with a checkpoint at each step.
Explore →Troubleshooting paths
Fork the walkthrough on the error the customer is actually seeing.
Explore →Help centre embeds
Replace the static screenshot strip in your articles with a guided path.
Explore →Macro attachments
Send a branching walkthrough from the ticket instead of retyping the steps.
Explore →Release notes
Show what changed and let customers jump to the change that affects them.
Explore →Agent training
Test agents on real cases with branching scenarios before they take queue.
Explore →Support FAQ
What support teams ask first
The objections that come up in every evaluation, answered plainly.
Does it embed in our help centre?
Yes. The walkthrough is a link or an embed, so it drops into Zendesk, Intercom, HubSpot, or your own documentation.
Can we tell whether it deflected a ticket?
You can see who finished a branch, who abandoned it, and who went on to open a contact form, which is the closest honest measure of deflection.
Do customers need an account?
No. Customers open a link. You only collect an identity where you place an interaction that asks for one.
Can escalations carry what the customer already told us?
Yes. The answers given in the walkthrough pass to the ticket, so the agent does not restart the diagnosis.
Start with one article
Rebuild your most-read help article
Take the page that still generates tickets and see which branch customers actually need.