Does it connect to Shopify or my store platform?

Not directly — there is no store integration, and the pages that promise you one are usually overselling. What works today: the agent answers everything your written policy covers, and for live order data your own system drives the reply through the API or the MCP server.

What about angry customers?

They go to a person, every time. That is a rule worth hard-coding: a slow correct answer costs you minutes, a fast wrong one can cost you the customer.

Does it hold up during a sales spike?

Volume is the case it was built for. The thing to watch in a spike is not throughput but your snippets — if your dispatch times have changed for Black Friday and the snippet has not, the agent will confidently tell everyone the wrong thing.

Can it handle returns and cancellations, not just tracking?

Yes, as separate branches. Returns get your policy and the next step, cancellations and address changes route by your rules, and any of those replies can sit behind approval.

What if the customer never mentions their order number?

The workflow tries to find one in the message. If it cannot, the thread falls to the catch-all branch and a person picks it up, so the customer still gets an answer instead of a form letter.

← All use cases

orders@support@

E-commerce order email automation

"Where is my order?" is most of what an online shop receives, and answering it is neither difficult nor interesting. An agent on orders@ takes that volume, starts returns by your policy, and pushes the genuine exceptions at a person.

What it looks like today

Copy-pasting the same dispatch-times paragraph forty times a day.
Peak season, where the volume triples and the team does not.
The one email in a hundred that is actually a problem, buried in ninety-nine that are not.

How the orders@ workflow runs

1
A customer writes to orders@
Delivery questions, returns, cancellations, address changes, and a fair amount of noise.
2
It gets classified, and the order number gets pulled out
Most people include it somewhere. When nobody can find one, that is its own branch — a person answers rather than the customer being asked to try again.
3
The documented answers go out
Dispatch times, where tracking shows up and when, what happens if a parcel is late, how a return starts. All of it from what you wrote, none of it invented.
4
Exceptions go to your team
Damage, a wrong item, anything with real money attached, and anyone who is clearly upset. These arrive summarised, not answered.

What changes

The delivery questions stop consuming the morning.
A sales spike raises the volume the agent handles, not the volume your team reads.
The email that is genuinely a problem is visible instead of buried.

Where you stay in charge

The agent absorbs volume. Anything that costs money or needs a judgement call goes to your team.

Refunds and goodwill gestures are people decisions. The agent can explain the policy; it does not apply it.
Frustration is an escalation trigger in its own right. A technically correct reply to an angry customer reads as an insult.
When the order cannot be identified, a person answers. Nobody gets told to write in again with more detail.

One morning, concretely

Three delivery questions arrive over lunch. All three come back with what your policy says about dispatch and tracking. The fourth email, about a parcel that arrived smashed, is sitting with a person and has not been answered by anything.

Questions people ask

Does it connect to Shopify or my store platform?: Not directly — there is no store integration, and the pages that promise you one are usually overselling. What works today: the agent answers everything your written policy covers, and for live order data your own system drives the reply through the API or the MCP server.
What about angry customers?: They go to a person, every time. That is a rule worth hard-coding: a slow correct answer costs you minutes, a fast wrong one can cost you the customer.
Does it hold up during a sales spike?: Volume is the case it was built for. The thing to watch in a spike is not throughput but your snippets — if your dispatch times have changed for Black Friday and the snippet has not, the agent will confidently tell everyone the wrong thing.
Can it handle returns and cancellations, not just tracking?: Yes, as separate branches. Returns get your policy and the next step, cancellations and address changes route by your rules, and any of those replies can sit behind approval.
What if the customer never mentions their order number?: The workflow tries to find one in the message. If it cannot, the thread falls to the catch-all branch and a person picks it up, so the customer still gets an answer instead of a form letter.