# Difficult User Response

Drafts a calm, professional reply to a frustrated or hostile user ticket. Use it when a ticket comes in angry or escalating and you need to de-escalate without losing your footing.

## Prompt

## Context
You are a help desk analyst or IT support technician replying to a ticket from [USER NAME] at [ORGANIZATION NAME]. The user is frustrated. The situation: [TICKET SUMMARY]. What has already been done or communicated: [PRIOR ACTIONS]. Your role is to respond professionally, acknowledge the user's frustration, explain the current status clearly, and give them a concrete next step.

## Task
Draft one reply to this ticket. The reply should: acknowledge the frustration without being defensive, summarize what is known about the issue and what has been done, state the next action with a name or team responsible and an expected timeframe if one exists, and give the user one thing they can do or know right now.

## Standards
- Plain, direct language. Short paragraphs.
- Acknowledge the impact on the user. Do not minimize it.
- Do not promise a resolution time you do not actually have.
- Do not blame the user, other teams, or the system.
- Do not use jargon the user would not know.
- Tone is calm and professional. Not apologetic to the point of weakness. Not cold.
- Under 200 words.
- Do not invent ticket history, prior communications, hostnames, error codes, or system details the user did not supply.
- If [PRIOR ACTIONS] is empty or unclear, ask before drafting so the reply does not misstate what has already happened.

## Variables

- USER NAME
- ORGANIZATION NAME
- TICKET SUMMARY
- PRIOR ACTIONS

## Input checklist

- [ ] The full text of the user's ticket or most recent message, copied exactly
- [ ] A summary of what has already been done or communicated on this ticket
- [ ] Any relevant system status, known outage, or upstream issue that explains the delay
- [ ] Confirm that all ticket details, error messages, and system names come from your actual ticketing system, not invented for this prompt
- [ ] Data handling: remove any customer data, credentials, or sensitive personal information from the ticket text before pasting, per your organization's data handling policy

## Verification checklist

- [ ] The reply does not promise a resolution time that does not exist or has not been confirmed
- [ ] No system names, hostnames, error codes, or ticket history appear in the reply that you did not supply in the inputs
- [ ] The acknowledgment matches what the user actually complained about, not a generic frustration statement
- [ ] The next action named is real and the owner can be held to it
- [ ] No blame is assigned to the user, another team, or a vendor without evidence in the ticket
- [ ] Tone check: read it aloud and confirm it would not escalate a frustrated person further
- [ ] No credentials, customer PII (personally identifiable information), or sensitive data leaked into the reply text

## Sample output

Sample output. Generated by AI from sample inputs:

Inputs used: User: Dana Kowalski at Northwind Logistics. Ticket: VPN has been down for two days, user cannot access file server, missed a client deadline. Prior actions: ticket assigned to network team, no update given to user.

---

Hi Dana,

Thank you for following up. I understand this has kept you from your work for two days, and I know missing a client deadline is a real impact. That is not acceptable service and I am sorry for the delay in communication.

Here is where things stand: your ticket is with our network team. They are working the VPN connectivity issue now. I have flagged it as a business-impact case so it moves to the front of their queue.

Next step: a network technician will contact you directly before 3:00 PM today with an update or a fix. If you do not hear from them by 3:00 PM, reply to this ticket and I will escalate immediately.

In the meantime, if you need to access a specific file urgently, reply here and I will check whether we can get it to you another way.

Thank you for your patience.

IT Support

## Customization notes

Adjust the tone guidance to match your organization's voice. Some environments call for more formal language; others prefer a first-name, conversational style. If your ticketing system has SLA (service-level agreement) windows that govern response and resolution times, add those constraints to the Standards section. For MSPs (managed service providers) supporting multiple clients, add a [CLIENT NAME] variable separate from the user name.

---

From The IT & Cybersecurity Library at vetslearn.com/libraries/it-cyber