Open an Organization Support Ticket

Submit a safe, well-scoped support request for the correct customer organization.

Before you begin

• Confirm that the organization owns the affected product, workspace, invoice, payment, or service.
• Review existing organization tickets to avoid reporting the same issue twice.
• Collect authorized evidence, exact timing, impact, expected result, actual result, and troubleshooting already completed.

Open the ticket

1. Open Open Organization Ticket.
2. Enter a specific subject that names the issue or requested outcome.
3. Select the correct organization when the account has access to more than one.
4. Choose a priority that reflects the actual operational impact.
5. Select the affected product or service when the option is available.
6. Choose the general, technical, or billing lane when your organization role permits it. Otherwise, review the lane assigned by the application.
7. Use the Markdown description to explain the context, steps, timing, expected result, actual result, impact, and actions already taken.
8. If you use Draft with BI, treat the result as a draft. Verify every statement and remove unnecessary information.
9. Attach only files that are authorized and necessary to understand the request.
10. Review the complete request and select Create Ticket.

Protect sensitive information

Never include passwords, one-time codes, private keys, API keys, access tokens, secret configuration, unrelated customer records, or unnecessary personal information. Redact screenshots and logs before attaching them. A support request does not authorize broader disclosure.

Use priority and lanes carefully

• Use technical support for product errors, access failures, APIs, integrations, and reproducible defects.
• Use billing support for invoices, payments, credits, renewals, subscription changes, or charge questions.
• Use general support when neither specialized lane is appropriate.
• Do not mark a request urgent solely to accelerate a normal request.

Completion check

• The ticket has a generated number and belongs to the intended organization.
• The subject, priority, lane, and description accurately represent the request.
• Attachments contain no secrets or unauthorized records.
• The ticket appears in Organization Tickets for follow-up.

Related tasks

Continue to Review and Manage Organization Support Tickets, use Troubleshoot a Batoi Workspace Task, or return to the Account, Support, and Billing guide.

Open an Organization Ticket