# Good and bad examples of a problem ticket We love it when merchants provide context and actionability in a support ticket. This allows our support team to focus on solving the problem quickly and efficiently, ultimately leading to a better customer experience. Here’s a bad and good example:
Bad ❌Good ✅  Why? It provides context and is actionable

Hello,

It’d be great if you could take a look at our store, seems like a sync issue.

Thanks












Hello,


I'm having an issue with DotApparel. I'm hoping you can help me out!


So far, I've looked into the issue and noticed that [summary of what you've done to solve the problem].

I've attached [any relevant screenshots] so you can get a better idea of what's going on. I was under the impression that [briefly explain your understanding].

However, the problem I'm experiencing is [describe the issue]. Can you please assist me with resolving this issue?

Let me know if there's any additional information you need from me or if there are any steps I should take on my end.

Thanks for your help!

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.dotapparel.com.au/core/troubleshooting/good-and-bad-examples-of-a-problem-ticket.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.