Creating Effective Support Tickets
The quality of information you provide directly impacts how quickly and effectively we can resolve your issue. A detailed, well-structured ticket can save hours—or days—in the resolution process.
What Every Ticket Should Include
Four essential elements belong in every ticket:
- What you were attempting
Your specific action or goal. - Expected outcome
What should have happened. - Actual outcome
What actually occurred. - When it occurred
The date and time, ideally with your time zone.
Additionally, include relevant identifiers such as email addresses, domain names, and message IDs.
Specifics beat summaries
“Mail to jane@example.com bounced at 14:05 UTC with a 550 error” tells us far more than “email isn’t working.” Concrete details let us reproduce and trace the problem immediately.
Do’s and Don’ts
| Avoid | Instead |
|---|---|
| Speculative diagnoses or assumptions about root causes | Describe observable facts and specific behaviors |
| Vague generalizations (“I’m not receiving any email”) | Provide concrete examples with timestamps |
| Multiple unrelated issues in one ticket | Open one ticket per distinct issue |
| Emotional language that obscures technical details | Include error messages and screenshots |
One issue per ticket
Combining several unrelated problems into a single ticket slows everything down. Each issue may need a different specialist, so split them into separate tickets.
Whenever possible, also mention any troubleshooting you’ve already attempted—it saves us from suggesting steps you’ve already ruled out.
Before You Submit
A few quick checks before contacting support often resolve the issue faster:
- Check the knowledge base for existing solutions.
- Search community forums for similar issues.
- Gather error messages, screenshots, and relevant dates.
Ready to reach out? You can open a ticket at design@overton.cloud. For common issues, see Common Error Messages first.