Help Center

Self-service guidance for onboarding, billing, workspace access, and runtime reliability.

Browse the help center, support policies, and onboarding guidance before creating a workspace.

The public support surface is intentionally separated from internal operator tooling and paid-tier channels.

Public support Self-service guidance active Operator tooling stays separate

Onboarding

Start the workspace cleanly, connect the first mailbox, and avoid skipping the launch checks that matter.

Connect the first mailbox with the right launch checks

Use the first mailbox connection as the ownership, provider, and business-hours validation step instead of treating it like a raw credential form.

Workspace owners and admins Read article

Review business hours before turning the warmup runtime loose

Business-hours settings drive the tone of the first warmup wave. Treat them like a launch control, not an afterthought.

Workspace owners and operators Read article

Billing and plans

Understand what each plan unlocks, when support changes by tier, and how to move from trial into a paid workspace state.

Understand seats, mailboxes, and support by plan

Plan limits now drive the pricing page, workspace billing surface, and support messaging. Review them in one place before you add users or mailboxes.

All workspaces Read article

Move from trial to paid without losing support context

The workspace should cross from trial into paid state cleanly so mailbox capacity, runtime access, and support-channel messaging stay consistent.

Workspace owners Read article

Workspace access

Keep team access deliberate, avoid plan-limit surprises, and route support from the correct workspace context.

Invite users without losing track of reserved seats

Pending invitations now reserve seats, so member management and support messaging should start from the workspace overview instead of guesswork.

Workspace owners and admins Read article

Switch workspaces safely before you troubleshoot

Many apparent support issues are really workspace-context issues. Confirm the current workspace first.

All signed-in users Read article

Reliability and troubleshooting

Use the new workspace-facing queue and failure visibility before escalating to internal support operations.

Read queued and failed work before escalating

The app now exposes queued and failed work so users and support agents can start with real runtime state instead of only raw anecdotes.

Workspace operators and support agents Read article

Handle repeated auth failures before they become an outage

Credential issues now fail closed more cleanly, but operators still need a repeatable response path when an account stops authenticating.

Workspace operators Read article

Featured

Start here

Need human follow-up?

Connect the first mailbox with the right launch checks Workspace owners and admins

Use the first mailbox connection as the ownership, provider, and business-hours validation step instead of treating it like a raw credential form.

Open article

Review business hours before turning the warmup runtime loose Workspace owners and operators

Business-hours settings drive the tone of the first warmup wave. Treat them like a launch control, not an afterthought.

Open article

Understand seats, mailboxes, and support by plan All workspaces

Plan limits now drive the pricing page, workspace billing surface, and support messaging. Review them in one place before you add users or mailboxes.

Open article

Move from trial to paid without losing support context Workspace owners

The workspace should cross from trial into paid state cleanly so mailbox capacity, runtime access, and support-channel messaging stay consistent.

Open article

Invite users without losing track of reserved seats Workspace owners and admins

Pending invitations now reserve seats, so member management and support messaging should start from the workspace overview instead of guesswork.

Open article

Switch workspaces safely before you troubleshoot All signed-in users

Many apparent support issues are really workspace-context issues. Confirm the current workspace first.

Open article