A good screenshot cuts support resolution from hours to minutes. Here is what to capture — and the message templates that get answers fastest.
The screenshot that actually helps - The FULL browser window: URL bar + error together. A cropped error with no URL forces a round-trip question - The exact error text, not a paraphrase - For phone issues: include the browser app name and network (WiFi/4G) - On desktop: press F12 → Console tab → screenshot any red text (this single habit halves debugging time)
The message template that works Copy, fill, send: 'Hi, my website [domain] shows [error text] since [time]. It happens on [phone/laptop, which browser]. I was trying to [what you were doing]. Screenshot attached. — [name, account email]'
Five data points. Every one removes a follow-up question.
What slows support down (avoid these) - 'Site not working' with no screenshot — support must ask, wait, and re-ask - Screenshots of the physical screen taken with a phone at an angle (use the actual screenshot button: Power+Volume-down on Android, Win+Shift+S on Windows, Cmd+Shift+4 on Mac) - Ten issues in one message — number them; support works through them in order
What Kairalmas support does with it Your screenshot goes to a human who can see your server's logs for that exact timestamp. That combination — your screenshot + our logs — usually ends with the fix in the same conversation.
Support is a two-player game. Send the right input and even complex issues become quick ones.