Support and Escalation

Use this page when a workspace issue needs human follow-up rather than self-serve troubleshooting.

Support Page

Route: /dashboard/organization/support

Use this page to:

• submit a real support request with organization context attached
• prefill the request with the signed-in user identity
• use the built-in fast links to documentation, integrations status, and billing settings

What Gets Sent

The support request includes:

• organization name
• signed-in user name and email
• subject
• freeform details entered in the form

If Turnstile is enabled in the current environment, the page also requires captcha completion before submit.

What To Include In A Good Ticket

• the exact route where the issue happened
• the organization name
• relevant deployment IDs, package IDs, digests, or timestamps
• whether the issue is billing, provisioning, API, webhook, or access related
• what you expected to happen

Fast Paths Before Escalation

• Open /docs for feature walkthroughs
• Open /dashboard/organization/integrations to verify automation posture
• Open /dashboard/organization/settings?tab=payment-methods for billing-portal actions

Escalation Guidance

• Use support for user-facing issues that need human follow-up
• Use Audit Log, Activity, and Integrations first when the issue looks operational and can be self-triaged