Guide16 min read
Ecommerce Customer Support Workflows: A Shopify Guide
An ecommerce customer support workflow is the written path a customer message takes from arrival to a closed ticket: who sees it, how it is tagged, what a rule answers, what goes to a person and what gets measured. Count your repeat tickets by cause in one export and fix the biggest causes before you buy software.
Key takeaways
- A support workflow is a written path with five stages: intake, routing, answer, escalation and measurement.
- Count tickets by cause for 30 days before you buy or build anything, because no verified share exists for how many tickets are order status questions.
- Fix causes at the source with the order status page, shipping notifications, self-serve returns and clear policy pages.
- Route with one tag per cause and one named owner, and keep refunds, damaged goods and chargebacks with a person.
- Track first reply time, resolution time, tickets per 100 orders, repeat contact and CSAT against your own 30-day baseline.
What is an ecommerce customer support workflow?
It is a repeatable path for every customer message, written down so the same question gets the same handling on every shift. Shopify defines a customer service workflow as "a series of steps for handling important customer service tasks, including managing and tracking customer interactions." The same page lists the key parts of a workflow diagram as triggers, action steps, decision points and stakeholders. We split that path into five stages. The split is ours, not Shopify's. For the vocabulary, see the ecommerce operations glossary, and for how written procedures become automated ones, what agentic operations are.
| Stage | What happens | Where it lives in a Shopify stack |
|---|---|---|
| Intake | Email, chat, social and phone messages arrive in one queue | A helpdesk for the shared queue, Shopify Inbox for chat on the store |
| Triage and routing | Each ticket gets a tag, a priority and an owner | Helpdesk rules or triggers |
| Answer | A rule, a macro, an AI draft or a person replies | Helpdesk macros, the Inbox agent, drafts for a person to send |
| Escalation | Refunds, damaged goods and chargebacks go to a named role | A tag, a queue and a written owner |
| Measure | First reply time, resolution time, tickets per 100 orders | A helpdesk export plus your order count |
Source: the five stages are Morsegrid's own. The definition and workflow parts are from Shopify, Customer Service Workflows: Types and Tips (2026).
Why do the same tickets keep coming back?
They come back because a few causes feed most of the volume and nothing fixes the cause. A reply closes one ticket, and the next customer with the same problem opens another. Count tickets by cause before you change a rule or buy a tool.
Shopify's guide offers the pattern as an example, not a statistic: you might find that "the majority of customer service inquiries are WISMO ("Where is my order?") questions," and that your team spends too much time sending order status updates by hand.
Count your tickets by cause
Export the last 30 days of tickets. Give each ticket one tag for its main cause: order status, return, address change, product question, discount, damaged item or other. Count tickets per tag.
Then work out tickets per 100 orders: tickets divided by orders in the same 30 days, times 100. That definition is ours, and it lets you compare months even when sales swing.
Do not borrow a share from the internet. The figure that circulates for how many ecommerce tickets are "where is my order" questions is about 40%, and Macha, which traced it to a Narvar blog post quoting Forrester, says it covers peak season only and to "treat 40% as unverified." So we use none, and you should use your own count.
Look for tickets nobody is waiting on
Some tickets are not customers at all. In one client account, 48% of a month's tickets (1,046 of 2,185) were the store's own order-confirmation robot writing to its own helpdesk, as we describe in why order confirmation emails show up as helpdesk tickets. That is one client in one month, so treat it as a reason to count your own tickets and fix the sender, not the queue.
Look for demand the helpdesk never sees
A helpdesk only counts what it receives. At one retailer, 3,067 inbound calls came in over 30 days and 155 were answered live, which is 94.9% missed, as we report in missed ecommerce calls your helpdesk may never show you. Again, one client and one month.
How do you cut repeat tickets at the source?
Put the answer where the customer already is, then send the update before they ask. Each fix below removes a cause rather than answering it faster. Use the table as a checklist for the top two causes your count turns up.
| Ticket cause | The fix at the source | Where to set it up |
|---|---|---|
| Where is my order | Let customers check the shipment themselves and send status emails automatically | Order status page and customer notifications. Read the WISMO guide. |
| Return, exchange or cancel before shipping | Let customers start a return, or cancel items that have not shipped, from the order status page and inside your rules | Self-serve returns and cancellations. Read how to reduce ecommerce returns. |
| Product question | Answer it on the product page: specs, sizing and care | Your product pages |
| Policy question | Publish the policy once and let the Inbox agent read it | Store policies, used by the Inbox agent |
| Stock promise that cannot be kept | Do not show or promise stock the system cannot back | Your inventory source. Read phantom stock and open purchase orders. |
Source: Shopify Help Center pages linked in the table. The pairing is Morsegrid's own.
Send the update before the question
Shopify sends an order confirmation, a shipping confirmation, an out-for-delivery message and a delivered message. Once you add tracking numbers, customers can check the status of their shipment without contacting you, with real-time location updates on a supported carrier. Add tracking to every order, because the page only helps when it has something to show.
The gap left over is the order that never gets tracking. Shopify Flow is a free app that runs automated workflows in your admin from triggers, conditions and actions. One merchant in a Shopify Community thread described using Flow to tag orders with no tracking after X days, delayed fulfillment or a refund created, so the helpdesk can prioritize those tickets. That is one merchant's setup, not a benchmark. For what to build in Flow and what outside it, read Shopify Flow, n8n or Make.
Write the policy before you switch the feature on
Self-serve returns work with your return and cancellation rules to control which items are eligible, how long customers have to make a request, and whether return shipping is free or paid by the customer. You can approve or decline each request under your policies, so decide eligibility, the time limit and who pays for shipping first, then turn it on.
How should tickets be routed?
Use one queue, one tag per cause and one named owner per category. Shopify describes a ticket routing system as one that sends each ticket to the available representative best equipped to handle it. That only works when the categories are written down.
| Category | Tag | First owner | Rule or macro | Escalate when |
|---|---|---|---|---|
| Where is my order | order-status | Support agent | Status macro with the tracking link | No tracking after your set number of days |
| Return or exchange | return | Support agent | Return instructions macro | Outside the window, or a high-value order |
| Address change or cancel | address-cancel | Support agent | Cancel-before-shipping macro | The order has already shipped |
| Damaged or wrong item | damaged | Support lead | Photo request macro, no auto-reply | Always |
| Refund exception or chargeback | refund-exception | Finance or support lead | None, a person replies | Always |
| Product or stock question | product-question | Support agent | Answer macro from the product page | It needs stock data you cannot see |
A template. The columns and rows are Morsegrid's own suggestion, so change them to fit your store.
One inbox for every channel
Bring email, chat, social and phone messages into one helpdesk view, so no channel keeps a private backlog. Shopify Inbox is a free app for customer messages, and it can send automated replies to common questions such as order status. That covers chat on your store. A helpdesk covers the rest.
Tags and rules
Gorgias recommends you first set up rules that auto-tag, auto-close and auto-reply. Its rules trigger in order from first to last, and it recommends a clear naming convention, such as a prefix for auto-close and auto-reply rules. Zendesk describes triggers as business rules that run right after a ticket is created or updated and perform actions when your conditions are met.
Keep the tag list short, one tag per cause, or the counts in your weekly review will not add up.
Name the categories a person always owns
Write down the cases a person always handles, so no rule or draft answers them. Our recommendation is refund exceptions, damaged or safety cases, chargebacks and your highest-value customers, each with a named owner.
If your own emails are creating tickets, stop them at the sender, as the order confirmation emails guide explains, not with a rule.
What should macros and AI drafts do, and what stays with a person?
Macros and rules answer questions that have one right answer. Drafts speed up the rest. A person sends anything that involves money or risk.
Macros for the questions you answer every day
Gorgias says macros let agents respond to customers and take actions on tickets in a single click, with standardized responses placed into the composer. Zendesk says you can use macros to update tickets with preset actions, such as changing the status, priority, group or assignee, adding comments, and setting, adding or removing tags.
Build your first macros from your top five tags, one per cause, and review them every quarter so stale return windows and old links do not linger. The quarterly review is our habit, not a vendor rule.
AI answers and drafts
Shopify's Inbox agent can answer questions about your products, shipping, returns, sizing and store policies, using your catalog, policies and published storefront content. You choose which conversations it handles. Start with one category, such as order status, and keep the rest with people.
A merchant in the same Community thread described a setup that pulls up the order, drafts a reply and routes it to the right person with full context, but "a human hits send." That is one merchant's view, and it matches how we build. Our Email work drafts replies with the full thread behind them for a person to review and send, not auto-replies. Our Chat work answers from content you have approved and hands anything else to a person with the conversation attached.
Billing differs by tool, so read the unit before you turn anything on.
| Tool | What it does for the workflow | Billing unit, from the vendor's docs |
|---|---|---|
| Shopify Inbox | Chat on your store, automated replies for common questions, and the Inbox agent | Inbox is a free app. Check current terms for the Inbox agent |
| Gorgias | Shared helpdesk with rules, macros and Shopify actions | A fee based on the number of tickets you use, not the size of your team. A reply sent by a rule counts as a billable ticket |
| Zendesk | Helpdesk with triggers, macros and an AI agent | AI agent usage is billed per automated resolution: a request an AI agent resolved without any escalation to a human |
Source: vendor documentation linked in the table. No prices are quoted here, because plans change.
Can a Shopify consultant work with your ERP and help desk?
Yes. The work is to map which system owns which fact, then wire the helpdesk so the agent sees it. In many stores that data lives in Shopify, an ERP or inventory system, and the helpdesk. Deep admin work inside an ERP or helpdesk can stay with a specialist, and the consultant owns the map between them.
What the helpdesk needs from the store
Gorgias says that by integrating Shopify you can perform Shopify actions from Gorgias, such as refund, duplicate, create and cancel an order. The same page lists limits to know before you promise a customer anything: Edit order is not available for archived orders, orders placed more than 60 days ago or orders in a different currency than your store's, and you can only refund orders that come from one payment gateway.
What the helpdesk needs from stock and the ERP
Customers ask "is it in stock" and "when will it ship." The answer has to come from the system that owns stock, not from a macro. If stock counts drift, replies drift with them, which is the problem phantom stock and open purchase orders describes.
We read your Shopify, helpdesk and ERP data before we propose anything, and our Gorgias integration connects tickets to the Shopify and Airtable records behind them.
Who owns each fact in the ticket
Fill this in for your own stack before any build. "To confirm" means the answer depends on your tools.
| What the agent needs | System of record | How it reaches the ticket |
|---|---|---|
| Order status | Shopify | Helpdesk store integration, to confirm in your stack |
| Tracking | Shopify or the carrier | Tracking link in the order, to confirm in your stack |
| Refund state | Shopify and the payment gateway | Shopify actions in the helpdesk, within the limits above |
| Stock and ship date | Inventory system or ERP | To confirm in your stack, often the weakest link |
| B2B price or account terms | ERP or Shopify, depending on your setup | To confirm in your stack |
| Past tickets | Helpdesk | The customer view in the helpdesk, to confirm in your stack |
A template. The system of record column is a starting point to confirm, not a claim about your stack.
How do you measure reply time and whether the workflow works?
Pick five numbers, take a 30-day baseline from your helpdesk export and change one thing at a time. A number only means something against your own past month.
| Metric | How to count it | What it tells you |
|---|---|---|
| First reply time | Ticket created to the first reply a customer can see | How long customers wait to hear anything |
| Resolution time | Average time from initial ticket creation through final resolution | Whether tickets close, not just get answered |
| Tickets per 100 orders | Tickets divided by orders in the same period, times 100 | Whether source fixes are working |
| Repeat contact | Same customer and same cause within 14 days (our definition) | Whether the first answer solved it |
| CSAT and cost per resolution | A score from one to 100 for one interaction, and the average cost of each resolved ticket | Quality and cost, read together |
Source: definitions of resolution time, CSAT and cost per resolution are Shopify's. First reply time, tickets per 100 orders and repeat contact are Morsegrid's own definitions. If you use Zendesk's AI agent, add automated resolutions, the unit Zendesk bills for.
Do not use a borrowed target
We found no neutral source for reply-time targets, so we quote none. Set your own once you have a baseline.
Count the phone line too
If your store takes calls, add them to the same sheet. Our Voice work answers after-hours calls from confirmed facts and lists a callback when unsure. At one client the voice agent now answers 69.5% of closed-hours calls, according to our missed calls guide. That figure covers closed hours only, so it is not a before and after of the 94.9% missed-call rate above.
What is a 30-day order of work?
Count first, fix the top two causes at the source, route, then add AI drafts for one category with a person sending. Each week gives the next something to measure.
- Week 1, count and tag. Export 30 days of tickets, tag each by cause and work out tickets per 100 orders. That is your baseline.
- Week 2, fix the top two causes at the source. Turn on the order status page, check notifications, and set up self-serve returns once the policy is written.
- Week 3, route. Fill in the routing sheet, set up the rules, name the owners and write your five macros.
- Week 4, add drafts for one category. Let AI draft replies for one cause, a person sends each, then compare every number with week 1.
Start where the time goes
Intercom, a helpdesk vendor, describes what it says leading brands do: rather than automate everything at once, they pick the three to five query types that consume the most agent time, like WISMO, returns and refund processing, and build those workflows first. That is a vendor's claim, but it matches the order above. Write each step down with the SOP template.
How do you choose a consultant for support workflows?
Choose by your bottleneck, then ask for the method, not the logo wall. In our reading there are two kinds of partner. Helpdesk and customer experience specialists work on rules, macros and staffing. Shopify integrators wire the store, the ERP, and subscription and returns apps into the ticket. Many stores need both, and a good partner says which one comes first. The split is our reading, so test it against your own problem.
| Question | What a good answer includes |
|---|---|
| How do you size the problem first? | A ticket count by cause from your own export, before any proposal |
| Which of our systems will you read? | The store, the helpdesk, the ERP or inventory system and the phone line, named |
| What changes in our helpdesk, and who maintains it after launch? | A list of rules, macros and tags, and a named owner on your side |
| What stays with a person? | Refunds, damaged goods and chargebacks, written down |
| How will we know it worked? | A 30-day baseline and a compare date |
| What do you not do? | A plain answer, with the work you would hand to a specialist |
A checklist. The questions are Morsegrid's own.
How we work
We diagnose first, from your own store, helpdesk and ERP data. Then we build inside the tools you already use, write it down and train your team. You work with the people building the systems, with no account manager in between.
Our ecommerce page shows where we usually start. For the tools behind it, see Insights and Reporting for conversation themes, Suggestions for knowledge gaps found in real conversations, and Watchtower for checks on every conversation, not a sample. For choosing a partner in general, read how to choose an ecommerce operations partner.
Frequently asked questions
- What is a customer support workflow for an ecommerce store?
- It is the written path a customer message takes from arrival to a closed ticket. Shopify defines a customer service workflow as a series of steps for handling important tasks, including managing and tracking customer interactions. We describe five stages: intake, routing, answer, escalation and measurement.
- Can AI answer support tickets without a person?
- For some questions, yes. Shopify's Inbox agent answers from your catalog, store policies and published storefront content, and you choose which conversations it handles. Some vendors bill per automated resolution, a request resolved with no escalation to a human. We keep refunds, damaged goods and chargebacks with a person.
- Do I need a helpdesk, or is Shopify Inbox enough?
- Shopify says Inbox is a free app for customer messages, including automated replies. A helpdesk adds one queue across channels, tags, rules and macros. Choose one when you need that shared queue and order actions in the ticket, such as Gorgias's refund and cancel actions.
- How many tickets per 100 orders is normal?
- We use no benchmark, because we found none we can source. Measure your own 30-day baseline. The circulating figure of about 40% for order status tickets is unsourced: Macha, which traced it to a Narvar blog post, says to treat it as unverified.
- Can a Shopify consultant work with my ERP and help desk?
- Yes. The work is to map which system owns each fact, connect the helpdesk so agents see it and name an owner for each. Deep ERP or helpdesk administration may stay with a specialist, and the helpdesk has limits: for example, Gorgias's Edit order action is not available for orders placed more than 60 days ago.
Start with a 30-day export and one tag per ticket. To have the problem sized from your own store, helpdesk and ERP data, see our ecommerce page.
Keep reading
Guide
Where Is My Order (WISMO): Cut Tickets With Updates
Cut WISMO tickets by finding stalled parcels first, sending the right update per delivery state, and wiring live tracking into your helpdesk auto-replies.
8 min read
Guide
Ecommerce Reporting: One Set of Numbers for Your Store
Ecommerce reporting that matches across Shopify, ad platforms and accounting: which reports to run, how to get profit per order, and how to pick tools.
16 min read