Use customer history for support and analysis
Customer history helps support, sales, and finance teams understand the full relationship with a buyer instead of reviewing each purchase in isolation.
What customer history helps answer
| Question | Where customer history helps |
|---|---|
| What did this buyer purchase? | Review purchases connected to the customer. |
| Is this buyer an active subscriber? | Review subscription status and lifecycle. |
| How valuable is this customer? | Compare lifetime spend and repeat purchases. |
| What payment methods were used? | Review buyer payment behavior when available. |
| Why is support asking about access? | Compare sale status, subscription status, and delivery context. |
Review a customer
- Confirm the correct business workspace.
- Open Customers or find the buyer from Sales.
- Search by name, email, or purchase context.
- Review purchases and subscriptions together.
- Check lifetime spend or buyer value when needed.
- Compare customer history with support messages.
- Export customer data when it is needed for CRM or lifecycle analysis.
Common support checks
- Buyer email matches the purchase.
- Sale status is approved before granting access.
- Subscription status matches the support request.
- Refund or chargeback history explains missing access.
- Product delivery method matches what the buyer expects.
- Customer record belongs to the selected business workspace.
Troubleshoot mismatched records
| Issue | What to check |
|---|---|
| Customer exists but sale is missing | Business workspace, date range, buyer email, and sale status. |
| Sale exists but subscription is missing | Payment model, plan type, subscription creation, and filters. |
| Subscription exists under another customer | Buyer email changes, duplicate records, or merge suggestions. |
| Export looks incomplete | Filters, archived records, selected date range, and product access. |
Best practices
- Use customer history before making refund or access decisions.
- Check subscriptions and purchases together for recurring products.
- Export only the filtered customer set you actually need.
- Avoid archiving customers until support and reporting needs are understood.
FAQ
Should support start from Sales or Customers?
Start from Sales when the question is about a specific purchase. Use Customers when the question involves the buyer's full history or multiple purchases.
Why can customer, sale, and subscription records look different?
They represent related but different parts of the buyer relationship. Filters, product access, payment model, duplicate records, or archived data can make them appear inconsistent.
When should I export customer data?
Export when accounting, CRM, lifecycle campaigns, or support analysis require work outside AtomicPay.