How can we help you improve your deliverability?

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.

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.

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.

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.

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.

Switch workspaces safely before you troubleshoot

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

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.

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.