Blog/ Email writing & templates

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

Nafiul HasanNafiul Hasan· 10 min read
A speech bubble card with an emerald magnifying glass held over a small beetle on an app window, representing asking a customer for details about a bug

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
  1. 01How do you ask a customer for more details about a bug?
  2. 02What should you do before you ask?
  3. 03Steps: how to write the request
  4. 04Template 1: How do you ask for reproduction steps?
  5. 05Template 2: How do you ask for a screenshot politely?
  6. 06Template 3: When is a screen recording better?
  7. 07Template 4: How do you ask for browser and version details?
  8. 08Template 5: How do you ask for a console log or HAR file?
  9. 09Template 6: How do you ask for app logs?
  10. 10Template 7: How do you request account details securely by email?
  11. 11Template 8: How do you ask when the problem happened?
  12. 12Template 9: How do you ask for details a second time?
  13. 13Which capture method works on which device?
  14. 14What if the customer still does not reply?
  15. 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. 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. 2

    Ask for one item

    Two questions feel like a form. One feels like a conversation. Ask for more in the next reply.

  3. 3

    Give the capture steps

    Name the keys, menus or buttons for their device. 'Press Shift, Command and 5' beats 'send a recording'.

  4. 4

    Say what it unlocks

    Customers answer faster when they see the payoff.

  5. 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.

Reproduction steps request
[WHAT WE NEED]Hi [First name], I can see the export fails on the Reports page. Could you list the clicks from the dashboard until the error appears? Rough notes are fine.
[HOW TO CAPTURE IT]Write each click as a numbered line, then what you expected and what happened instead.
[WHY IT HELPS]Engineers can only fix what they can repeat.
[SEND BY]Reply by [day], or tell me a good time and I will walk through it with you.

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.

Screenshot request
[WHAT WE NEED]Could you send a screenshot of the error message? Please include the whole window.
[HOW TO CAPTURE IT]Mac: Shift, Command and 4, then drag over the whole window. Windows: Windows key, Shift and S. iPhone: side button and volume up together. Android: power and volume down together (varies by phone). Attach the image to your reply.
[WHY IT HELPS]The exact wording of the error often points straight to the cause.
[SEND BY]Whenever you next see it. No rush; the ticket stays open.

Template 3: When is a screen recording better?#

Use a recording when the problem depends on timing or sequence.

Screen recording request
[WHAT WE NEED]Would you record a short video of the problem, ideally under a minute?
[HOW TO CAPTURE IT]Mac: Shift, Command and 5, then Record Selected Portion. Windows 11: open Snipping Tool and pick the video icon. iPhone: the Screen Recording button in Control Center (add it in Settings if it is missing). Android: the screen record option in quick settings, which varies by phone.
[WHY IT HELPS]A video shows the order of events, which a still image cannot.
[SEND BY]Reply with the file or a share link by [day], after checking it shows no private data.

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.

Browser and version request
[WHAT WE NEED]Which browser or app version are you using, and on which device or operating system?
[HOW TO CAPTURE IT]Chrome: More, Help, About Google Chrome. Edge: Settings and more, Help and feedback, About Microsoft Edge. Firefox: Help, About Firefox. Safari: Safari, About Safari. Menu names vary slightly by version. Our app: Settings, version number.
[WHY IT HELPS]It tells us whether this is a known issue and whether an update fixes it.
[SEND BY]A quick one-line reply is perfect.

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.

HAR file request
[WHAT WE NEED]If you are comfortable, a network recording would show us the failing request. I can walk you through it.
[HOW TO CAPTURE IT]Press F12 (Option, Command and I on a Mac), open the Network tab, repeat the problem, then click Export HAR (sanitized) and attach the file.
[WHY IT HELPS]It shows which request failed and what the server answered, so we skip the guessing.
[SEND BY]By [day]. The sanitized file leaves out Cookie, Set-Cookie and Authorization headers but may still show page addresses and other request data; tell us if you would rather share it another way.

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.

Log file request
[WHAT WE NEED]Could you send the latest log file from the app?
[HOW TO CAPTURE IT]Open [Your App], go to [Help > Export logs], save the file and attach it. If you cannot find the menu, tell me your version and I will point you to it.
[WHY IT HELPS]The log shows what the app was doing at the moment it failed.
[SEND BY]Within a day or two. Tell me if it includes anything you do not want shared.

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.

Account identifier request
[WHAT WE NEED]Could you confirm the email address on the affected account and your workspace name?
[HOW TO CAPTURE IT]Both are in Settings, under Account. Please do not send a password, full card number or one-time code. We will never ask for them.
[WHY IT HELPS]It lets us open the right account and check the error ourselves.
[SEND BY]Reply whenever suits, or ask for a secure upload link.

Template 8: How do you ask when the problem happened?#

A narrow window lets an engineer search logs instead of scanning days of them.

Timing window request
[WHAT WE NEED]When did you last see the problem? A rough time and your time zone is enough.
[HOW TO CAPTURE IT]'Around 3pm Eastern on Tuesday' works. Tell us too if it has happened before.
[WHY IT HELPS]We can match your attempt against our logs.
[SEND BY]A short reply today or tomorrow, while the logs are fresh.

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.

Second request, frustrated customer
[WHAT WE NEED]Hi [First name], thank you for that, and sorry to come back to you again. It showed us [what you learned]. We still need one more thing: [single item].
[HOW TO CAPTURE IT][Two-line capture steps]. If that is a hassle, reply with a time and we will do it together on a quick call.
[WHY IT HELPS]It is the last missing piece. With it, [named outcome, such as 'we can reproduce the fault and give you a fix date'].
[SEND BY]No deadline from you. I will update you by [day] either way.

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.

A phone, a laptop and a tablet, each paired with a capture tool: an emerald camera for a screenshot, a screen-record button and a document sheet for a file or log
Every device has its own capture shortcut. Paste the matching row so the customer knows exactly how to send it.
ItemMacWindowsiPhone / Android
ScreenshotShift + Command + 4Windows key + Shift + SSide button + volume up (iPhone with Face ID); power + volume down (most Android)
Screen recordingShift + Command + 5Snipping Tool, video mode (Windows 11)iPhone: Control Center Record button; Android: quick settings (varies by phone)
Browser versionSafari > About Safari, or Chrome > About Google ChromeBrowser menu > Help > About (wording varies by browser)Android: Settings > Apps > browser name; iPhone: Safari follows the iOS version
Network (HAR) fileOption + Command + I, Network tabF12, Network tabNot practical: ask for a desktop attempt or a recording
App versionApp menu > AboutHelp > AboutSettings > 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

Do not request passwords, full card numbers, recovery codes or tokens. If a customer volunteers one, tell them to change it and redact it from your helpdesk record. Treat any HAR file or log as sensitive: limit access and delete it when the ticket closes.

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

Nafiul Hasan

Written by

Nafiul Hasan

Nafiul 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.

EntrepreneurAI Automation System BuilderAI EnthusiastBuilds AI Enterprise Solutions10+ years experience
More from Nafiul
Ready when you are

Draft the follow-up in seconds, then approve it

Try AI Emaily on a 7-day free trial and turn these nine requests into reusable templates. We build AI Emaily, and nothing sends without your approval.

  • 7-day free trial
  • Cancel anytime
  • Every provider