12/10/2026 21:57
Support Screenshots: Show the Issue Without Exposing Secrets
A screenshot can make a ticket clearer when it shows the relevant observation and protects private information. KhmerBoosting customers should pair the image with the accepted reference and a concise explanation. Support should not have to guess which row matters, and a picture should never reveal login or API credentials.
Reader note: Service availability, targeting and delivery depend on the individual listing. Review platform rules and the current Services catalogue before ordering. The illustrations are conceptual, not actual campaign results.
Capture the relevant area
Show the order, payment state or visible error that needs review. Avoid including unrelated browser tabs, private messages or customer data. Keep enough context to explain the observation, but do not make a large image the only description of the problem. The written reference and issue summary remain essential for locating the record.
Redact sensitive information
Remove passwords, API keys, recovery codes, session details and other secrets before attaching an image. A payment review may need a transaction reference, not access to your payment account. Keep any required information in the private ticket rather than posting it publicly. Check the final image again so an accidental corner of the screen does not expose something unrelated.
Explain time and expectation
State when you took the screenshot and what you expected based on the selected listing or payment instructions. Include the relevant time zone if timing affects the question. Avoid guessing the provider's internal cause. A factual observation is more useful than a confident explanation that the available records cannot verify.
Keep the conversation connected
Use the KhmerBoosting accepted order or payment reference and answer clarification requests in the same thread. Do not repeatedly place orders or payments as a diagnostic experiment. The screenshot supports the evidence; it does not guarantee a particular remedy. A coherent ticket makes it easier to identify the next authorized action.
Quick questions
Should I include an API key to help support investigate?
No. Never attach secrets or account-access information to a screenshot.
Where can I review the current offer?
Use the Services catalogue and selected description. For account-specific questions, sign in and use Tickets.
Continue your planning
Review available services · Read customer API documentation · Browse common questions. For account-specific help, sign in and open Tickets. Never include passwords or secret keys.