Workflow pattern
Request → Diagnose → Resolve
Request visual context, see the real issue, and respond with a clearer fix.
Diagnosis starts with evidence — the clarifying-question loop disappears.
How the motion works
-
1
Request
Send one link. The other person records their screen in the browser — no account, no install — and their console logs and browser details come along with it.
-
2
Diagnose
You see what actually happened: the steps, the behavior, the environment. Not a secondhand description of it.
-
3
Resolve
Answer with a recording of the fix. The person follows along click for click, and the resolution is reusable for the next case.
What it looks like in practice
Get complete context before troubleshooting
Ask the person seeing an issue to submit a recording, screenshot, file, or approved technical context.
Resolve remote issues without another call
Let the right person see the environment, behavior, and steps before scheduling time.
Escalate with context intact
Pass the visual record to the next team — nobody retells the story.
Teams that run it
Customer Support · Troubleshooting · IT & Internal Support · Engineering
Tools that run it Request links · Screen recorder · Zight AI
Weighing alternatives? Zight vs Loom
"Request Video is so much better than users trying to explain what’s happening in an e-mail… I can see exactly when an issue occurs and what is causing it."
Integrations
Where this workflow runs
Zight drops into the tools this work already lives in — recordings, request links, and guides included.
Run it with Zight.
A recorder only lets you talk at people. This is the motion where Zight asks — and the evidence comes to you.