Open any ecommerce support inbox during a sale and count the messages. A big slice of them — usually the biggest single slice — say the same thing in a hundred different ways: "Where's my order?" "Did this ship?" "Tracking number?" "It's been five days." These are not hard questions. The answer already exists in your own database the instant the carrier scans the package. The only reason a human reads each one and copy-pastes a tracking number is that the question arrived as an email instead of an API call.
That part is fully automatable, and it's the cleanest agent task in all of ecommerce support, because the lookup is deterministic. You're not reasoning about a refund policy or a damaged item. You're matching a sender (or an order number) to a row, reading a tracking field, and replying. So this post wires up exactly that: an Agent Account that fields order-status email, looks the order up in your system, and replies in the same thread from your store's own address. Anything it can't match goes to a human — honestly and on purpose.
Most "AI email" demos point a model at a human's inbox and let it draft suggestions a person still has to approve. That's fine for an assistant. It's the wrong shape when you want the agent to be the participant — to receive mail at orders@yourstore.com, answer from that address, and keep the thread intact without a human in the loop for the routine 80%.
