Help Center›Getting Started

How do I write a good support request?

For everyone · Updated July 7, 2026

Use this when help articles do not answer the question and you are about to submit a request.

Include this

  1. What you were trying to do.
  2. What happened.
  3. What you expected instead.
  4. The page or workspace you were on.
  5. The customer, project, event, invoice, employee, or vendor involved.
  6. The office, date, and device if relevant.
  7. A screenshot when the issue is visual.

Pick the right type

Bug means something is broken or wrong, Feature idea means something new would help, and Question means you need help doing something. The form asks short follow-up questions based on the type you pick. Answering them speeds everything up.

Automatic context

The page you filed from and your browser details are attached automatically, so you do not need to describe your setup unless something about it matters.

Best practice

Avoid writing only "it does not work." One or two specific sentences plus a screenshot usually gets a useful reply on the first pass.