Features / Customer records that get smarter after checkout
Customer records that get smarter after checkout
Most customer databases stop learning at the transaction. This one keeps going. After a customer claims their first plant, their record fills in with what they own from you, how they are caring for it, and every support and warranty interaction, in one view.
What a customer record contains
Open a customer and you see their email and name, the date they first connected to your nursery, and their status. Below that:
- Plants claimed from you: each one with its species, the date it was claimed, its watering schedule, and a short care summary drawn from the plant's activity.
- Support threads: every conversation the customer has opened on a plant they bought from you, with message counts and the last activity date.
- Warranty claims: what was filed, on which plant, the review state it came back with, and how staff resolved it.
- Last activity: the most recent thing that happened across care events, support, and claims, so a stale record is easy to spot.
Search that matches how staff think
A customer phones about "the maple I bought in spring". Staff rarely have the order number. Search matches on the customer's email or name, and also on the species of any plant they have claimed, so typing "japanese maple" surfaces every customer who owns one from you. From there, one click opens the full record.
How the record is built
A persistent link between a customer and your nursery is created the first time they claim a plant from you, and it is not duplicated on later purchases. The "first connected" date is the first claim and stays fixed. Everything else on the record is assembled at read time from the plants, support threads, and claims that point at your nursery, so it is always current and there is nothing to sync.
Read-only, on purpose, for now
In this version the customer record is a view, not an editor. There is no merging of records, no manual customer creation, and no free-text CRM notes at the customer level. It exists to answer "who is this person, what did they buy, and what has happened since". Notes live where the work happens: on a support thread or a warranty claim.
What it is groundwork for
A record that knows what a customer owns and how they are caring for it is the foundation for staying useful to them over time. Features that build on it, such as signals about when a customer might be ready to reorder or a way for a nursery to send plant-specific updates, are not in the product today and are not sold here. When they exist, they will build on this record rather than a separate contact list.
Plan limits
The customer list and search are on every plan. The full per-customer detail view, with the plants, support history, and claims expanded, is a Starter and Growth feature. On Basic, opening a customer's detail returns an upgrade prompt.