A support ticket is a written request for help, sent to a company’s support team through a form, email or chat, and tracked until it’s resolved. A well-written ticket gets solved faster, because the agent can start working on it instead of asking you questions first. Most of the back-and-forth on a ticket comes from three missing things: what you were trying to do, what exactly happened, and proof of it.
This guide shows how to write a support ticket that gets a fast answer, with a copyable template and examples. If you work in support, you can send it to customers, or use it to write internal tickets to engineering.
What to include in a support ticket
- A specific subject line. Name the feature and the symptom: “CSV export fails with an error on saved reports,” not “Urgent!!” or “Help.”
- What you were trying to do. The goal, in one sentence. Agents sometimes know a faster way to get there.
- Steps to reproduce. Numbered, starting from a page the agent can open. Include the exact buttons you selected.
- Expected and actual result. What should have happened, and what happened instead. Copy error messages word for word.
- When it started and how often. “Since this morning, every time” is very different from “once last week.”
- Your environment. Account or workspace name, your role, browser and version, device, and operating system. For mobile apps, the app version.
- Who is affected and the impact. Just you, your team, or all your customers? Are you blocked, or is there a workaround?
- Evidence. A screenshot with the problem marked, or a short screen recording. Don’t send passwords, card numbers or other secrets.
Support ticket template
Copy this into the support form or email and fill in each line:
Subject: [Feature or page] – [what goes wrong] What I'm trying to do: [One sentence] Steps to reproduce: 1. Go to [page or URL] 2. Select [button or menu] 3. [Next step] Expected result: [what should happen] Actual result: [what happens, with the exact error message] When it started / how often: [date or time, every time or sometimes] Account: [workspace or company name, your role] Browser and device: [e.g. Chrome 141 on Windows 11] Impact: [who is affected, any workaround] Evidence: [screenshot or recording link]
Support ticket examples
A ticket that will need three more emails
Subject: Not working
Exports are broken again. Please fix ASAP.
The agent has to ask which export, what “broken” means, which account, and since when, before they can even try to reproduce it. Each question adds hours to the reply.
A ticket that can be solved in one reply
This example is fictional:
Subject: CSV export of saved reports fails with “Export failed (500)”
I’m trying to export our “Q3 refunds” saved report as a CSV for our finance team.
1. Go to Reports > Saved reports
2. Open “Q3 refunds”
3. Select Export > CSVExpected: a CSV file downloads.
Actual: after about 5 seconds, a red banner says “Export failed (500)”. PDF export of the same report works.Started this morning, happens every time. Account: Northwind (I’m an admin). Chrome 141 on macOS 15. It blocks our month-end close, so the whole finance team is affected. Recording attached.
The agent can open the same report, see that only CSV fails, and pass a precise case to engineering if needed.
Why a screen recording beats a long description
Many issues are easier to show than to explain: a button that does nothing, a layout that breaks at one width, an error that flashes and disappears. A 30-second recording answers most of the agent’s questions at once. When the support team sends you a recording link (Screendesk lets agents send a link from the ticket, and customers record without installing anything), the video goes straight back to your ticket, so nothing gets lost in an attachment. If the agent asks for a HAR file instead, see how to get a HAR file.
For a still image, capture just the relevant part of the page, circle the problem and blur personal data. How to take a full-page screenshot in Chrome covers the options.
Tips for a faster resolution
- One problem per ticket. Two unrelated issues in one ticket often means one gets forgotten, or the ticket bounces between teams.
- Reply in the same thread. A new ticket for a follow-up loses the history and can go to a different agent.
- Set the right priority. Reserve “urgent” for outages and blocked work. If everything is urgent, nothing is.
- Say what you already tried. Clearing the cache, another browser, another account: it saves the agent from suggesting the same steps.
- Keep secrets out. Support will never need your password. If they need access, they’ll ask for it through a secure process.
For support teams: get better tickets
You can’t make every customer write the perfect ticket, but you can make it easier. Add the template fields to your contact form as separate inputs, ask for the browser and account automatically where possible, and give customers a one-click way to record their screen instead of describing it. When a ticket needs engineering, use a consistent handoff: our support ticket escalation process and Jira bug report template cover the internal side.
Frequently asked questions
What is a support ticket?
A support ticket is a record of a customer’s request for help in a help desk system such as Zendesk, Intercom, Freshdesk or Help Scout. It holds the conversation, status, priority and owner, so the request can be tracked until it’s resolved.
How long should a support ticket be?
As short as possible while still answering the template questions: what you tried to do, the steps, expected and actual results, your environment, and evidence. Five to fifteen lines is typical.
What is a good subject line for a support ticket?
Name the feature and the symptom in under ten words: “Invoice PDF shows the wrong VAT rate” or “Can’t invite users: ‘seat limit reached’ error.”
