Status
A readable map. No painted dots.
A live status page is not up yet, and this one will not pretend to be it. It explains what is monitored and how incidents are communicated, and it will not show you a green light it is not measuring.
What the live page will track
The board and dispatch
Scheduling, assignment, and the day’s view
The field app
The web app in the truck; native iOS and Android when they reach the stores
Estimates and invoices
Writing, sending, approvals
Payments
Collection on the job and payout visibility
The shop number
Voice and texting, where enabled
The API and webhooks
Ordinary calls, integrations, the developer surface
The refusal
No dot we are not measuring.
A marketing page that renders “all systems operational” from a template is decoration, not information. Uptime numbers appear when they come from measurement you can inspect, the same rule this site applies to reviews and metrics everywhere else.
When something breaks
How incidents are communicated.
Plain words, not color codes
An incident note says what is broken, who is affected, and what to do in the meantime, in operating terms a dispatcher can act on. Status should reduce uncertainty, not just report color.
Updates while it is broken
When the live page is up, it will carry timestamps during an incident, and the note will be updated as the picture changes, not once, afterward, in the past tense. Until then, support answers by email.
A postmortem when it matters
Incidents that cost shops real time get a written account: what happened, why, and what changed so it does not repeat.
Something look wrong right now? Email support@thorbis.com with the screen and the job. A person responds, and a real incident gets a real note.
Status
Trust is a record too.
The same stance as everywhere else on this site: measured numbers or no numbers. See how the rest of the product earns it.
Coming from a suite? We’ll extract your records.