ROUTE THE QUESTION
Pick the path that matches the problem.
Broad platform incidents, stuck workflows, and account-specific questions each have a faster lane.
Active incidentUse the live status host for update cadence, affected components, and subscription management.Open status hostWorkflow issueWhen the platform is green but one task is stuck, use the Help Center for product-specific recovery.Open help centerAccount-specific supportSend the product area, company, timestamp, and role so support can investigate the right path.Contact support
DURING AN INCIDENT
Everyone needs a different next step.
Who does what while the status page is yellow — and what to send support so the workflow can be traced.
WHO DOES WHAT
- OwnerDecides whether the team pauses a workflow, uses a fallback, or waits for the live status update.
- DispatcherKeeps the schedule moving and notes which jobs or technicians are affected by the service area.
- OfficeCollects customer, invoice, payment, and browser context for account-specific support.
- TechnicianReports the job, device, app state, and customer impact instead of retrying without context.
WHAT TO SEND SUPPORT
- WhoCompany, user role, workspace, and affected team member.
- WhereProduct area, page, record type, customer, job, invoice, payment, or mobile screen.
- WhenTimestamp, timezone, browser or device, and whether the issue is still happening.
- ImpactWhether customers, technicians, payments, dispatch, or reporting are blocked.
HOW WE COMMUNICATE
Status should reduce uncertainty, not just report color.
01
Time-stamped updates
Incident communication should make sequence and current state clear, even when the root cause is still under review.
02
Workflow impact
Status should explain what customers can still do, what is degraded, and which fallback path to use.
03
Post-incident learning
After recovery, the review should name the customer impact and the operational change that follows.