Help center
Available nowAll visitors and all tiers
Read onboarding, billing, workspace, and reliability guidance without signing in.
Queue treatment: Self-service
How can we help you improve your deliverability?
AI support chat
Locked to paid tiersPaid workspaces
Start here for AI-backed guidance on onboarding, billing surfaces, workspace state, and runtime troubleshooting before escalating to human support.
Queue treatment: AI guidance plus standard human follow-up
Email ticketing
Locked to paid tiersPaid workspaces
Route billing questions, launch blockers, and product issues into the support inbox with workspace context.
Queue treatment: Standard email queue
Onboarding
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 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
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
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 →
Start here
Connect the first mailbox with the right launch checks
Workspace owners and adminsUse 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 operatorsBusiness-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 workspacesPlan 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 ownersThe workspace should cross from trial into paid state cleanly so mailbox capacity, runtime access, and support-channel messaging stay consistent.
Open article →Support Policy
Channel availability
Support entry points are intentionally tier-aware so the product shell, pricing surfaces, and help center tell the same story.
Escalation path
The expected launch path moves from self-service guidance into paid support only when the issue needs human intervention.
Response expectations
The UI communicates queue treatment even before a full SLA document lands in the broader launch policy set.