Customer portal
Invite loops, wrong customer association, missing invoices, and permission errors—symptom-first steps for CS teams.
2 symptoms covered
Dispatch
Capacity overload, wrong assignments, invisible backlog, and access-related failures—symptom-first triage aligned to dispatch triage workflows.
2 symptoms covered
Inventory
Truck stock vs warehouse, unexplained shrink, and dispatch promising parts that aren’t pickable—symptom-first checks tied to replenishment workflows.
2 symptoms covered
Invoices & payments
Payment links, portal pay failures, mismatched totals, and collections cadence issues—operations-first triage linked to quote-to-cash workflows.
2 symptoms covered
Offline / mobile
Captures that don’t upload, photos stuck pending, and conflicts after reconnect—mobile-first triage for field teams.
2 symptoms covered
Permissions
‘Access denied’, missing menus, and field-level hides—RBAC-first triage for admins without turning security into guesswork.
2 symptoms covered
QuickBooks export
Issue-first guidance for export mismatches, mapping errors, duplicates, and period locks—written for ops and finance, not as tax advice.
3 symptoms covered
Reporting
When dashboards disagree with finance or dispatch—definition alignment, time zones, and grain mismatches first.
2 symptoms covered
Syncing & data
Symptoms like stale lists, missing updates across devices, and delayed dashboards—structured checks before assuming a bug.
3 symptoms covered
Technician access
Mobile access, MFA, device limits, role templates, and offline behavior—symptom-first checks that reduce “can’t log in” churn.
2 symptoms covered
Work orders
Symptom-first fixes for assignment failures, duplicate records, missing asset context, and completion bottlenecks—linked to workflows and product areas.
3 symptoms covered
FAQ
- How is this different from general Help Center articles?
- Troubleshooting pages are issue-first: symptoms lead to short quick answers, expandable step lists, and curated links to workflows and product areas. Articles teach concepts; this library helps you resolve incidents faster.
- Why symptom-based navigation?
- Customers and technicians search the way failures feel (“won’t assign”, “stuck pending”, “numbers don’t match”). Symptom anchors improve long-tail SEO and AI retrieval by matching intent language directly.