Decide dispatch vs remote fix on a field support call

A customer reports field impact. 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.

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.

With Dataplicity

1. Open the incident and confirm the affected devices plus available customer and site context.
2. Collect evidence first using scoped logs and a controlled remote check with Remote Shell or Wormhole before committing to travel.
3. Record the decision on the incident: remote fix, dispatch, or wait-and-monitor, with the evidence behind it.
4. Publish only reviewed customer-facing facts on a status page when customers need 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.

Next

• From signal to verified recovery
• Customer surfaces
• Map devices to customers
• Remote access
• Customer status visibility

Related path: Connected product company