One customer, one record

Ask three people in a growing business for a customer's phone number and you may get three answers. Sales has it in their phone, support has it in an old ticket, accounts has the one on last year's invoice.

It sounds like a small thing. It is not. Every time a team works from its own copy of the customer, someone makes a promise the others do not know about.

What belongs on the record

A useful customer record is not a long form. It is the short list of things everyone needs:

• Who they are: name, the people you deal with, how to reach them and the language they prefer.
• Where you stand: open deals, quotes waiting for an answer, work in progress.
• What they owe and what you owe them.
• What happened last: the last conversation, the last ticket, the next action and who owns it.
• What they agreed to receive: which messages, on which channel.

Consent is part of the record

If you send campaigns, the record should say who agreed to what. An opt-out should always win, everywhere, immediately. That protects your customers — and your sender reputation.

How Kluvan keeps one record

In Kluvan, sales, service and accounts share the same customer. CRM holds the profile, tags, notes and the next action, and moves deals through your pipeline. A deal links to its quote in Books. A Desk ticket for the same customer can become a field job without retyping anything. Consent is kept per channel, and an opt-out always wins.

A "Linked" panel that shows everything connected to a record on one screen is coming soon. Business leads kept apart from customers — with their company and contacts — are coming soon too.

Start small

You do not need a perfect database to begin. Import the customers you have, merge the obvious duplicates, and agree one rule: if it is not on the record, it did not happen. The record gets better every week from there.