Asking customers for screenshots, logs and files by email
How to ask a customer for a screenshot, an error log or a file so they actually send it: what to request, how to explain it, and what to do when they can't.
On this page(11 sections)
- Ask only when it will change your answer
- Say what you want, exactly
- Explain how, in one sentence
- Ask for text as text when you can
- Respect the sensitive parts
- Make it easy to reply
- A request you can reuse
- When they cannot or will not send it
- Follow up once, then decide
- Keep the evidence with the conversation
- The short version
A support conversation often stalls on one sentence: "Can you send me a screenshot?" The customer is not sure what to capture, does not know how, or is on a phone and gives up. Two days later you are still guessing, and they are still annoyed.
Asking for evidence is a skill of its own. This post covers what to ask for, how to phrase it, and what to do when the customer cannot or will not send it.
Ask only when it will change your answer
Before you request anything, check whether you can solve the problem without it. Every request costs the customer time and adds a round trip.
- If their message already names the page, the action and the error text, you may not need a screenshot at all.
- If you can look the account up yourself, do that first.
- If you need a file, know what you will do with it. "So I can see which row failed" is a reason. "For our records" is not.
When you do need something, ask for it in the first reply, along with anything else you need. One complete request beats three small ones. Our post on getting reproducible bug reports covers the full list of questions to batch together.
Say what you want, exactly
"Send a screenshot" leaves too much open. Name the screen and what should be visible.
Weak: "Please send a screenshot of the problem."
Better: "Could you send a screenshot of the page where you see the error, with the whole browser window showing so the address bar is included?"
The better version tells them where to look, how much to capture and why the address bar matters. It also fits in two lines.
Explain how, in one sentence
Most people know how to take a screenshot on their own device. Some do not, and they will not say so. Add a short line for the common cases:
- Windows: press the Windows key, Shift and S, then paste into your reply.
- Mac: press Command, Shift and 4.
- Phone: press the power and volume-down buttons together.
You do not need all three every time. Match it to what you know about the customer, or link to a short help page you keep for this. A recording of the screen can beat a still image for something that happens over several steps, but only ask for one if you will watch it.
Ask for text as text when you can
A screenshot of an error message cannot be searched or copied into a bug tracker. If the message is short, ask the customer to copy and paste it into their reply. Keep the screenshot as a second option for when the text will not select.
For logs and long output, ask for a file instead of a paste. Say what kind: "the exported CSV", "the file the app downloaded when you pressed Export".
Respect the sensitive parts
Customers will send whatever you ask for, including things they should not. Protect them.
- Tell them what to leave out. "Please hide any passwords or card numbers before sending" is one line and builds trust.
- Never ask for a password. If you need to see their account, use your own admin tools.
- If a file might contain other people's data, say how you will handle it and offer a smaller sample.
A customer who sees you thinking about their privacy is more likely to cooperate with the rest of the request.
Make it easy to reply
Tell them they can answer the email directly and attach the file there. Do not send them to a form or a portal unless the file is too large for email. Most mail systems limit attachments to around 20 to 25 MB, so for larger files send a link where they can upload it, and say so in the same message.
Mention the format only when it matters. "A photo from your phone is fine" removes a lot of hesitation.
A request you can reuse
Thanks for the detail. To see what is happening, could you send:
- A screenshot of the page with the error, with the address bar visible.
- The error text, copied and pasted, if you can select it.
Please hide any passwords or card numbers first. You can reply to this email and attach the image directly. If that is awkward on your device, tell me and I will find another way.
Keep a few of these as saved replies so you are not rewriting them under pressure.
When they cannot or will not send it
Some customers cannot. They are on a locked-down work machine, away from a computer, or not comfortable with the steps. Offer a different way in:
- Ask them to describe what they see, step by step, in plain words.
- Offer a short call if the problem is urgent and a call is something you do.
- Ask a teammate on their side to help, if they mention one.
If the customer is frustrated, drop the request and solve what you can. Our guide to handling angry customer emails explains when evidence can wait. If they write in simple, short sentences or seem unsure of the language, see support email in plain English.
Follow up once, then decide
If you hear nothing, one reminder after a day or two is fair. Restate the single thing you need, not the whole history. If another few days pass, tell them you will close the conversation but that replying reopens it. That is better than leaving it open forever, and it is honest about what you can do without their help. For problems that need to move to another team in the meantime, see email support escalation paths.
Keep the evidence with the conversation
Once the file arrives, it should stay attached to the thread so the next person does not ask for it again. Whoever picks the conversation up later should see the screenshot, the error and what you concluded in one place. If your team shares an inbox, a short internal note saying "screenshot shows the export failing at row 12" saves the next teammate from opening the file at all.
The short version
Ask once, ask specifically, say how, protect their data and make replying easy. Have a fallback for people who cannot send what you need. Good evidence requests feel like help, not homework, and they shorten almost every support thread that needs them.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
