Customer context
Customer context is the history you have in front of you when you reply: orders, earlier conversations, notes and campaign messages, all visible in one place.
When a customer writes "Where is my order?", the quality of your answer depends on what you can see. Customer context means everything you know about that person is within reach at the moment you reply. Recent orders, total order count, items waiting in the cart, conversations on other channels and team notes are all part of it.
Without context, every message starts from zero. The customer explains the same thing a second time, and you risk recommending the wrong product or reopening a problem that was already solved. A team that works with context knows half the answer before asking, and the customer feels recognised without any show of it.
Why It Matters
- Customers do not have to repeat themselves, which is the cheapest way to improve satisfaction.
- Replies are based on the person's real situation instead of a stock answer.
- When one team member takes over from another, the conversation does not get lost.
How It Works
- Data gathers on one personWhen a phone number, email or Instagram handle points to the same person, orders, messages and notes combine under that one record.
- The history is readThe person replying, or the AI, looks at the latest order, any return or cancellation, and an open cart.
- The reply fits the situationA customer from a campaign is answered with the campaign in mind, one from an ad with the ad in mind, and an earlier complaint shapes the tone.
- New details are written backAnything learned in the conversation is saved as a note, so the next person finds it ready.
Example
Elif Arslan writes to Liva Butik: "The shirt I bought last time doesn't fit." When Selin Kaya opens the message, she sees that Elif has five orders, that the latest includes the Linen shirt (₺1.490), and that Burak Demir noted two days ago that a size exchange is possible. Selin offers the exchange in her first sentence and does not ask for the order number again. Elif's problem is solved in one message, and she comes back to the same store for her next purchase.
Not to Be Confused With
Customer context is not the same as the fixed details in a profile, such as name and phone. The profile says who the person is; context says what is happening with them now. A timeline is context laid out in date order.
In Creato
In Creato, AI employees read the recorded customer history before they reply.
- Recent orders (including cancellations and returns), total order count and spend.
- The cart from the last 7 days, summaries of conversations on other channels, Instagram comments, sent campaign messages and tags also count as context; a conversation on Instagram is remembered on WhatsApp.
- A person coming from an ad is answered with the ad in mind, and one replying to a campaign with the campaign in mind.
- Order count and spend are calculated from the date the store was connected to Creato; past orders can be imported for up to 12 months, and no message goes to the customer during the import.
Frequently Asked Questions
Is customer context the same as a customer profile?
No, they are two separate things. The name and phone in a profile rarely change; context grows with every order, message and note. A profile can stay the same for years, while an open order or an unresolved complaint can change within a week. The moving part is what you read before replying; the profile only tells you who you are writing to.
Do I need to collect a lot of data for context?
No. What matters is showing the right data at the right moment. The latest order, any open problem and a note, if there is one, are enough for most messages. Keep the five or six facts your team actually looks at in the same place.
Can context get mixed up between two people?
If a phone number, email or Instagram handle matches, the records merge into one person. If no identifier matches, the profiles stay separate and the context looks incomplete. In doubtful cases, review the records by hand; this merging happens on the CRM side.