How to Ask a Customer for More Details: 9 Support Templates

The short answer
To ask a customer for more information about a bug, do your own homework first, then ask for one specific thing per email. Say exactly what you need, how to capture it in under two minutes, what it will unlock, and by when to send it. Never ask for passwords.
How to ask a customer for more details in a support email: nine copy-paste requests for steps, screenshots, logs and account IDs, plus a second-ask variant.
On this page
- 01How do you ask a customer for more details about a bug?
- 02What should you do before you ask?
- 03Steps: how to write the request
- 04Template 1: How do you ask for reproduction steps?
- 05Template 2: How do you ask for a screenshot politely?
- 06Template 3: When is a screen recording better?
- 07Template 4: How do you ask for browser and version details?
- 08Template 5: How do you ask for a console log or HAR file?
- 09Template 6: How do you ask for app logs?
- 10Template 7: How do you request account details securely by email?
- 11Template 8: How do you ask when the problem happened?
- 12Template 9: How do you ask for details a second time?
- 13Which capture method works on which device?
- 14What if the customer still does not reply?
- 15Is there a faster way to send these?
A customer writes in with 'it's broken', and your first instinct is a list of eight questions. That feels thorough. To the customer it feels like homework, and many stop answering.
Below are nine copy-paste requests for the details engineers need: reproduction steps, screenshots, recordings, version data, HAR files, logs, account identifiers and timing. The last covers the hardest case, asking a frustrated customer a second time.
How do you ask a customer for more details about a bug?#
Ask for one thing at a time, in plain words, with the exact capture steps included. Tell the customer why it helps and give a time to reply by. Everything else in this post is a variation on that sentence.
Each template uses four labels: WHAT WE NEED, HOW TO CAPTURE IT, WHY IT HELPS and SEND BY. Rewrite them into normal sentences before sending.
What should you do before you ask?#
The fastest way to lose goodwill is to ask for something you could have found yourself. Atlassian's Incident Management Handbook notes that incident issues are typically created by a support engineer in response to a customer ticket, so what you collect in the first two emails becomes what engineering works from. Spend five minutes first.
- Read the whole thread and earlier tickets. Do not ask for what they already told you.
- Check your side: recent errors in your logs, the status page, and whether other reports match.
- Try to reproduce it from what the customer wrote. If you can, you may not need to ask.
- Pick the single missing item that would change what you do next.
Steps: how to write the request#
- 1
Open with what you already know
One sentence showing you read their message, such as 'I can see the export fails on the Reports page'.
- 2
Ask for one item
Two questions feel like a form. One feels like a conversation. Ask for more in the next reply.
- 3
Give the capture steps
Name the keys, menus or buttons for their device. 'Press Shift, Command and 5' beats 'send a recording'.
- 4
Say what it unlocks
Customers answer faster when they see the payoff.
- 5
Set a soft deadline and a way out
Offer a reply-by time and a fallback, such as a short call.
Template 1: How do you ask for reproduction steps?#
Use this when the report is vague.
Template 2: How do you ask for a screenshot politely?#
Screenshots are the lowest-effort request. Say what to include, because a cropped image usually hides the error.
Template 3: When is a screen recording better?#
Use a recording when the problem depends on timing or sequence.
Template 4: How do you ask for browser and version details?#
Bugs that hit one customer are often one browser or one old app version. This is a ten-second ask.
Template 5: How do you ask for a console log or HAR file?#
A HAR file records every network request a page made. It is the most useful artifact for web bugs and the one customers fear most.
Chrome's DevTools documentation says its default export is a sanitized HAR that leaves out Cookie, Set-Cookie and Authorization headers. Point customers to that option.
Template 6: How do you ask for app logs?#
Ask for a log file only if your product documents where it lives, and give the exact path.
Template 7: How do you request account details securely by email?#
Ask for an identifier, never a secret. The account email, workspace name or order number is enough.
Template 8: How do you ask when the problem happened?#
A narrow window lets an engineer search logs instead of scanning days of them.
Template 9: How do you ask for details a second time?#
The customer already replied once, it did not work, and now you need more. Own it, shrink the ask, and offer a way to skip the typing.
Which capture method works on which device?#
Customers get stuck on the how, not the what. Keep this table handy and paste the row that matches their device.

| Item | Mac | Windows | iPhone / Android |
|---|---|---|---|
| Screenshot | Shift + Command + 4 | Windows key + Shift + S | Side button + volume up (iPhone with Face ID); power + volume down (most Android) |
| Screen recording | Shift + Command + 5 | Snipping Tool, video mode (Windows 11) | iPhone: Control Center Record button; Android: quick settings (varies by phone) |
| Browser version | Safari > About Safari, or Chrome > About Google Chrome | Browser menu > Help > About (wording varies by browser) | Android: Settings > Apps > browser name; iPhone: Safari follows the iOS version |
| Network (HAR) file | Option + Command + I, Network tab | F12, Network tab | Not practical: ask for a desktop attempt or a recording |
| App version | App menu > About | Help > About | Settings > About, or the app store listing |
What if the customer still does not reply?#
Silence usually means the ask was too heavy. Check whether you asked for more than one thing or skipped the capture steps.
Wait two or three working days, then send one short follow-up restating the single item and offering a call. If that gets nothing, say you will close the ticket on a set date and that replying reopens it.
Never ask for secrets in email
Is there a faster way to send these?#
The manual approach works: copy a template, fill in the brackets, send. The pain appears at thirty of these a week, each with a different device, name and deadline.
AI Emaily can draft the request from the thread, using reply templates and variables for the customer's name, device and the one item you still need. You write the guidance once in your Personal Context and every draft follows it. Nothing sends until you approve it.
It does not capture screenshots or logs, and it does not replace your helpdesk. It drafts the follow-up. We build AI Emaily, so weigh that accordingly. There is a 7-day free trial (card required, nothing charged if you cancel before day 7), and plans are on the pricing page.
Frequently asked
See it in AI Emaily
Keep reading
Sources

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.