Every time you have to type the customer name or number or address, it creates a new record. It creates another version of the truth, it creates conflict. This conflict is a A few years ago, two Telecoms operators merged. One had 5m subscribers and the other had 7m subscribers. Together, you would think they had something like 12m subscribers…. But no. After duplications and false entries were removed the total was less than 9m subscribers. Each company had, for years, run several systems, each with their own view of the customer. In some circumstances only a capital letter or comma caused duplication and multiple versions of “the truth”. At the time, sorting this out was nothing less than mayhem. If it can happen to them, then it can happen to your business.security hazard
to a business. How many versions of the truth, for each piece of information, will be created in multiple applications across multiple devices. This mayhem can eat your day.
Zway says “Get a life”
Zway offers “Contact Lifecycle Management” A contact (during its lifecycle) changes status several times. For example:
· Joe Bloggs (contact) is stored in your central contacts repository.
· Joe Bloggs offers his email address. You store that with his contact creating a unique record.
· Joe agrees to go onto your sales email list.
· Joe Bloggs buys your products and becomes a customer. He now has a delivery and billing address linked to his record.
· Joe decides to apply for a job at your business
· Now you hold private information about him, that is stored appropriately and is hidden to everyone apart from your HR Manager.
· Joe Bloggs becomes an employee. He gets a company email address and is now seen in your HR register along with his new position, salary and reporting line.
· At all times, Joe Bloggs is a contact, but has changed status and even has multiple statuses during his lifetime.
· At present, even big companies cannot handle this flexibility properly. It becomes a GDPR nightmare.
· With Zway, the system does the hard work for you whilst maintaining integrity.
· Joe Bloggs logs onto your system as a self-service user to change any of his data and sees all relevant information you hold about him. This access exceeds GDPR regulations and empowers contacts to see and edit personal information (if permitted).
· When Joe leaves your employ, he is still a contact of your company. His private employment details are linked but kept secure, even after he loses his company email address. His purchase history is linked to his unique record and Joe continues his lifecycle with your business. Joe is one person with three profiles.
