Skip to content

Troubleshooting and known patterns

How to describe a problem so support can act quickly

This section covers the most common reasons users think something is broken when the real issue is permissions, cache, wrong workspace, or outdated assumptions.

The best issue report is short but complete. Include the route, the workspace, the expected outcome, the actual outcome, and the approximate time. If there is a visible error, send the exact text instead of paraphrasing it.

When the issue is email-related, include sender, recipient, subject, and approximate send or receive time. When the issue is inbox-related, include the conversation type and where you expected it to appear.