How to write a support ticket that is easy to resolve

A useful ticket makes the problem understandable without repeatedly asking for the same information. Gather the details from your account and briefly describe what you expected and what happened.

Start with the reference

For an order, include its ID and service. For a top-up, use the reference shown by SoneBoost. If a payment is pending, include its visible status and approximate time; returning from a payment provider does not itself establish that the money is confirmed.

Describe a concrete sequence

For example: “I submitted the order, its status changed to processing, and the link is still public. This is the count I now observe.” Avoid combining several incidents without separating their references. If a ticket already exists for the same case, continue that conversation.

Attach only what is needed

A screenshot can show the error and status. Crop information about other accounts and hide full card numbers, documents, passwords, API keys and recovery codes. Support does not need those credentials to follow your order.

Say what help you need

Ask for a status explanation, a delivery review or information about the service’s refill coverage. Do not send another payment or duplicate the order as an attempt to resolve a pending problem.

Keep the response in the ticket so the context stays together. A history of references, dates and specific observations makes the case easier to review and later changes easier to understand.