Write a useful Cloud Markup support request

Start with a specific subject

Use a short description such as “Export download fails for revision 12” instead of “Not working.” Start at support.cloudmarkup.com so the request is filed under Cloud Markup. Use one ticket for one issue and keep its follow-up conversation together.

Include the essentials

1. The workflow you were using and the step where it stopped.
2. What you expected and what actually happened.
3. Organization, project, revision, or operation identifiers relevant to that step.
4. The exact error, time and time zone, and browser version.
5. A short reproduction sequence and what you already tried.

For a visual issue, attach a redacted screenshot with enough surrounding interface to show context. For generated output, identify the filename and include only the relevant non-sensitive excerpt.

Explain the impact

Choose Normal for a routine question, High when important work is blocked, or Urgent for a serious active interruption or security concern. Explain who is affected and whether a workaround exists. Priority helps the team triage; it does not create a response-time guarantee.

Keep secrets out

Never include passwords, AWS keys, invitation tokens, session cookies, or private customer data. If an AI article suggestion does not resolve the issue, reply with what you tried and ask for employee review. Your conversation remains available in My tickets.