Support Ticket Template: Examples You Can Copy

Most support inefficiency happens in the first two messages. A customer describes a problem without the details you need, you reply asking for them, and a resolution that could have taken one exchange takes three — with a day lost in between.

Support ticket templates fix this from both ends: structured intake so the right details arrive first time, and reply templates so agents aren’t rewriting the same explanation daily.

Intake templates

The goal is the minimum set of fields that lets an agent act without asking a follow-up question. Every field beyond that reduces completion.

General support request

Category:        [dropdown: Billing / Technical / Account / Other]
Subject:         [short text]
Description:     [long text — "What happened, and what did you expect?"]
Priority:        [Low / Medium / High]  ← treat as a hint, not an instruction
Attachments:     [optional]

Bug or technical issue

What went wrong:     [long text]
What you expected:   [long text]
Steps to reproduce:  [long text — numbered]
URL or screen:       [short text]
Browser / device:    [short text or auto-captured]
Screenshot:          [optional attachment]

Auto-capturing browser, device and page URL rather than asking removes three fields and gets better data — people report the browser they think they use.

Ecommerce / order issue

Order number:    [short text — required]
Issue type:      [Not delivered / Damaged / Wrong item / Return / Refund]
Item(s):         [short text]
Description:     [long text]
Photo:           [optional — required for damage]

The order number is the one field genuinely worth making required. Everything else can be inferred or asked; without it, every reply starts with a request for it. Our guide to reducing WISMO tickets covers preventing this category entirely.

Internal IT request

Request type:    [Access / Hardware / Software / Bug / Other]
System or app:   [short text]
Urgency:         [Blocking my work / Slowing me down / Not urgent]
Description:     [long text]
Asset tag:       [conditional — hardware only]

“Blocking my work” is a better urgency question than “Low/Medium/High”, because it asks about impact rather than asking someone to guess your priority scheme. See internal ticketing system for the wider setup.

Reply templates

These save typing without sounding automated — provided someone edits them before sending.

Acknowledgement

Hi {name},

Thanks for getting in touch — I’ve picked this up and I’m looking into it now.

{One sentence restating their problem in your own words.}

I’ll come back to you by {time}. If anything changes in the meantime, just reply here.

Restating the problem is the part that matters. It proves someone read it, and it catches misunderstandings before you spend an hour on the wrong thing.

Asking for more information

Hi {name},

Happy to help with this. To get to the bottom of it I need one thing:

{Specific request}

{One sentence on why you need it.}

As soon as I have that I should be able to sort it out.

Ask for one thing, not a list. Explaining why increases the reply rate noticeably.

Escalation

Hi {name},

I’ve looked into this and it needs input from our {team} team, so I’ve passed it over with everything you’ve sent.

{Named person or team} will pick this up, and you’ll hear back by {time}.

I’m still on the ticket, so reply here if anything else comes up.

Never escalate silently. A customer who doesn’t know their ticket moved assumes it was forgotten.

Resolution

Hi {name},

This should be sorted now — {what you did}.

{What they should see or do next, if anything.}

I’ll leave this open for a couple of days in case anything’s still not right. Just reply if so.

Bad news

Hi {name},

I’ve looked into this properly, and I’m afraid {clear statement of what isn’t possible}.

{The reason, briefly and without jargon.}

What I can do is {alternative}. {Or: I’ve passed the request to our product team, and I’ll let you know if that changes.}

Sorry it’s not the answer you were after.

Lead with the answer. Burying a “no” under three paragraphs of preamble makes people read it twice and trust you less.

Internal note templates

Not customer-facing, but the ones that save the most time on handovers.

Handover:

Status: {what's been done}
Blocked on: {what's needed}
Customer expects: {what you promised and by when}
Next step: {specific action}

Escalation to engineering:

Impact: {how many customers, how severe}
Reproduced: {yes/no + steps}
First reported: {date} — {n} tickets so far
Customer-facing workaround: {yes/no}

The “how many tickets so far” line is what gets engineering to prioritise. One report is an anecdote; fourteen is a pattern.

Making templates work

• Fewer, better. Five templates covering your most common replies beat fifty nobody can find.
• Always edit before sending. The template supplies the structure; the specifics of this customer make it not feel like a template.
• Review quarterly. Templates referencing discontinued features or old policies are worse than none.
• Keep tone consistent with your brand, not with a support-software default.
• Conditional fields beat long forms. Show the order-number field only for order issues.

Our canned responses guide goes deeper on writing replies people don’t resent, and live chat scripts and templates covers the real-time equivalent.

Where EasyChatDesk fits

EasyChatDesk supports custom forms with conditional fields for structured intake, and macros that apply a canned reply, set status and assign an owner in one click — inside CRM ticketing that keeps every template-driven reply attached to the customer’s full history.

Pricing is $17/agent/month with a 15-day free trial.

The takeaway

Templates aren’t about making support robotic — they’re about not retyping the same three paragraphs and not spending a day collecting an order number you could have asked for up front. Keep the forms short, keep the replies editable, and review them before they go stale.

Related: how to prioritize support tickets, canned responses guide, and what is a ticketing system.