Home / Guides / Escalations and support operations

Email asking for more information: 5 support email templates

By Draft First. Updated October 2026

"Could you send more details?" doesn't tell the customer what you need. They may write back without the error text, the steps or the environment details you need to investigate. Then you have to ask again, and the customer keeps waiting.

Before you ask the customer anything, work out what the ticket is missing. Then ask for just that. The examples and names below are made up.

A short email asking for more information

Subject: A few details so we can look into this

Hi [name],

Thanks for reporting this. To investigate, could you send:

1. What you were doing when the problem occurred.
2. The exact error message or wrong result.
3. How this is affecting your work.
4. Where it happened: web or app, browser, and which account.

Please remove passwords, keys and personal details before sending
anything.

I'll review what you send and update you by [day].

[Your name]

Delete the lines for anything you already have. The five answers below show you which ones those are.

Before you write: read the whole thread

Read the whole thread history first. Check whether the customer already gave you the error, the steps or the environment details. Use what's there and ask only for what's missing.

Know what you're missing: the five answers

Before every escalation to engineering, write down five answers:

1. What the user did.
2. The exact error or wrong result.
3. The impact.
4. Whether you can reproduce it.
5. The environment.

Then add a sixth line for what you've already ruled out.

For any answer you don't have, write [MISSING]. Don't fill a gap with something vague like "environment: web". Some answers, like whether you can reproduce it, come from your own testing. Your email only needs to ask for the rest.

It's fine to escalate with a gap you've marked. The problem is a gap nobody wrote down.

Three rules for the ask

• Ask specific questions. "Did you change anything?" can get an honest "no" when a colleague or an integration made the change. Name the changes you want them to check instead.
• Ask for the exact text. "Some timeout error" and the real error copied word for word can send an engineer looking in two different places. Ask for a screenshot or the error text copied and pasted, plus the time and time zone.
• Keep it short. In email, use short paragraphs and put the next step on its own line at the end. In chat, ask one question at a time and wait for the answer before sending the next.

More templates for specific gaps

1. Asking for the exact error

Use this when the ticket describes the error loosely.

Subject: The exact error you saw

Hi Priya,

Thanks for the report. To get this to the right people quickly,
could you send me the error exactly as it appeared? A screenshot of
the whole screen is ideal, or copy and paste the text.

Please also tell me roughly when it happened, and your time zone.

If you can't find it now, that's fine. Next time it happens, grab it
then and reply to this email. Please blank out any passwords or
personal details first.

I'll [next step] by [day].

[Your name]

2. Asking what changed on their side

Use this one when the customer says "it worked until last week." First check your own releases, settings changes and maintenance for the same days, because that's the part you control.

Subject: Anything change around [date]?

Hi Priya,

To narrow this down, could you check whether any of these changed on
your side between [last day it worked] and [first day it failed]?

- New users or roles
- Changes to the [feature]'s settings
- New integrations
- Large data imports
- Network, proxy or single sign-on changes

Even small changes help. We're checking our side for the same days.

[Your name]

3. When it only happens sometimes

If you tried to reproduce it once and couldn't, keep the ticket open. Ask the customer to catch it next time, and set a date when you'll stop collecting.

Subject: Catching it next time

Hi Priya,

Since this doesn't happen every time, could you collect a few details
the next time it happens?

1. Note the time, and your time zone.
2. Write one line on what you were doing just before.
3. Take a screenshot of the whole screen, including any error.
4. If this happens in a web browser: press F12, click the Console tab,
   and take a screenshot of any red lines. (Skip this if it's unfamiliar;
   steps 1 to 3 are the important ones.)
5. Reply to this ticket with all of the above.

Please blank out passwords, keys and personal details first.

We'll collect until [number of times or date]. I'm keeping the ticket
open until then, and I'll check in on [date] either way.

[Your name]

4. When they've already sent it

Don't ask for it again. Tell them you've read it and what you did with it, and give them an owner and a date. If your team doesn't allow personal ownership, give the owner's name and the date.

Subject: Re: Stock sync still stopping

Hi Dana,

This is your third message about the overnight sync, and you've
already sent screenshots twice. I've read both, so I won't ask for
them again. [What you've done with them.] I'm keeping this ticket
with me until it's resolved.

You'll hear from me by [time, day] either way.

[Your name]

5. The chat version

In chat, ask one question and tell them what you're checking while you wait.

Thanks, I can see the failed sync on your account. One question: did
anyone add a new integration this week? Checking the logs on our side
in the meantime.

If they can't give you the answer

If an answer is still missing, decide whether to hold the escalation or send it now with the gap stated. Hold only when all three are true:

1. The missing answer can come back within one working day.
2. The customer's deadline is more than two working days away.
3. The case is Severity 3 or 4 on your severity guide.

Otherwise, send it now and say what's missing and why. Never hold a security or data exposure case. Follow your company's security policy for those.

Let AI find the gaps

You can paste a long thread into an AI assistant and have it fill in the five answers and point out what's missing. Only use a tool your company has approved for customer data. Before you paste anything, take out passwords, keys, tokens and any personal details you don't need.

From this ticket thread: [paste, secrets removed], fill in the five answers (did,
error, impact, repro, environment) and a "ruled out" line. Quote errors exactly.
Take facts only from the thread; write [MISSING] for anything not there. Then list
what to ask the customer, as a numbered list. Don't file anything. Draft only.

Check every quoted line against the thread yourself. For each [MISSING] item, decide whether your own testing can answer it or whether you need the customer. Put the customer's items into one of the emails above. What actually gets sent is still up to you.

Check before you escalate

Ask yourself whether an engineer could start on this without coming back to you with one question. If not, use the hold or send rule above and state the gap.

Improve the next escalation

Look at the questions engineering keeps sending back. If support could have answered one of them, include that answer up front next time. It also helps to agree on the five answers with engineering, so you're both checking the same list.

The free sample is one complete play from The CS Agent Playbook, the Escalation Brief for Leadership. It's a 3-page PDF with the prompt, a fill-in list, a sample output and guardrails. Get the free sample play

If engineering keeps sending your tickets back with questions, Ready to Escalate has 24 plays for support to engineering escalations, including The five answers and Reproduce from a known state.