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.

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.

Article

What to collect

A good escalation includes the workspace name, the affected mailbox or action, and whether the issue appears as queued, failed, or retried. That usually tells support whether the problem is capacity, configuration, or a code path that needs attention.

  • Capture timestamps in UTC when possible.
  • Note whether the failure is limited to one workspace.
  • Mention whether the issue concerns warmup sends or inbox actions.

Article

When operator tooling is appropriate

The Support operations console exists for platform support roles to inspect worker health, Hangfire pressure, and failed jobs. It is not the first stop for ordinary workspace users, and its presence should not leak into public help surfaces.

  • Workspace users should open a support request, not ask for dashboard access.
  • Support agents can correlate workspace reports with job failures after the ticket arrives.
  • Hangfire visibility should confirm, not replace, workspace-facing product signals.

Related Articles

Keep reading

Open full help center
Handle repeated auth failures before they become an outage Workspace operators

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

Read article