Open an effective support ticket
What each field is for, and what makes a ticket resolve faster.
The ticket form asks for a specific set of fields because each one saves a round trip:
- Business email — where we reply; use the one linked to your account if you have one
- Company/organization — helps us route Enterprise-adjacent questions correctly
- Request type & product/service — routes the ticket to the right queue immediately
- Severity — see support severity levels; be honest rather than optimistic or alarmist
- Error code & approximate incident time — lets us find the exact failure faster than a vague description
- Description — what you were doing, what you expected, and what happened instead is worth more than a one-line summary
Never include passwords, MFA codes, API secrets, access tokens, private keys, or other credentials in a ticket — see the warning on the form itself. If a screenshot or log would help, link to it rather than pasting raw secrets.