# Ticket Response Builder

Drafts a clear, professional response to an open support ticket. Use it when you need a well-structured reply that addresses the user's issue without over-explaining or leaving gaps.

## Prompt

## Context
You are an IT support technician or help desk analyst drafting a response to a support ticket. The ticket was submitted by [USER NAME] in [DEPARTMENT]. The ticket system is [TICKETING SYSTEM, e.g., ServiceNow, Jira Service Management, Zendesk]. Ticket summary: [TICKET SUMMARY]. Current status: [CURRENT STATUS, e.g., in progress, awaiting parts, resolved]. Any actions already taken: [ACTIONS TAKEN].

## Task
Write a professional ticket response that:
- Acknowledges the issue in one sentence, using the user's own words where possible.
- States what has been done so far, if anything.
- Describes the next step and who owns it.
- Gives a realistic timeline for resolution or next contact: [EXPECTED TIMELINE].
- Closes with a direct offer to follow up.

## Standards
- Under 150 words. Plain language a non-technical user can follow.
- No jargon without a brief explanation.
- Confident and specific. Avoid "we will try" or "hopefully." State what will happen and when.
- Do not promise resolution if you cannot guarantee it. State the next concrete step instead.
- Do not invent ticket details, system names, error codes, or resolution steps that were not provided.
- If the ticket summary or actions taken are missing or ambiguous, ask before drafting rather than filling in plausible details.

## Variables

- [USER NAME]
- [DEPARTMENT]
- [TICKETING SYSTEM]
- [TICKET SUMMARY]
- [CURRENT STATUS]
- [ACTIONS TAKEN]
- [EXPECTED TIMELINE]

## Input checklist

- [ ] The ticket summary in the user's own words, copied from the ticket, not paraphrased from memory
- [ ] A list of actions already taken, from your own notes or the ticket log, not from memory
- [ ] A realistic timeline you can actually hold to. Do not guess a date you cannot commit to
- [ ] All technical artifacts (error codes, asset names, system names) must come from the actual ticket and your own systems, not from the AI
- [ ] Redact any credentials, passwords, account numbers, or personal data before pasting ticket content, per your org's data-handling policy

## Verification checklist

- [ ] Every action listed in the response actually occurred. Do not let the AI add steps you did not take
- [ ] The timeline is one you can keep. If the AI suggested a date, confirm it against your queue and parts availability
- [ ] No invented error codes, hostnames, asset tags, or system names appear in the draft
- [ ] Jargon is either removed or explained in plain language
- [ ] The next step is concrete and names who owns it, not a vague 'we will look into it'
- [ ] No user personal data or credentials appear in the draft

## Sample output

Sample output. Generated by AI from sample inputs:

Hi Sergeant Martinez,

Thanks for submitting a ticket about your VPN connection dropping after the Windows update on June 10.

I've reviewed your device logs and confirmed the issue is a known conflict between the updated network adapter driver and our VPN client. I've pushed a corrected driver to your machine (WEB-APP-03). The push is scheduled to run tonight during the maintenance window.

You should be able to connect normally by 0800 tomorrow. Please test it then and reply here if the issue continues. If it is still dropping, I will remote in directly to resolve it the same morning.

Ticket: INC-4821
Next contact: 0800 June 14

## Customization notes

Adjust the word count and formality to match your organization's tone. Government and defense environments often require more formal language and a specific ticket number in the closing. If your ticketing system auto-sends responses, paste the draft there directly. If a technician edits before sending, add a line in verification asking that editor to confirm the timeline against their own queue.

---

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