An online shop's support inbox is really two inboxes wearing the same chat bubble. One is the shopper who has not bought yet and is deciding whether to. The other is the customer who already paid and now needs something to go right. They arrive through the same widget, and the cheapest mistake you can make is answering both with the same agent behavior.
I build AI support agents for e-commerce, and separating these two has done more for results than any model upgrade. Here is how we think about the split and how it shows up in the code.
Different goal, different cost of being wrong
A pre-sale question is a conversion event in disguise. "Does this fit a 12-month-old?", "Will it ship before Friday?", "Can I return it if the color is off?" The shopper is holding their card. A fast, correct, confident answer removes the last reason not to buy. A slow or hedged answer loses the sale, and you never even see it in a ticket count.
A post-sale question is a retention event. "Where is my order?", "I need to send this back." The money is already collected. Now the only variable is whether this person comes back or tells a few friends not to. The cost of a wrong answer is different on each side: pre-sale a bad answer costs one conversion, post-sale a bad answer costs a customer and their word of mouth.
