Customer data: decided before the first customer
If someone has sent you this: they’re considering something new, and they’d like to decide with you what happens to customers’ information before there are any customers. Tick what you’ve done, and talk about the rest.
Tick it on your own, or each of you separately and then compare.
What customers would give you
What you’ve decided
What customers are told
Why these points are important
Before there are customers, deciding what happens to their information takes an afternoon. Afterwards it means changing systems that are already in use, and telling people who trusted you with something.
What customers usually give without thinking
- Email threads with names and details of other people.
- Files with figures in them.
- Notes from calls.
- Complaints, which often say more than the customer intended.
- Payment details.
Each of these can end up in an AI tool through an ordinary piece of work, such as a summary or a reply.
Why the first tool tends to decide
Whatever tool is set up first tends to set the practice, because it’s already holding the information when anyone thinks to ask. Deciding before it’s set up means the tool follows the decision.
What I’d do first
I’d write down the most sensitive thing a customer would give you and follow it, step by step, through everywhere it would go. In my experience that one trace answers most of the other questions.
When you’re the one it’s been sent to
If you’d be setting up the systems, it helps to say where the information would actually go, including anything automatic. The person sending this may not know.
Where coaching fits
People at this point often use coaching to decide what they want to promise customers, and how much of that they’re prepared to keep to when it costs time. I won’t tell you what to decide, and I’m not a lawyer. I’ll ask the questions that show what you’d want a customer to be able to rely on.
If you’re considering something new, AI Checkpoint is a free reflection on what AI could change about it, and who’s checking: simonbowen.com/reflections/ai-checkpoint