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

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.

Article

Why this matters

The warmup planner depends on business hours to avoid awkward send timing. If business hours are left wide open, the runtime can look healthy while still acting in a way that surprises the team using the mailbox.

  • Use narrower windows during the first warmup days.
  • Mirror the actual team schedule instead of a generic 24/7 template.
  • Review the setting again after adding new mailboxes or new regions.

Article

When to escalate

Escalate only after you have confirmed the schedule, account status, and queued work state from the workspace UI. That gives support the context needed to tell a configuration problem from a runtime bug.

  • Capture the workspace name and the mailbox involved.
  • Mention whether the issue is isolated or repeats across multiple accounts.
  • Use the paid support queue if the workspace already has active paid support.

Related Articles

Keep reading

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

Read article