Support Surface

Public help content lives at the Support root; operator-only diagnostics stay behind platform roles.
Workspace users can reach help and contact paths without seeing Hangfire or worker-status tooling.

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.

Article

Before you save the account

Collect the provider host, ports, SSL posture, and any account-specific credential notes before you open the add-account screen. The goal is to validate ownership and connectivity once, not to bounce between edit and retry screens.

  • Confirm the mailbox belongs to the workspace you are currently operating in.
  • Know whether the provider still supports app passwords or basic auth for that mailbox.
  • Plan your initial send window so business-hours rules match the mailbox owner's expectations.

Article

After the account is live

Open the workspace dashboard and activity views immediately after the first mailbox is saved. Those surfaces now show queued and failed work, which should be your first stop before escalating an issue to support.

  • Check for early auth or health failures.
  • Review the workspace's current mailbox limit before inviting more operators to add accounts.
  • If a launch blocker appears, use the support request flow from inside the workspace so the ticket includes workspace context.

Related Articles

Keep reading

Open full help center
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.

Read article