Appearance
Customer ownership
What is this?
Customer and site modules provide dedicated records for customer organisations, contacts, locations, device relationships, and supported SLA workflows. Tags are useful selectors, but they are not the system of record for ownership or location.
Why does it matter after devices ship?
When a support ticket says "the device at the Manchester warehouse is offline," you need to find that specific unit among hundreds. Without customer and site context on the device record, every incident starts with "which device is it?"
How does it work in Dataplicity?
Create the customer, add contacts and sites, then associate devices through the supported customer and site fields. Use networks and tags for operational cohorts such as environment, rollout wave, or firmware.
When should I use it?
- Devices are deployed to customer-owned networks
- Multiple customers each have their own device fleet
- Support teams need to filter by customer or location
- Customer support, licensing, warranty, or SLA work needs shared context
Example workflow
An operator creates Acme Corp, adds its Manchester site and support contacts, then assigns deployed devices. Support opens the customer record to reach the relevant inventory, service context, and available warranty or licensing records.