Peak season or not, the pattern is the same: inbox volume tracks order volume, and both land on the same operator. Orders ship late, customers email, suppliers need chasing — all of it lands in the same inbox used to run the rest of the business. Hermes handles the message layer: drafting responses to order queries, queuing supplier follow-ups, flagging unresolved complaints — each draft surfaced for review before anything sends.
Ecommerce operators handle 30+ customer messages daily — and the number scales with orders, not team size
Gorgias's 2023 Ecommerce Customer Service Benchmark reports the average Shopify store handles over 1,000 customer support conversations per month — roughly 33 per day.[¹] For an operator responding personally, at 3–5 minutes per response, that is two to three hours of daily inbox work.
That number tracks order volume directly. A store growing from £300K to £600K annual revenue does not halve its message count — it doubles the delivery questions, tracking requests, return queries, and restocking chasers. The work scales with the orders.
Hiring a customer service assistant transfers the inbox load but adds coordination overhead: handoffs, context-sharing, approval loops before anything sends to a customer. The message volume problem becomes a management problem. Neither version scales cleanly past £1M annual revenue.
How Hermes handles customer order queries and follow-up
Hermes connects to the Shopify store and the operator's Gmail account. For an incoming order query — a delivery question, a return request, a product issue — Hermes reads the relevant order data from Shopify, drafts a response matching the store's policies and tone, and surfaces the draft for review.
The draft arrives in Slack or Gmail, depending on which channel the operator uses for approvals. The operator approves, edits, or dismisses. Nothing sends without a sign-off.
Hermes surfaces every customer response as a draft for approval before anything sends. Hermes does not auto-reply to customers. The operator reviews and approves each response — Hermes handles the assembly, not the decision.
For follow-up sequences — the customer who hasn't responded to a shipping update, the order that went out without a confirmation — Hermes queues the follow-up at the configured interval and surfaces it for review. The timing and template are set once; Hermes monitors and drafts against them.
How Hermes handles supplier and fulfilment follow-up
Supplier communication is less frequent than customer queries but higher-stakes. A restock confirmation missing for 48 hours has inventory implications. An order past its estimated ship date needs chasing before the customer notices.
Hermes watches for supplier communication gaps: messages awaiting a reply past a defined window, restock confirmations due but not received, fulfilment statuses that haven't updated in the expected timeframe. When a gap appears, Hermes drafts the follow-up and queues it for review.
The draft surfaces in Slack or Gmail with the relevant order or stock context attached — the operator reviews and approves in one read. Hermes does not require the operator to track which supplier needed chasing or when.
Order volume doubles. The time spent on customer messages doesn't have to.
How Skills build from ecommerce-specific patterns over time
Each completed task — an approved customer response, a sent supplier follow-up — adds a Skill object to Hermes's library. The Skill records the task type, the inputs, the approach used, and the outcome. On the next similar task, Hermes applies the Skill.
For an ecommerce operator, Skills build against the store's specific products, complaint patterns, and supplier relationships. In week one, Hermes handles return requests at a baseline level — structurally correct, needing edits for tone and product-specific detail. By month three, Skills built from 80–100 real completed responses reflect the store's actual return policy language, preferred tone for delivery complaints, and supplier communication style.
The draft quality in month three is not the same as week one. Hermes improves on what the operator actually sends — not on generic customer service templates.
What a Hermes ecommerce deployment covers on day one
A Hermes ecommerce deployment starts with three connections: the Shopify store (for order data and fulfilment status), the operator's Gmail account (for customer and supplier communication), and Slack (for the approval workflow). These are configured before the first workflow goes live.
On day one, Hermes handles configured workflows at a baseline level. A delivery query draft is structurally correct — it needs editing for tone and the operator's specific return window. A supplier follow-up is in the right format — it needs review before sending. The output is usable from day one. Skills start building from every completed task.
By month two, Hermes handles the store's most common query types without editing. By month three, edge cases — partial orders, international shipping queries, product-specific complaint patterns — are handled more precisely. The operator's role shifts from composing to reviewing.
For a full overview of Hermes and how it works, see what is Hermes. For how Skills build from completed tasks, see how Hermes learns. For running Hermes across multiple platforms from a single deployment, see the Hermes setup guide.
Frequently asked questions
How does Hermes help ecommerce operators manage customer messages? Hermes connects to Shopify and Gmail, reads order data for incoming queries, and drafts responses matching the store's policies and tone. Each draft surfaces for operator approval before sending. Skills build from every completed response, improving accuracy on the store's specific products, complaint types, and customer patterns over time.
Does Hermes send customer replies automatically? No. Every draft Hermes produces surfaces for human review before sending. The operator approves, edits, or dismisses each response. Nothing sends without a sign-off.
Can Hermes handle both customer communication and supplier follow-up? Yes. Hermes watches for customer order queries and supplier communication gaps simultaneously — drafting responses and follow-ups for each type. Both draft types surface for operator review before anything sends.
How long before Hermes improves on a store's specific communication patterns? Common query types — delivery questions, return requests, tracking updates — are typically handled accurately within the first two to four weeks. Edge cases specific to the store's product range and supplier relationships improve through months two and three as Skills accumulate from real completed tasks.
Notes
- Gorgias, Ecommerce Customer Service Benchmark Report, 2023. https://www.gorgias.com/blog/ecommerce-customer-service-benchmark