“It doesn't work” is hard to fix. A 30-second recording that shows exactly what you did and what happened usually saves a round of questions.
Why a video helps
A recording captures the order of clicks, what was on screen, error messages that flash and disappear, and timing problems that are hard to describe. The developer can see the issue the way you saw it.
What to show
- Where you start (the page, and that you're signed in if it matters).
- Each step, at a normal pace, with a pause after each click.
- What you expected (“this should save and close”).
- What happened instead, held on screen for a couple of seconds.
- Any error message, zoomed in so it's readable.
With automatic zooms, each click is framed on the exact button you pressed, so the developer can see what you clicked without guessing.
Keep it short
- Record just the tab or window involved.
- Start one or two steps before the problem, not from the beginning of your day.
- Cut long pauses. If the bug is about slowness, keep the wait and say so.
Hide private data
Bug reports often include customer names, emails or account numbers. Blur anything the developer doesn't need before you share. Wekiflo can blur sensitive fields such as emails and card numbers automatically, and you can add areas to blur or block out by hand. See how to blur sensitive information.
What to write with the video
- The browser and version, and the operating system.
- When it happened (with time zone) and the account or record involved.
- The steps in writing, so they can be copied into a ticket.
- Whether it happens every time.
Export a small MP4 (1080p is plenty) so it attaches easily to a ticket or a chat.