Status and support expectations before rollout.

Review support targets, incident communication, launch coverage, and status reporting before purchase.

Status and SLA visibility

A visible health path before a formal uptime history exists.

HexaFit exposes the current health route and explains how status, incident updates, escalation, and response targets become part of the customer proposal or service terms.

Open Health Check Open Status History Data

Live status reviewSystem health and event history

Shows current health, public status events, and response-target examples for reviewer inspection.

History starts from the public monitoring surface; no pre-existing uptime percentage is invented.

Priority 1Production outage or critical access/payment disruption

Proposal-defined emergency response path

Priority 2Major workflow degradation affecting a location or team

Business-hours triage target in service terms

Priority 3Configuration, data, training, or non-critical workflow issue

Queued support response by support plan

Status history

Public status history starts from the live monitoring surface.

HexaFit shows current public events and does not invent an uptime percentage before enough history exists.

2026-07-01Operational

Public health check available for live review.

/api/health

2026-07-01Monitoring started

Public status history surface added. No historical uptime percentage is claimed before data exists.

/api/status/history

Open Status History Data Open Health Check

Support path

Know what happens when your team needs help.

Support should be easy to understand before launch: how requests enter, who reviews them, and how updates are shared.

Request

The team submits the issue with location, user, and workflow context.

Support channel

Triage

HexaFit identifies impact, urgency, owner, and next action.

Response target

Update

Admins receive clear updates for incidents, maintenance, or launch blockers.

Status update

Resolve

The fix, workaround, or configuration change is confirmed.

Resolution

Review

Launch lessons, recurring issues, and training needs are captured.

Post-review

Improve

Process changes feed into rollout planning and support expectations.

Action plan

HexaFit command centerAll locations. One clear view.

Support target
Escalation path
Incident updates
Launch coverage

Specialist routeContact sales or book demoSupport targetDefined in proposalStatus pagePublic status path readyView Status Path

Support review

Define response expectations before launch.

Support channels, targets, and incident paths should be clear before rollout.

Public status path

Live health and public status history are available for current review and future incident history.

Support targets

Response targets, escalation contacts, and support channels should be defined in the customer proposal or service terms.

Incident communication

Enterprise buyers can review how planned maintenance, service degradation, and resolution updates will be communicated.

Launch support

Implementation plans should define launch coverage, training windows, admin handoff, and post-go-live review.