Get unstuck without losing the signal.

Search the public help center, check live status, or create a workspace-linked ticket for credentials, channels, origins, usage, and production readiness.

⌕6 results

Support flow

Online

Path

Search, diagnose, then open a focused ticket.

Public help stays open. Workspace-specific support stays attached to the signed-in account.

Support paths

Choose the fastest route.

Start with docs

Use the public docs for setup, keys, channels, security, and common fixes.

Read docs →

Check status

See current availability, component health, and recent public incident notes.

View status →

Open a ticket

Send a workspace-linked request when an issue needs private context.

Create ticket →

Knowledge base

Answers before tickets.

Use these focused guides first. They are public, fast to scan, and written for real setup issues.

Workspace ticket

Open a private support request.

Tickets require a workspace account so the request can stay connected to the right apps, plan, and reply history.

Affected app

Mention the app name, environment, and region when it matters.

Channel details

Include the channel name and whether it is public, private, or presence.

Error message

Paste the exact error or denial message you are seeing.

Urgent cases

Use urgent priority for credential exposure or production outage concerns.

Get unstuck without losing the signal.

Choose the fastest route.

Answers before tickets.

First app setup

Credentials and key rotation

Private channel authorization

Presence channel payloads

Trusted origins

Usage and plan limits

Open a private support request.

Public help is open. Tickets stay workspace-linked.