Skip to main content

What to include when reporting a problem

Share time, screenshot, and what you were doing. Describing it in chat files the ticket.

J
Written by Josh Hunsaker

The single most useful thing you can give us is when it happened. Our engineers find the cause by looking at server activity around that moment. A timestamp turns a guess into a five-minute fix.

If you already described the problem in chat, it is filed. Missing an order number or screenshot does not mean you still need to send a ticket. Share what you have. We will ask if we need more.

Always helpful

  • Roughly what time it happened (even "about 10 minutes ago" works)

  • A screenshot of the error — the whole window, not a crop

  • What you were trying to do in plain words

  • The order, job, or item you were working on, if you have it

Not needed

Don't try to diagnose it for us, and don't retype error text. A screenshot is better than a transcription. Don't paste a request template unless we ask. If you were mid-way through something, tell us where you got to and whether you've tried again since.

If you're chatting from inside the tool

Most of this is captured automatically. Just describe what went wrong. That is the ticket.

Did this answer your question?