track what it runs on
Everything about this customer, in one view.
Every job, asset, contract and conversation for a customer, for whoever picks up the phone.
what it does
What Customer 360 does
When a customer calls, the person answering should not have to open four systems to find out what has been happening.
One view gathers the sites, the assets, the open and historical work, the agreement they are on and what has been said to them.
It matters most where install, fault and upgrade work are handled by different teams, because that is where accounts usually fall between the gaps.
- Sites, assets and equipment per customer
- Open and historical work in one place
- The agreement and entitlement they are on
- Useful to whoever answers the phone
how it works
Four steps, and none of them are magic.
-
unify
One record per customer, however they arrived
Sites, contacts, assets, contracts, jobs, quotes and invoices against a single organisation instead of four systems that each know part of it.
-
attach
Every interaction lands on the record
Calls, appointments, visits, forms completed, parts fitted, what was signed and by whom.
-
structure
Hierarchy matches how the customer is organised
Parent company, regions, sites, buildings, assets, so a national account can be reported as one relationship and served as many locations.
-
surface
Whoever answers the phone has the history
The last three visits, what is outstanding, what they are entitled to, and what they were last unhappy about.
data and integration
What it reads, what it writes, what it sits beside.
Nothing here is a separate database. Customer 360 works off the same work order, customer and asset records as everything else, which is the whole reason the modules are worth running together.
reads
Every module: jobs, contracts, assets, quotes, invoices, appointments.
writes
Nothing new of its own. It is the view the rest of the platform composes into.
alongside
Your CRM, if sales is run elsewhere. Records can sync rather than be duplicated.
questions we actually get
Before you ask us on the call.
Merging is part of onboarding. Duplicates are matched and combined with history preserved, rather than one record being discarded.
Through a portal, scoped to what you choose to expose: typically jobs, appointments, documents and invoices.
Yes. Contract values and margin are permissioned separately from operational history, so technicians see what they need without seeing pricing.
For service it usually can. If your sales team lives in a CRM, keep it and sync: running two systems that both claim to own the customer is worse than either.
elsewhere in the platform