How to read a single customer record before you reply or sell
One person, their purchases, their lifetime value and their messages in one place. What each field is telling you, and the three decisions it should change.
A name comes up. Maybe it is in a message, maybe it is a refund request, maybe you are about to send an email to 300 people and this person's address catches your eye. Most creators react to the name itself — the vague sense of whether it rings a bell — and reply from there. There is a better option that takes ten seconds: open the record and read it properly.
Why memory is a bad customer database
You remember the loud ones. The person who left a long compliment, the person who asked for a refund in capital letters, the person who emailed four times about a file that would not open. What you do not remember is the quiet buyer who has bought every single thing you have released, never asked you for anything, and is currently reading a support reply that treats her like a stranger.
That is not a character flaw, it is arithmetic. Once you pass a hundred customers, nobody holds the shape of the list in their head. The customer list holds it instead, and it builds itself: every purchase, membership and free download attaches to a person, with what they spent in total sitting on the same row.
The hard part is that the record does not interpret itself. Two people can both show £80 of lifetime value and need completely opposite handling: one spent it in a single order last week, the other in four small orders over two years. Reading well means noticing which of those you are looking at.
Guessing from memory, or reading the record
The default is to answer from vibes. It works often enough that the failures are invisible: you never find out that the person you brushed off was your third-best customer, because they simply stop buying and you assume the market cooled.
| Guessing from memory | Reading the record first |
|---|---|
| Loud customers get the attention | Frequent customers get the attention |
| "Have they bought before?" is a guess | Purchase history and count are on the row |
| Every reply starts from zero context | You can name the product they own before they explain it |
| Upsells go to everyone equally | Offers go to people who already own the prerequisite |
| Refunds feel like an argument | Refunds are a five-second decision based on what they have spent |
| Free downloaders are invisible | Free downloaders sit in the same list with a clear next step |
The six fields, in the order you should read them
Open Customers in your dashboard and search the email address or name — this is on every plan, including Free, as the pricing page sets out. The record opens with everything attached to that person. Read it in this order, because each field changes how you read the next one.
- 1Purchase count. One is a trial, two is a relationship, four is a fan. This single number sets the tone of everything you are about to write.
- 2What they bought. The specific products tell you what they already own, which is the difference between a helpful recommendation and an insulting one.
- 3Lifetime value. Read it alongside the count: one big order and four small ones mean different things at the same total.
- 4First seen. How long they have been around. Someone from your first month has watched you get better and will forgive more than someone who arrived yesterday.
- 5Most recent activity. The gap between this and today is your real churn signal. Six months of silence from a former repeat buyer is worth a personal note.
- 6Messages and order notes. Anything they told you at checkout through an order-form question, and anything they have written to you since, sits with the record rather than in a separate inbox.
The three decisions it should change
- How you reply: a fourth-time buyer gets "of course, sorted" rather than a policy paragraph.
- What you offer next: never pitch the thing they already own, and never pitch the advanced thing to someone who bought the beginner one yesterday.
- Whether they go in the next broadcast: a contact who took a free download eight months ago and never opened anything since is a candidate for a re-permission note, not a launch email.
The same question, two people
Two messages arrive on the same morning, both saying roughly "is the course going to be updated?". The first is from someone whose record shows one purchase, a $9 template, bought yesterday, no previous history. The second shows four purchases over fourteen months, a total around £220, including the course itself and a membership that renewed twice.
The first person is asking whether you are trustworthy before they spend more. The honest answer is a short one about what you plan to release, with a link to the thing that follows on from the template they bought. The second person is asking about something she already owns and has been paying into. She gets a straight date, or a straight "not before autumn", and she gets it first. Same question, two different replies, and the only thing that produced the difference was ten seconds of reading.
The customer list, lifetime value and CSV export all sit on the free plan, so you can see this working before you spend anything.
Start for freeThe mistake most people make
The mistake is reading the record after the decision instead of before it. You send the refund, or the pitch, or the slightly short reply, and then you look someone up and feel the small drop in your stomach. The habit that fixes it is mechanical: before any reply that involves money, and before any message that goes to more than ten people, open the list. It costs less time than rereading your own draft, and it stops the two errors that actually cost you customers — treating a regular like a stranger, and selling someone something they already own.
Treat any lifetime value figure as a summary rather than an accounting document. When the number matters for tax or reconciliation, use your Stripe dashboard, which holds the authoritative record of what actually settled.
Yes. A $0 lead magnet creates a customer record just as a paid order does, so you can see that someone took three free things and never bought — which is useful information rather than clutter.
The purchase history is ordered, so the first row is the product that started the relationship. That is often a more interesting number across your whole list than your bestseller, and per-product analytics shows the same thing from the other direction.
Then they are a browser, not a customer, and you are answering a pre-sales question. Say what the product does and does not include, and resist inventing an exception for someone who has not bought yet.
None of this is customer relationship management in the corporate sense. It is closer to remembering people properly at scale, which is what you were doing naturally when you had eleven customers. The record just keeps doing it after you have eleven hundred. If you want to see the shape of the whole thing first, the features overview lays out what attaches to a customer and where.
Set up a storefront and let the customer list build itself from the first sale onwards.
Get your linkTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.
