Appearance
Decide dispatch vs remote fix on a field support call
Harbor Retail gets the call: a brand partner says screens are dark at open. Support must choose remote fix versus dispatch without guessing. When every responder debugs differently and device or site context is missing, dispatch becomes the path of least resistance - and the expensive one for a mall visit.
The same decision shape shows up on Northstar warranty and depot calls, and on Solstice contractor escalations: evidence first, travel second.
Without Dataplicity
Tickets cite a serial. Logs live elsewhere. Remote access is a separate VPN or “ask the customer to open a port.” The evidence behind a dispatch decision is scattered across tools and conversations - so Harbor ships a tech for a playlist fault.
With Dataplicity
- Open the incident and confirm the affected devices plus available customer and site context (which Harbor store, which player class).
- Collect evidence first using scoped logs and a controlled remote check with Remote Shell or Wormhole before committing to travel.
- Record the decision on the incident: remote fix, dispatch, or wait-and-monitor, with the evidence behind it - including warranty context when replacement hardware is on the table.
- Publish only reviewed customer-facing facts on a status page when the brand partner needs an update. Keep internal diagnostics private. See Design the wallboard for who walks past it.
Outcome
Dispatch becomes a decision supported by evidence, not the default response.