15 parts · 6 checkpoints
Show all 15 parts
- 01Give the buyer a person and a next update
- 02Set contact details, timing, and routes
- 03Use product identity to find the cause
- 04Keep empathy and facts in the same record, has a checkpoint
- 05Turn the message into a useful first reply, has a checkpoint
- 06Six scripts connect the reply to internal action
- 07Connect replies to the six post-purchase stages
- 08Read the first week through buyer questions
- 09Record distinct return, refund, and reship outcomes
- 10Resolve the case before planning follow-up
- 11Use metrics to decide what to fix
- 12Verify the actual tools and human handoff
- 13Work through one complete practice case
- 14Keep the current choices and team setup
- 15Work it out: what full refunds would cost on four tickets
Give the buyer a person and a next update
“My parcel has not arrived” can be a tracking question or a sign that the buyer is losing trust in the store. Understand the concern, verify the facts, assign a person, give the next update time, and state when the case escalates. Every reply should leave a next step another person can continue. A small store can start with an inbox and a simple table. Make the contact details, timing, and record location clear.
The classroom case uses a 20oz tumbler in black and white. An out-of-stock black variant still advertised as available, a white item sent for a black order, damage, and delay point to different failures: stock sync, SKU mapping, packaging, or delivery promises. A separate 30oz barcode example tests product identity. These are teaching cases, not observed complaints or completed refunds. To start here independently, prepare a fictional buyer message, known and unknown facts, the relevant policy version, and an assigned reviewer.
If you completed launch QA, bring the named buyer path, evidence location, Go / Soft launch / Hold / No-go decision, pause action, and retest. Otherwise, name a support gap to investigate. A QA board locates a tested blockage; human response, refund receipt, carrier performance, and customer experience need separate evidence. This lesson leaves a support SLA and routing table covering response timing, evidence, escalation, updates to pages, and automation state.
Set contact details, timing, and routes
Before launch, prepare a working inbox or helpdesk, store and product FAQs, contact instructions in order and shipping messages, an internal refund/reship process, working hours, and an expected human response time. Define time zone, weekends, holidays, cover, and escalation ownership. An automated acknowledgment, the first human reply, and resolution are separate events. The aim is to answer purchase questions, reduce repeated disputes, build reusable help, and support repeat purchase. Use the records to assess those results.
Start the FAQ with four groups of buyer questions: size, material, use, suitability, and delivery coverage before purchase; handling time, delivery windows, tracking, and duties around shipment; return windows, conditions, and request steps; and lost parcels, damage, wrong items, address errors, and contact details after purchase. Before orders arrive, begin with questions you would ask as a buyer. Replace assumptions with recurring questions from actual contacts as they arrive. FAQs, product pages, emails, and policies should give consistent answers.
A workable classroom starting point is a first reply within 24 hours on a business day, refund review progress or a decision within 1 business day after necessary evidence arrives, and a damage/wrong-item plan or escalation within 48 hours. Review chargeback risk and public complaints the same day. These are staffing examples, not Shopify defaults, legal deadlines, or guaranteed refund receipt. Set actual promises against team capacity, market obligations, risk, and the payment path.
When should I hand this ticket to a person?

As text: the whole walk-through
- Front line An automatic acknowledgment goes out, so the buyer sees “received”, but no person has replied.
- On-duty lead The front line’s time limit passes with no next step, so the ticket climbs one level to the on-duty lead.
- On-duty lead A person sends the first human reply, and the ticket records it.
- Human review The buyer mentions a bank, PayPal, a complaint platform or a public review: no waiting for the clock, it goes to human review the same day.
- Human review An escalation leaves three things: the reason, the reviewer and the latest handling time.
- Review concluded With the three records in place, human review gives its conclusion and the next teammate can pick it up.
Illustrative: two ways one ticket escalates. Hours are classroom examples, not Shopify defaults or legal deadlines, so none are drawn.
From first response to learning
- What this stage promises
- Tell the customer someone has picked it up and give the next timing expectation.
- Evidence to keep
- Auto reply, first human response time, support entry, and working hours.
- What this stage promises
- Collect order, photos, tracking, policy clause, and customer description.
- Evidence to keep
- Ticket record, order number, screenshots, carrier scan, and handling note.
- What this stage promises
- Define refund, reship, partial compensation, return, or no-refund boundary.
- Evidence to keep
- Resolution plan, amount, timing, assigned teammate, and customer confirmation.
- What this stage promises
- Chargeback risk, sentiment escalation, batch quality issue, or high-value order must escalate.
- Evidence to keep
- Escalation reason, reviewer, deadline, and dispute evidence packet.
- What this stage promises
- Frequent issues flow back to FAQ, product page, shipping promise, policies, and retention touchpoints.
- Evidence to keep
- Weekly review table, page change, FAQ update, and template version.
Read the five stages from response through investigation, resolution, escalation, and learning. Record both the promise and its evidence rather than only marking a message “answered.”
Choose a support route
- First action
- Answer size, material, use case, shipping region, and limitations.
- Evidence to keep
- Customer question, product link, matching FAQ or product-page gap.
- Timing and next update
- First response within 24 hours on a business day.
- Escalation trigger
- Repeated question escalates into product-page or FAQ update.
- First action
- Check order number, tracking, promised window, and next update time.
- Evidence to keep
- Order number, tracking scan, Shipping Policy, and carrier screenshot.
- Timing and next update
- Give the next step within 24 hours, not only please wait.
- Escalation trigger
- Promise window missed, tracking stalled, or sentiment escalates.
- First action
- Collect photos, packaging, SKU, order number, use context, and batch clues.
- Evidence to keep
- Photos, outer box, SKU, order record, supplier/warehouse feedback.
- Timing and next update
- Give a resolution or escalation decision within 48 hours.
- Escalation trigger
- Reship, refund, supply-chain review, or repeated issue on the same SKU.
- First action
- First check policy window, conditions, item state, and responsibility boundary.
- Evidence to keep
- Order, reason, item state, policy clause, and refund record.
- Timing and next update
- State review timing and expected return-to-original-payment timing.
- Escalation trigger
- Customer rejects policy, evidence is insufficient, value is high, or dispute starts.
- First action
- Respond first and preserve order, shipping, policy, communication, and refund records.
- Evidence to keep
- Timeline, order screenshot, tracking, support log, and policy screenshot.
- Timing and next update
- Handle same day and move to human review.
- Escalation trigger
- Customer mentions bank, PayPal, complaint platform, or public negative review.
- First action
- Trigger after delivery or realistic usage window, and do not automate marketing before resolving issues.
- Evidence to keep
- Delivery time, review content, incentive disclosure, and support state.
- Timing and next update
- Review and retention touches should follow the support state.
- Escalation trigger
- Negative review, quality issue, or repeated complaint goes to human follow-up and page correction first.
A single message can involve several of the six routes. Name a primary route and a person, then collect related evidence. Dispute, serious quality, or uncertain-meaning signals need timely escalation rather than an ordinary queue.
Use product identity to find the cause
“Black ordered, white received” needs more than a color tag. Compare the ad, product page, order, pick record, and received item to find the mismatch. These terms help that investigation; you do not need a separate feed-operations course first.
- SLA
An SLA sets service timing. Here it specifies first human response, progress updates, escalation, and refund review. Check public promises against the actual contract and applicable rules.
Look in support auto replies, ticket notes, refund policies, shipping-exception snippets, and weekly review sheets. Customers use it to know when someone will act; support and operations use it to know when to escalate.
Without an SLA, support often says "we will handle it soon" without a next timing, and delay or refund cases can become disputes or low reviews. Example: For example, if tracking has not moved for five days, the SLA should say the carrier is checked within 24 hours and missed promise windows move into reship, compensation, or refund review.
- Feed
A feed is the product-data stream that sends title, image, price, inventory, SKU, GTIN, and related product facts to Merchant Center, ad platforms, or store systems.
Look in Merchant Center, product-sync tools, ad product groups, onsite search, and product-data sheets. Readers: Ad platforms, search systems, onsite recommendations, support, and warehouse teams indirectly read product facts from the feed.
When feed inventory, color, or images are wrong, support receives cases like "I ordered black and got white" or "the page says in stock but it cannot ship." Example: If a black 20oz tumbler variant is out of stock while the feed still says available, support should write the issue back to inventory sync and the product page.
- Merchant Center
Merchant Center is the Google surface for product data, product review, and Shopping or Performance Max eligibility. It is not a support tool, but it affects whether Google can read product facts correctly.
Look in product diagnostics, item status, feed sync, price and inventory review, and ad product eligibility. Readers: Google reads product facts from Merchant Center; ads, search, support, and operations are affected by whether those facts are accurate.
When Merchant Center price, inventory, image, or status differs from Shopify, support can receive complaints such as "the ad says in stock but the store does not" or "the price is different." Example: If a black 20oz tumbler still appears in ads while Shopify is sold out, support should write the complaint back to Merchant Center diagnostics and sync rules.
- SKU
SKU is the store-owned identifier for a product or variant. It separates color, size, bundle, warehouse picking, and support records.
Look in Shopify product admin, orders, pick lists, feeds, support tickets, and refund/reship records. Readers: Warehouse teams use SKU for picking; support uses SKU to diagnose wrong items, damage, batch clues, and repeated issues.
When SKU naming is messy, support cannot tell whether the buyer received a wrong item, the page image misled them, or inventory sync failed. Example: If TUMBLER-20-BLK and TUMBLER-20-WHT are mismatched between warehouse and page, support should write back to SKU naming and QA sampling.
- GTIN
GTIN is a global trade item number, often represented as a UPC or EAN barcode. It helps Google, marketplaces, and some inventory systems identify the exact product.
Look on product barcodes, Shopify product fields, Merchant Center diagnostics, feed files, and marketplace product data. Readers: Google, marketplaces, inventory systems, and comparison surfaces read GTIN to match product identity.
When GTIN is missing or wrong, the product can fail review, match the wrong item, and make wrong-item or batch support cases harder to trace. Example: If a tumbler has separate 20oz and 30oz barcodes and the feed swaps their GTINs, ads and support records can mix the variants together.
Check whether the product has an applicable GTIN and follow Google’s requirements for that item; do not invent a number to fill the field. Repeated cases should lead back to stock sync, SKU naming, variant images, product pages, and warehouse sampling.
Keep empathy and facts in the same record
Start with the concern, then separate verified facts, unknowns, and the next check. Record language and market separately: one language can span markets, and one market can contain several languages. Keep the buyer’s original wording and policy version. Refund, use-limit, or safety ambiguity needs a person who can verify both meaning and facts.
For this exercise, limit automation to acknowledgment, known status, and reminders for a person to act. Refunds, reships, denials, risk judgments, and safety conclusions require review against actual evidence and authority. This is the exercise’s operating policy, not a claim that Shopify or third-party workflows lack those capabilities. Use nonsensitive fictional content; keep real identities, emails, addresses, payment data, photos, and access details out of the saved records.
Review one case: tone, facts, and boundaries
- Buyer signal
- The buyer reports stalled tracking, a missed promise window, or an update that conflicts with the page promise.
- Acknowledge the concern
- Acknowledge the wait and uncertainty; do not make the buyer do the tracking work for you.
- Read back the facts
- Read back the order, item, representative address, promise window, latest carrier scan, next-update time, and known exception.
- Practice classification
- Suggested practice tag: support:shipping-delay
- Timing and next update
- Write a real, reviewable next-update time instead of only saying "please wait."
- Automation policy for this exercise
- Automated status messages can state a known scan; they cannot decide compensation, reship, refund, or a new delivery date.
- Human-review trigger
- Move to human review when the promise window is missed, address or market scope differs, delays repeat, or buyer concern escalates.
- Buyer signal
- The buyer asks for a refund, reship, exchange, or an explanation for the missing outcome.
- Acknowledge the concern
- Confirm the issue and the requested outcome before using policy language as the whole reply.
- Read back the facts
- Read back order state, item state, policy version, evidence received, actions completed, and facts still unknown.
- Practice classification
- Suggested practice tag: support:refund-review
- Timing and next update
- State when an update or outcome review is due; do not turn the practice route into a real refund result.
- Automation policy for this exercise
- Automation can acknowledge a case; it cannot approve, deny, refund, reship, change inventory, or close a dispute by itself.
- Human-review trigger
- Move to human review for high value, conflicting evidence, policy exceptions, payment disputes, or repeated issues.
- Buyer signal
- The buyer reports damage, a wrong item, an unusual use outcome, injury risk, or a repeated issue on one SKU.
- Acknowledge the concern
- First ask whether the buyer is safe and whether use should stop; do not minimize the report.
- Read back the facts
- Record SKU, batch or order clues, photos, packaging, use context, market, and any temporary action already taken.
- Practice classification
- Suggested practice tag: support:quality-safety
- Timing and next update
- Give the next time for human review without reaching a conclusion about safety, recall, responsibility, or compensation.
- Automation policy for this exercise
- Pause review, UGC, discount, and product-promise automation; automation cannot decide safety, risk, or the outcome.
- Human-review trigger
- Every potential safety, recall, batch-quality, or injury signal needs the real-market human safety and compliance review path.
- Buyer signal
- The buyer mentions a bank, dispute, unauthorized payment, complaint channel, or a material conflict in order and conversation records.
- Acknowledge the concern
- Stay neutral and confirm review; do not accuse the buyer or promise an immediate outcome.
- Read back the facts
- Read back order, payment, and fulfillment state, timeline, policy version, notifications sent, and communication evidence.
- Practice classification
- Suggested practice tag: support:risk-dispute
- Timing and next update
- Name the human-review and next-update timing without presenting response timing as a dispute or payment conclusion.
- Automation policy for this exercise
- Automation cannot cancel an order, refund, deny a request, label fraud, or send an accusatory message on its own.
- Human-review trigger
- Keep every payment, identity, dispute, or high-risk order signal for human review within the real account authority.
- Buyer signal
- The buyer uses another language, a policy or product term is misunderstood, or translation could change refund, return, use, or safety meaning.
- Acknowledge the concern
- Thank the buyer for clarifying, then confirm the preferred language and the actual problem to resolve.
- Read back the facts
- Record the original buyer wording, market, page or policy version used, meaning confirmed, and translation still needing review.
- Practice classification
- Suggested practice tag: support:language-review
- Timing and next update
- State when a reviewed next step will arrive; do not treat machine translation as the final explanation or promise.
- Automation policy for this exercise
- An automated reply can acknowledge receipt, but cannot translate policy, decide eligibility, or continue marketing when meaning is unclear.
- Human-review trigger
- Use human review that can verify language and facts when refund, return, payment, use limitations, or safety meaning is involved.
The support:* strings are suggested exercise classifications. They create no Shopify tags and are distinct from Inbox’s automatic topic labels and Flow customer tags. Potential injury, recall, or batch-quality signals go to the actual market’s human safety/compliance process. Record interim steps such as pausing use or promises without making a safety or liability determination here.
Each group has separate save, restore, and clear controls. The core group holds the lane, gates, and decision; two case-note groups hold the eight reply/evidence fields; views and team notes save separately. Each note allows 2000 characters. Old notes had no text-length limit: keep complete longer originals elsewhere; a short imported sample does not prove lossless handling at arbitrary length.
Case decision
Self-check not answered
Case decision result
Note
Choose an answer
Review facts and hand over
Reconsider the decision
Reconsider the decision
Record completeness
Seven items considered
Hold
Complete the missing record
A fresh record starts on the first shipping lane with empty gates and an unanswered decision. Restoring an old record preserves its choices, ticks, and wrong answer. Clearing the core resets only that group; it leaves other notes alone. The old save time remains in the old record. A native save time describes the new save, not an imported learner answer.
Turn the message into a useful first reply
The first reply can precede the final solution. Acknowledge the experience, state what you know and do not know, give a check and update time, and name the escalation trigger. Avoid long silence while composing a perfect explanation, defensive language, vague reassurance, and conflicting answers across teammates.
Build a useful first reply
- Buyer message
- "I ordered 10 days ago and tracking has not moved. Did you even ship it?"
- Underlying concern
- The shipping question also shows that the buyer is starting to doubt the store’s reliability.
- Why a weak reply causes trouble
- If the reply only says "please wait", the buyer gets no timing and no escalation rule. The next step can become a dispute or public low review.
- Reply frame
- (1) Acknowledge the issue: we can see tracking is stuck at a scan and we will check it.; (2) Give facts: order number, ship date, last tracking scan, and whether the promised window is still open or already missed.; (3) Give the next timing: for example, contact the carrier within 24 hours and reply with the next step by a clear date.; (4) Give the escalation line: if the promised window is missed with no update, move into reship, compensation, or refund review.
- Ticket evidence
- (1) Order number and email; (2) Screenshot of the last tracking scan; (3) Promised window from the Shipping Policy; (4) Next reply time and assigned teammate
- Wording to avoid
- Do not only say "shipping is slow, please wait."
- Buyer message
- "The cup arrived cracked. I want a refund."
- Underlying concern
- The buyer needs the store to acknowledge the problem, collect evidence, and explain the resolution path.
- Why a weak reply causes trouble
- Arguing over responsibility before reviewing the facts can sound evasive. If you skip proof, repeated same-SKU damage will not show up as a root cause.
- Reply frame
- (1) Apologize and say you will handle it. Avoid asking the buyer to retell the same problem.; (2) Ask for proof in one clean list: order number, outer box photo, damaged item photo, SKU or package label.; (3) State possible outcomes: reship, partial refund, or return/refund, decided from photos and stock.; (4) If the same SKU repeats, log it for supplier or warehouse review. Do not only close the single ticket.
- Ticket evidence
- (1) Damaged item and outer box photos; (2) SKU, batch clue, or package label; (3) Reship/refund amount and handling time; (4) Whether it enters supply-chain review
- Wording to avoid
- Do not start with "return it first under policy" unless policy, photos, and responsibility are already clear.
- Buyer message
- "I do not like this color. Can I return it?"
- Underlying concern
- This may not be a store mistake, but support still needs to make the policy window, item condition, and return cost clear.
- Why a weak reply causes trouble
- If each agent decides by feeling, cost gets out of control. Rigid wording can add friction and lead to a poor review.
- Reply frame
- (1) Confirm purchase date, order number, whether the item is unused, and whether packaging is complete.; (2) Explain the return policy window in one sentence. Do not paste a long policy block.; (3) State what the buyer should do: send photos, return address, return shipping, and expected refund timing.; (4) Log the return reason and review next week whether color, size, or images need product-page updates.
- Ticket evidence
- (1) Policy window and item condition; (2) Return reason category; (3) Return shipping and refund timing note; (4) Whether the product page needs an update
- Wording to avoid
- Do not only say "handled by policy." The buyer needs the next step.
Route a mixed support message
- Buyer message
- "Tracking has not moved for five days. Did you actually ship it?"
- Risky route
- Only paste the tracking link or ask the buyer to keep waiting.
- Correct route
- Route to shipping exception: check last scan, promise window, carrier state, and next update time.
- First reply
- Acknowledge the stalled scan, say you will check with the carrier, and promise the next step within 24 hours.
- Evidence to keep
- Order number, last tracking scan, Shipping Policy promise window, and carrier check record.
- Escalation trigger
- If the promise window is missed with no update, escalate to reship, compensation, or refund review.
- Where the learning goes
- Write back to Shipping Policy, shipping notification, and delay-case snippet.
- Buyer message
- "The cup is cracked. I sent photos. What will you do?"
- Risky route
- Ask for a return first, or argue whether shipping caused the damage.
- Correct route
- Route to damage/wrong item: collect complete proof, then decide reship, partial refund, return/refund, or supply-chain review.
- First reply
- Apologize, confirm photos were received, then ask once for order number, outer-box photo, and SKU/package label.
- Evidence to keep
- Damage photo, outer-box photo, SKU, batch clue, reship/refund amount, and handling time.
- Escalation trigger
- Escalate when the same SKU repeats, value is high, or the buyer threatens public complaint.
- Where the learning goes
- Write back to packaging rules, supplier review, and product-page material or size notes.
- Buyer message
- "I ordered black and received white. I do not want to wait too long."
- Risky route
- Treat it as a preference return and ask the buyer to pay return cost.
- Correct route
- Route to wrong-item handling: confirm order, picking, stock, and replacement path so store error is not pushed onto the buyer.
- First reply
- Acknowledge the item does not match the order, say you will check stock, and give timing for replacement or refund decision.
- Evidence to keep
- Order screenshot, received-item photo, package label, warehouse pick record, and stock status.
- Escalation trigger
- Escalate when stock is unavailable, wrong-item cases repeat, or the buyer asks for immediate refund.
- Where the learning goes
- Write back to warehouse pick rules, SKU naming, variant images, and QA sampling.
- Buyer message
- "If this is not solved today, I will dispute it with my bank."
- Risky route
- Leave it in the normal queue, or refund in full only to end the conversation.
- Correct route
- Route to chargeback risk: handle same day and preserve order, shipping, policy, communication, refund, and timeline records.
- First reply
- Confirm the case is escalated to a human, say a clear option will be sent today, and ask for proof needed for the decision.
- Evidence to keep
- Full timeline, order record, tracking, policy screenshot, support conversation, and refund or reship record.
- Escalation trigger
- Escalate when bank, PayPal, complaint platform, public low review, or high order value appears.
- Where the learning goes
- Write back to dispute evidence packet, escalation SLA, refund boundary, and blocked high-risk wording.
What the first incident reveals
- First signal
- The first real buyer says tracking has not moved for four or five days and starts doubting whether you shipped.
- Wrong move
- Only send the tracking link or say please wait, without a next update time or escalation trigger.
- First reply
- Acknowledge the stalled scan, state the last scan and promised window, say you will check the carrier within 24 hours, and explain the compensation, reship, or refund review after the promise window is missed.
- Evidence to keep
- Order number, last tracking scan, Shipping Policy promise window, carrier check record, and next reply time.
- Resolution path
- Inside the promise window, give the next update time. After a missed window, review applicable rights and promises before deciding compensation, reship, or refund. Confirmed loss moves into refund/reship handling.
- Where the learning goes
- Write back to Shipping Policy, shipping email, order-status copy, and delay first-reply snippet.
- Action to pause
- Before carrier check and next update time exist, do not keep sending a wait-only template.
- First signal
- The buyer receives the item, says it is unsatisfactory, wrong size, or problematic, and asks for a refund.
- Wrong move
- Refund in full just to save time, or only paste policy and make the buyer interpret it.
- First reply
- First separate store fault, shipping damage, wrong item, quality issue, or preference return. Ask once for order number, photos, item state, and package state, then give review timing.
- Evidence to keep
- Order number, refund reason, photos/video, item state, policy window, refund amount, and expected original-payment return timing.
- Resolution path
- For store fault, prioritize an appropriate reship or refund. For preference returns, check applicable rights, policy window, and item state. Request only evidence needed for the decision; do not use evidence collection to delay an owed refund indefinitely.
- Where the learning goes
- Write back to return policy, product-page size/material notes, refund review table, and support cost review.
- Action to pause
- Without reason category and proof, do not let individual support emotion decide full refund, rejection, or reship.
- First signal
- An early buyer leaves a one- or two-star review mentioning slow shipping, mismatch, slow support, or unclear refund.
- Wrong move
- Focus only on removing or changing the review, or keep sending automated repeat-purchase and review requests.
- First reply
- Pause automation for this buyer first. Public reply should acknowledge the issue and support entry; privately check order proof, shipping, product, support log, and refund state.
- Evidence to keep
- Review text, order number, product SKU, support log, shipping scan, refund state, and whether the same issue repeats.
- Resolution path
- Single case: repair the buyer experience. Repeated issue: write back to page, shipping promise, SKU/feed, or QA. High-risk low review: human follow-up, no automated repeat-purchase trigger.
- Where the learning goes
- Write back to review handling table, product-page trust assets, FAQ, lifecycle-email pause rule, and weekly review.
- Action to pause
- Before the low-review cause is handled, do not send repeat-purchase discount, UGC request, or review reminder to that buyer.
For a ten-day-old order with no scan for five days, establish carrier handoff, the last scan, and the promised window. “It will arrive tomorrow” needs fresh evidence. Committing to a carrier check is a next step the team can own. Respond to a public complaint with the issue and support entry, then verify the order privately. Do not expose buyer details or make a refund conditional on deleting a review.
Delay-reply decision
Self-check not answered
Delay reply result
Note
Choose an answer
Reconsider the decision
Review facts and hand over
Reconsider the decision
Six scripts connect the reply to internal action
A script fixes the opening, evidence request, next timing, wording to avoid, and internal update. Adapt it to language, evidence, stock, and authority before sending. A carrier inquiry, refund approval, and money reaching a bank are different outcomes.
Choose and adapt a script
- Trigger
- The buyer says tracking has not updated, the estimate is missed, or they suspect the store never shipped.
- Adaptable opening
- Acknowledge the delay and anxiety instead of making the buyer read tracking: I can see your parcel has not updated since last_scan; I will check the carrier and promised window first.
- Evidence to request together
- Order number, last tracking scan, promised delivery window, carrier check record, and next update time.
- Next timing
- Give the next update within 24 hours; after the promise window is missed, review compensation, reship, or refund.
- Internal update
- Write back to Shipping Policy, order-status page, shipping email, and delay first-reply snippet.
- Wording to avoid
- Do not only say "please wait," and do not promise a new delivery date without evidence.
- Portable summary
- A delay reply must state the last scan, next update time, and the boundary after the promise window is missed.
- Trigger
- The buyer is unhappy, says the size is wrong, wants a return, or asks for an immediate refund.
- Adaptable opening
- Acknowledge the request, then explain what needs checking and what happens next: I will first confirm whether this is a product issue, shipping issue, or preference return, then give you a clear resolution under the policy.
- Evidence to request together
- Order number, refund reason, photos/video, item state, packaging state, whether it was used, and preferred resolution.
- Next timing
- Give the review result within one business day after evidence arrives; when refunding, state the expected original-payment return timing.
- Internal update
- Write back to Refund Policy, product-page size/material notes, refund review table, and support cost review.
- Wording to avoid
- Do not refund in full immediately, and do not only paste policy clauses for the buyer to interpret.
- Portable summary
- A refund script should classify reason and proof before giving review timing, amount boundary, and payment-return expectation.
- Trigger
- The buyer receives damage, wrong color, wrong spec, missing part, or suspects the item does not match the page.
- Adaptable opening
- Make responsibility for the check clear: we will verify this by order and photos, without sending you back and forth between the warehouse, carrier, and product page.
- Evidence to request together
- Outer-box photo, item photo, SKU/variant, package label, order number, missing part, or damaged area.
- Next timing
- Give a reship, partial refund, return/refund, or supply-chain review decision within 48 hours.
- Internal update
- Write back to SKU naming, warehouse picking rule, packaging QA, product images, and supplier feedback.
- Wording to avoid
- Do not doubt the buyer first, and do not only ask them to return it before any review; first decide whether direct reship or compensation is appropriate.
- Portable summary
- A damage or wrong-item script should collect photos, SKU, order, and package proof in one pass.
- Trigger
- The buyer leaves a one- or two-star review mentioning slow delivery, mismatch, slow support, or unclear refund.
- Adaptable opening
- The public reply only acknowledges the issue and support entry: We have seen your feedback and will verify shipping, product, and handling records through the order support channel.
- Evidence to request together
- Review text, order number, support log, shipping scan, refund state, and whether the issue repeats.
- Next timing
- Pause automation for this buyer the same day; verify privately and give the next step within 24 hours.
- Internal update
- Write back to review handling table, product-page trust assets, FAQ, lifecycle email pause rule, and weekly review.
- Wording to avoid
- Do not argue publicly, pressure review changes, threaten removal, or keep sending repeat-purchase discounts.
- Portable summary
- A low-review script first pauses automation, keeps the public reply restrained, and repairs privately using order evidence.
- Trigger
- The buyer mentions bank, PayPal, complaint platform, scam, or demands immediate handling for a high-value order.
- Adaptable opening
- De-escalate and move to human review: I will handle this order separately, preserve order, shipping, communication, and refund records, and give you a clear next step today.
- Evidence to request together
- Order timeline, payment status, fulfillment status, tracking, policy screenshot, support conversation, and refund or reship record.
- Next timing
- Move to human review the same day and give the next step the same day; do not leave high-risk buyers in the normal queue.
- Internal update
- Write back to dispute evidence packet, escalation timing, refund boundary, and high-risk wording guardrail.
- Wording to avoid
- Do not threaten the buyer, deny the issue, or let frontline support without authority keep arguing.
- Portable summary
- A chargeback-risk script assigns same-day human review and preserves the evidence needed to resolve the dispute.
- Trigger
- The order is delivered with no open support issue, and you plan a review request, UGC request, or repeat-purchase discount.
- Adaptable opening
- Confirm experience before asking: If you have used the product for a while, we welcome an honest review; if anything is still wrong, reply here first and we will handle the experience.
- Evidence to request together
- Delivery time, support state, incentive disclosure, last touch time, and whether an open ticket exists.
- Next timing
- Send after delivery and a realistic usage window; pause marketing when any issue is unresolved.
- Internal update
- Write back to review timing, email automation conditions, low-review pause rule, and retention segmentation.
- Wording to avoid
- Do not trade cash for positive reviews, and do not keep asking for reviews during unresolved refund, delay, or low-review cases.
- Portable summary
- A review or retention script checks objective case completion, permission, and product cycle. Open cases receive human follow-up; review invitations resume under consistent criteria without screening for praise.
Shipping delay short email
Use this as an editable draft. Verify the facts and replace each placeholder with a checked scan or explicit time. The braces are placeholders, not executable code.
Subject: Update on your order delivery
Hi, we can see your parcel has not updated since
{last_scan}. We will check with the carrier and update you before{next_update_time}. If the promised delivery window is missed and tracking still does not recover, we will review compensation, reship, or refund options.
Confirm first: Order number, last scan, promised delivery window, carrier check record, and next update time. Do not promise a new delivery date before carrier evidence is available.
Damage reship short email
Use this as an editable draft. Verify the facts and replace each placeholder with a checked scan or explicit time. The braces are placeholders, not executable code.
Subject: About the damaged item you received
Hi, we are sorry the item arrived with an issue. Please reply once with your order number, outer-box photo, damaged-item photo, and SKU or package label. We will confirm before
{review_time}whether this should be a reship, partial refund, return/refund, or supply-chain review.
Confirm first: Order number, outer box, item photos, SKU/variant, package label, missing part, or damaged area. When the same SKU repeats damage, pause review requests and scaling, then review packaging or supplier root cause.
Connect replies to the six post-purchase stages
The script answers “how should I reply?” The flow board answers “what happens in which system next?” A closed ticket with ongoing review reminders, a refund with unreconciled stock, or repeated delays without a changed promise indicates a handoff failure. Select the weakest stage and read its buyer question, action, record, pause line, and destination for the correction.
Find the weakest post-purchase stage
- Trigger
- The buyer has just ordered and has no tracking yet; they care whether the order is correct and when it ships.
- Buyer question
- Did my order go through? What are the address, amount, items, and next step?
- Support action
- Confirm order number, product/variant, shipping address, payment status, and expected dispatch window; do not make the buyer infer it from scattered emails.
- System record
- Shopify order Timeline, order confirmation email version, Customer events purchase event, and support entry.
- Action to pause
- If address, payment capture, stock, or high-risk order status is unresolved, do not ship or continue automation.
- Where the learning goes
- Write back to order email, FAQ, address-change language, and launch QA test-order record.
- Portable summary
- The order confirmation step should leave order number, payment, address, dispatch window, and support entry.
- Trigger
- The order is fulfilled and the buyer starts watching tracking, but scans can be slow, stalled, or inconsistent with the promise window.
- Buyer question
- Where is the parcel now? If tracking stalls, when will someone act?
- Support action
- State the last scan, promise window, next update time, and compensation/reship/refund boundary after timeout.
- System record
- Tracking page, carrier check screenshot, Shipping Policy version, and delay-case snippet.
- Action to pause
- Without last scan, next update time, and timeout boundary, do not only send a link and ask the buyer to wait.
- Where the learning goes
- Write back to shipping promise, order-status page, fulfillment email, and Fulfillment Promise Checker.
- Portable summary
- The tracking step should turn scan, promise window, next update, and timeout handling into one clear line.
- Trigger
- The buyer reports delay, damage, wrong item, refund request, low review, or chargeback risk, so support must enter evidence mode.
- Buyer question
- Have you seen my issue? What proof is missing, who is handling the case, and when will I get a result?
- Support action
- Ask once for order number, photos/video, SKU, tracking, policy version, and preferred resolution; give first response, next update, and human-review condition.
- System record
- Support thread, ticket ID, order Timeline, policy screenshot, dispute evidence packet, or refund review table.
- Action to pause
- Before proof is complete, do not argue responsibility first or let frontline support without authority keep explaining.
- Where the learning goes
- Write back to service reply scripts, refund/reship rules, FAQ, and high-risk wording guardrails.
- Portable summary
- The support case step should leave a proof list, assigned teammate, next update time, and review trigger.
- Trigger
- Proof is sufficient and the team must decide cancel, reship, partial refund, return/refund, no refund, or supply-chain review.
- Buyer question
- What resolution will I receive? What are the amount, timing, payment return path, and next action?
- Support action
- State the resolution, amount, timing, original-payment return expectation, and whether a return is required based on responsibility boundary.
- System record
- Refund / Return / Exchange record, reship order, inventory deduction, and supplier or warehouse feedback.
- Action to pause
- If the same SKU repeats damage, wrong item, or refund cases, do not treat it as isolated; pause scaling and review root cause.
- Where the learning goes
- Write back to Refund Policy, SKU naming, packaging QA, profit review, and WBR.
- Portable summary
- The refund/reship step should lock amount, timing, responsibility boundary, and whether scaling must pause.
- Trigger
- The order is delivered, a realistic use window has passed, and no support case is open.
- Buyer question
- Have I actually used the product? If something is still wrong, can you fix it before asking for a review?
- Support action
- Check support state before requesting an honest review; disclose incentives and do not filter out negative buyers.
- System record
- Delivery time, review request log, incentive disclosure, open ticket status, and public review handling record.
- Action to pause
- Pause review request and repeat-purchase discount while refund, delay, low review, or damage remains unresolved.
- Where the learning goes
- Write back to review timing, product-page trust assets, FAQ, and lifecycle email pause condition.
- Portable summary
- The review request step checks delivery, usage window, and support state before the touch.
- Trigger
- The customer experience is normal, and the product has replenishment, bundle, upgrade, or education next steps.
- Buyer question
- Was the experience smooth? What is the real reason to buy again, beyond a discount?
- Support action
- Use three operational states: complete, handled but awaiting confirmation, and still open. Completed cases can receive suitable contact based on permission, product cycle, and margin; confirm handled cases first; keep open cases with a person and pause promotion. Apply consistent objective review-invitation criteria rather than selecting by satisfaction.
- System record
- Email Flow conditions, Customer tag, last purchased SKU, support state, repeat offer, and profit boundary.
- Action to pause
- Without profit boundary, support state, or inventory/fulfillment capacity, do not push discounts only to lift repeat purchase.
- Where the learning goes
- Write back to lifecycle email, profit tools, inventory plan, and support weekly review.
- Portable summary
- The repeat-purchase step should carry support state, product cycle, inventory fulfillment, and profit boundary.
Keep authorization, capture, a refund record, refund receipt, fulfillment status, and physical transit separate. The order Timeline and a Customer events purchase event serve different purposes; one event cannot prove funds, shipment, or support resolution. Reconcile a reship with its order or fulfillment record, inventory, and notification. Available actions depend on the actual account, channel, and payment provider.
Read the first week through buyer questions
This 7-day map is a classroom reading sequence, not a dispatch, delivery, or refund deadline for every order. Ten minutes after order on Day 0, Day 1, Days 2-3, Days 4-5, Days 6-7, and after Day 7 organize confirmation, waiting, tracking, escalation, resolution, and follow-up. Act on actual delay, dispute, or safety risk when it appears rather than waiting for a map date.
Read the buyer timeline
- Buyer question
- Did my order go through? Are address, item, amount, and expected dispatch time correct?
- Weak reply
- Only send the system order confirmation email and make the buyer infer everything.
- Support action
- The order confirmation email should show order number, product/variant, address, payment status, expected handling time, and support entry.
- Evidence to keep
- Shopify order Timeline, order confirmation email version, payment capture state, address completeness, and inventory state.
- System connection
- Order confirmation email, order status page, support entry, and address-change language.
- Where the learning goes
- If buyers repeat the same question, write it back to FAQ, first screen of order email, and post-checkout message.
- Action to pause
- Before address, payment, high-risk status, or stock is confirmed, do not ship or continue automation.
- Portable summary
- Day 0 should confirm order success, information accuracy, and when the next step happens.
- Buyer question
- Why has it not shipped yet? Is it out of stock, or is the order stuck?
- Weak reply
- Only say "we will ship soon" with no handling time, cutoff, or exception condition.
- Support action
- Put handling time, warehouse cutoff, preorder/out-of-stock exceptions, and next update timing into support snippets and order status page.
- Evidence to keep
- Fulfillment status, stock/supplier confirmation, warehouse cutoff rule, and Shipping Policy handling time.
- System connection
- Order status page, shipping notification, Shipping Policy, and support first-reply snippet.
- Where the learning goes
- If pre-dispatch waiting questions grow, write them back to the product-page shipping block and Fulfillment Promise Checker.
- Action to pause
- When handling-time proof is weak, pause strong promises such as "ships today" or "ships in 24 hours."
- Portable summary
- Day 1 should explain pre-dispatch waiting so the buyer does not guess whether the order is stuck.
- Buyer question
- Why is tracking available but not moving? When should it update?
- Weak reply
- Only paste the tracking link and ask the buyer to wait.
- Support action
- Explain last scan, carrier first-scan delay, promise window, next update timing, and the boundary after timeout.
- Evidence to keep
- Tracking page, carrier screenshot, Shipping Policy version, and last scan time.
- System connection
- Shipping email, tracking page, delay-case snippet, and support SLA.
- Where the learning goes
- When tracking delays repeat, write back to shipping promise, order status page, and carrier choice.
- Action to pause
- Without last scan and next update time, do not promise a new delivery date.
- Portable summary
- Day 2-3 should translate stalled tracking into follow-up timing and boundaries.
- Buyer question
- Was I scammed? Can I get a refund, reship, or should I keep waiting?
- Weak reply
- Keep the case in the normal queue, or refund immediately just to calm the buyer.
- Support action
- Move into support-case mode: ask once for order, tracking, photos/video, policy version, and preferred resolution, then give human-review condition and same-day next step.
- Evidence to keep
- Support thread, ticket ID, order Timeline, policy screenshot, dispute evidence packet, or refund review table.
- System connection
- Ticket system, refund review table, dispute evidence packet, and escalation SLA.
- Where the learning goes
- Write exception type back to refund/reship rules, support wording guardrails, FAQ, and policy promises.
- Action to pause
- When chargeback threat, high-value order, or repeated same-SKU exception appears, do not let frontline support handle it alone.
- Portable summary
- Day 4-5 should switch from normal replies to evidence, escalation, and resolution boundaries.
- Buyer question
- What is the final resolution? What are the amount, timing, return path, and next action?
- Weak reply
- Only say "handled" with no amount, original-payment timing, reship order, or next instruction.
- Support action
- State reship, partial refund, return/refund, no refund, or supply-chain review by responsibility boundary, and tell the buyer whether any action remains.
- Evidence to keep
- Refund / Return / Exchange record, reship order, inventory deduction, and supplier or warehouse feedback.
- System connection
- Refund record, reship order, inventory, profit review, and support weekly report.
- Where the learning goes
- Write resolution back to policy page, product page, packaging QA, SKU naming, and WBR.
- Action to pause
- When same-SKU exceptions repeat, pause scaling and review requests before finding root cause.
- Portable summary
- Day 6-7 should lock resolution, cost, evidence, and root-cause write-back.
- Buyer question
- Is my experience really resolved? Is it appropriate to ask for a review or send a discount now?
- Weak reply
- Automatically ask for review or send discount by fixed timing without checking support state.
- Support action
- Use three operational states: complete, handled but awaiting confirmation, and still open. Completed cases can receive suitable contact based on permission, product cycle, and margin; confirm handled cases first; keep open cases with a person and pause promotion. Apply consistent objective review-invitation criteria rather than selecting by satisfaction.
- Evidence to keep
- Delivery time, open ticket state, refund/reship state, review incentive disclosure, and last touch time.
- System connection
- Review app, Email Flow, Customer tag, UGC permission record, and repeat-purchase offer.
- Where the learning goes
- Write back to review timing, retention segmentation, email pause condition, product-page trust assets, and FAQ.
- Action to pause
- Pause review request and repeat-purchase discount while refund, delay, low review, or damage remains unresolved.
- Portable summary
- After Day 7, do not automate blindly; check whether the experience is truly resolved first.
Record distinct return, refund, and reship outcomes
Separate cancellation before dispatch, delay, confirmed loss, damage, wrong item, quality dispute, preference return, refused-and-returned parcels, and duty refusal. Each needs different records. Check applicable consumer rights, promises, and actual order status before applying policy. Return windows, return charges, and restocking fees are not universal rules. Ask only for evidence needed for the decision without using it to postpone an obligation.
Separate refund and reship reasons
- When it applies
- Order is unfulfilled and customer wants to cancel.
- Next action
- Cancel and refund quickly to reduce friction and support load.
- Risk
- Delay can turn simple cancellation into complaint.
- When it applies
- Promise window is near or already missed.
- Next action
- Check scan, give next update time, then compensate, reship, or refund if needed.
- Risk
- Only saying wait longer increases dispute risk.
- When it applies
- Customer reports damage, wrong item, functional issue, or mismatch.
- Next action
- Collect evidence, then decide reship, partial refund, return/refund, or supply-chain review.
- Risk
- Repeated same-SKU issues should not be treated as isolated cases.
- When it applies
- Customer dislikes it, it does not fit, or ordered wrong item, but item is normal.
- Next action
- Check applicable consumer rights first, then the relevant policy window, item state, return shipping, and any permitted restocking-fee rules. A policy cannot automatically exclude mandatory rights.
- Risk
- Do not let individual support emotion set cost boundary.
Once a decision is made, record amount, currency, reason, assigned person, time, return requirement, return-label and stock state, and the buyer’s next action. Provider and bank processing determine the payment path and timing; “refund submitted” does not mean “buyer received funds.” For a Shopify Payments chargeback, check dispute status and the evidence deadline first. A refund cannot be issued while the chargeback is open; check available actions after formal resolution. An inquiry follows a different path from a chargeback, and other providers have their own procedures.
Self-serve returns provide a request entry, not automatic approval, exchange, or refund. Current Shopify documentation requires the customer-accounts experience. A store retaining legacy accounts can provide a separate customer-accounts URL; that does not make the legacy account itself support self-serve returns. The documentation also excludes exchange requests from self-serve returns. Verify eligibility and notifications individually; a request confirmation only acknowledges receipt.
Resolve the case before planning follow-up
Check delivery and a realistic use period, then open issues, last contact, permissions, stock, and margin. While service remains unresolved, pause review reminders, UGC requests, discounts, and upsells while a person follows up. Confirm handled-but-unverified outcomes first. UGC means buyer-created photos, videos, or text; promotional reuse needs permission, disclosure, and privacy checks. Repeat purchase can involve replenishment, bundles, upgrades, education, or membership rather than only discounts.
Pause because a case is objectively open and resume under consistent criteria, not because a buyer may criticize you. The US FTC Q&A warns that soliciting only expected-happy customers may violate the FTC Act. Incentives must not require positive sentiment and can require disclosure. Do not use threats or baseless accusations to force review removal. Check other markets and review-platform rules separately.
Choose follow-up by service state
- When it applies
- Delivered successfully with no open support issue.
- Next action
- Once the experience is complete, use consistent objective criteria for review invitations. Plan UGC, replenishment, or bundles separately around permission, product cycle, and stock; do not select by expected praise.
- Risk
- Asking too early reduces review quality.
- When it applies
- Had an issue, but reship, refund, or resolution is complete.
- Next action
- Repair the relationship and confirm the outcome first. Resume suitable contact under the same objective completion criteria, preserving the chance for an honest review without requiring satisfaction or a changed rating.
- Risk
- Pushing repeat purchase immediately after a fix can worsen experience.
- When it applies
- Repeated complaints, low review, dispute risk, or severe quality issue.
- Next action
- Pause promotion while complaints, disputes, or serious quality issues remain open, and assign human follow-up and root-cause review. A low rating or expected criticism is not a reason for permanent review exclusion.
- Risk
- Automation can amplify frustration.
With suitable permission and disclosure, praise and usage feedback can explain a product. Classify criticism by delivery, mismatch, slow support, unclear refund, or quality. Selected praise should not imply a universal experience. Repeated issues should change product pages, FAQs, delivery promises, SKU/feed data, packaging QA, and email rules rather than only prompting a nicer reply.
Use metrics to decide what to fix
Track response time and resolution time separately. Review tags, refund/reship reasons, reopened cases, and page changes within the same time window, market, and SKU. Small samples do not establish general performance. Support can reveal causes to investigate; a metric improving after a template change does not by itself establish causation.
First-contact resolution (FCR)
After the first interaction, does the buyer truly need no next step, or did they only receive an initial reply?
Record the issue tag, first reply, fact readback, outcome, reopen state, and buyer confirmation.
Do not count an automated acknowledgment or closed ticket as FCR; it is a review signal, not a staff score or satisfaction conclusion.
Customer satisfaction (CSAT)
Once the case is actually complete with no unresolved refund or safety issue, how does the buyer rate the support experience?
Record invitation conditions, language used, send time, open-ticket state, and feedback wording or summary.
Continue helping unresolved or escalating cases and apply consistent completion criteria for surveys. Record exclusions, nonresponses, and sample size; a small or selected response set does not establish overall satisfaction.
Contact rate
Within the same week, market, or SKU, which tags keep generating contacts and does the page or fulfillment promise need correction?
Keep the same denominator, time window, market or SKU, tag count, and write-back action.
Use contact rate to locate problems while preserving normal replies, complete tags, and access to support.
Define what counts as FCR resolution and the reopen window, the CSAT invitation scope and response rate, and the contact-rate denominator before comparing. Distinguish two ratios: orders with a customer contact divided by orders in the same period, and messages divided by orders in that period. CSAT is also distinct from a public product review. If unresolved cases are excluded from a survey, record that limitation rather than claiming all customers are satisfied.
Turn support findings into operating changes
FAQ
- Input
- Repeated size, material, shipping, duties, and return questions.
- Update
- Add to FAQ, product page, policy page, and order emails.
Product page
- Input
- Customers do not understand use case, specs, limitations, or actual result.
- Update
- Update product copy, visuals, comparison table, and trust assets.
Shipping promise
- Input
- Delays, duties, tracking, or remote regions create repeated inquiries.
- Update
- Update Shipping Policy, product-page promise, and support snippet.
Reviews and creative
- Input
- Real praise, low reviews, usage feedback, and common objections.
- Update
- Praise becomes trust asset; low reviews become page and support playbook fixes.
In the weekly review, record a person, page/template version, change, and retest date. Three repeated cases are a classroom prompt to investigate the system, not a statistical threshold. Check whether the product page, fulfillment, feed, SKU, policy, or messaging keeps creating the same problem.
Verify the actual tools and human handoff
Check hours, time zone, and first-reply settings at Sales channels > Inbox > Chat settings > Availability. Automatic first replies apply to staff-handled conversations. Where Inbox agent is enabled, AI handling and staff handoff depend on configuration and availability. If handoff is unavailable, the documented fallback gives the sender email to the buyer to initiate contact; it does not mean an email was sent or a person took ownership. Verify actual availability and permissions in an authorized store.
Inbox automatic topics, exercise classifications, and Flow customer tags are separate records. The conversation guide limits automatic topic labels to English; use a reviewable manual classification or suitable system for other languages. Add customer tags acts on the workflow’s Customer ID, and another app or admin can overwrite tags. Check trigger, run history, customer, and downstream conditions; a tag proves neither resolution nor marketing permission.
Review suggested replies for tone and accuracy. Editing a reply does not itself correct the product, policy, page, or Knowledge Base facts used as source information. Fix the source and retest repeated errors. Open/Closed conversation status is not FCR, buyer confirmation, or a refund outcome. Verify chat permission and notification ownership when assigning staff.
Where to reconcile the same order
Order and refund
- Record location
Shopify Admin > Orders > target order > Timeline / Refund- Record and update
- Order, payment/fulfillment state, refund amount/reason, person, and time; update refund snippets, policy, and SLA.
Returns and exchanges
- Record location
Shopify Admin > Orders > target order > Return / Exchange- Record and update
- Reason, window, label state, exchange SKU, final refund/reship outcome; update sizing, packaging, and warehouse rules.
Conversation continuity
- Record location
Support inbox / helpdesk ticket > customer message thread- Record and update
- Ticket ID, first response, next update, template, review trigger, and buyer promise; update FAQ and frontline scope.
Notifications and invitations
- Record location
Shopify Admin > Settings > Notifications; review tool > request log- Record and update
- Template version, trigger, delivery/use window, request time, and disclosure; correct notification and retention conditions.
Reconcile four jobs: confirmation of item, amount, address, and next step; consistent tracking and exception messages; a fixed support entry, timing, and evidence standard; and genuine reviews with applicable disclosures. The next teammate should be able to reopen the same record. A screenshot can help locate the issue; also check the record’s current state.
Series start
For field-by-field English admin work
Use this lesson to define the decision and handoff. Use Notifications and email for message-by-message testing and Locations, inventory, and fulfillment for stock and routing. The reading routes do not mean live messages, orders, or refunds were executed.
Work through one complete practice case
Set contact details and response timing
State where buyers contact you, when someone reads the message, how quickly normal questions receive a first response, and how quickly refunds or chargeback risk move to human review. Align email, chat, ticket, or contact form with order records first.
Keep as evidence
Keep the record location, person responsible, and remaining unknowns. The classroom exercise does not act on live orders or contact buyers.Define six support routes
Do not send every message into the same template. Each route needs issue type, first action, evidence, person handling it, SLA, human-review condition, and write-back location.
Keep as evidence
Keep the record location, person responsible, and remaining unknowns. The classroom exercise does not act on live orders or contact buyers.Record evidence, next update, and triggers
Shipping needs tracking and promise window. Refund needs policy version and item state. Damage or wrong item needs photos, SKU, and packaging proof. Chargeback risk needs a timeline and order record. Every reply gives the next update time.
Keep as evidence
Keep the record location, person responsible, and remaining unknowns. The classroom exercise does not act on live orders or contact buyers.Route the first incident
Do not treat the first incident as a one-off. Decide whether it exposes shipping promise, refund boundary, product data, review request, or repeat-purchase automation, then write it back to the right page, email, policy, or backend record.
Keep as evidence
Keep the record location, person responsible, and remaining unknowns. The classroom exercise does not act on live orders or contact buyers.Adapt the reply script
Each script fixes the opening line, evidence request, next timing, what not to say, and internal write-back location, but it is not copy-paste support. The shipping delay short email and damage reship short email can serve as bases. The goal is a buyer who knows the next step and a next person who can continue from the same record.
Keep as evidence
Keep the record location, person responsible, and remaining unknowns. The classroom exercise does not act on live orders or contact buyers.Connect the six post-purchase stages
Check each node for buyer question, support move, system record, action to pause, and write-back location. Unresolved support state pauses reviews, UGC, discounts, and upsells.
Keep as evidence
Keep the record location, person responsible, and remaining unknowns. The classroom exercise does not act on live orders or contact buyers.Check the first-week questions
From Day 0 through Day 7+, list what buyers naturally ask and confirm whether order email, order status page, tracking, refund record, review request, and repeat-purchase touch give a next step.
Keep as evidence
Keep the record location, person responsible, and remaining unknowns. The classroom exercise does not act on live orders or contact buyers.Check platform and review rules
Review official sources for notifications, returns, self-serve returns, chargeback evidence, Feed/SKU/GTIN product data, and review touches. This workflow is not legal, tax, payment, or platform-policy advice.
Keep as evidence
Keep the record location, person responsible, and remaining unknowns. The classroom exercise does not act on live orders or contact buyers.Keep the handoff and pause actions
Finish with current pressure, first evidence, this-week action, automation status, action to pause, review window, and next route. Automation status should be allowed, paused, or human follow-up only.
Keep as evidence
Keep the record location, person responsible, and remaining unknowns. The classroom exercise does not act on live orders or contact buyers.
Keep the current choices and team setup
The twelve reading choices, including the delay self-check, were previously page-only; the views group now saves them. Ten team notes also gain new persistence in two groups. These values are not restored from the old snapshot. A group JSON backs up only that group’s fields.
Choose the next piece of work
- Work to carry forward
- Move into system integration and connect orders, notifications, support logs, automation, and weekly review.
- Reading route
- Start system integration
- Work to carry forward
- Return to fulfillment and clarify timing, duties, tracking, and exception rules first.
- Reading route
- Review fulfillment
- Work to carry forward
- Return to policy pages and turn refund, return, reship, contact entry, and handling timing into promises buyers can understand before ordering.
- Reading route
- Review policies
- Work to carry forward
- Return to launch QA and use test order, email, refund, and failure paths to verify support coverage.
- Reading route
- Return to launch QA
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
Carry the remaining evidence gap forward
If you use the Store Launch Readiness Scanner, submit only the store URL, platform, stage, and confirmations the form provides. Keep support threads, screenshots, SLA, shipping, and refund evidence separately for human review. The tool does not offer file or free-text evidence uploads for those materials; compare its result with the human record.
Work it out: what full refunds would cost on four tickets
Four tickets and the cost of three resolutions (example data, US dollars). Rule: pick the compliant path from who is responsible, then compare cost inside that path; a full refund is compliant unless a chargeback is still open, and it is usually not the cheapest.
What three resolutions cost
| Item | Cost | Applies when |
|---|---|---|
| Full refund | 49 | Compliant unless a chargeback is still open |
| Reship one unit | 27 | Damage, loss in transit |
| Replace | 18 | Wrong item, wrong spec |
Who is responsible: A damaged in transit, B we shipped the wrong item, C lost in transit, D the buyer changed their mind.
Work it out before you read on. Get the total for refunding everything, the total when each ticket follows its responsible path, and the difference.
Answer key: refunding all four is 4 times 49, or 196; following responsibility gives reship 27 for A, replace 18 for B, reship 27 for C and refund 49 for D, which totals 121. The difference is 75, about one and a half refunds. D has to be refunded, because nothing on our side caused it, so reshipping or replacing would not be compliant: the saving comes from turning the three we own into reship or replace, not from refunding less. The counter-intuitive part is that a reship looks more generous than a refund, yet a refund carries both the goods and the shipping while a reship costs 27.
Common questions
- When do I actually need to work through customer service and post-purchase operations?
- Use this workflow when early orders start creating shipping delays, refunds, damaged or wrong items, low reviews, or repeat-purchase touches. The goal is not more process; it is a clear first-response SLA, evidence list, handling boundary, human-review condition, and write-back location for each case type.
- How ready should the support inbox and return entry be before launch?
- Buyers should know where to contact you, when a human will reply, where the return or exchange entry is, what evidence is needed, and when the next update will arrive. A complex helpdesk can wait, but support entry, working hours, first-response SLA, and record location cannot.
- Should my Shopify support SLA be 24 hours or shorter?
- A new store can start with first response within 24 hours on a business day for normal questions, while refunds, damaged or wrong items, chargeback risk, and public low reviews need a shorter human-review window. The number matters less than giving the next update time and timeout boundary in every reply. These numbers are staffing examples. Define the time zone, business hours, and person responsible; they are not legal deadlines or refund-receipt guarantees.
- What SLA should I set for refunds, exchanges, and reships?
- You can set one business day for review after evidence arrives, 48 hours for damaged or wrong-item resolution, and same-day human review for chargeback risk or public low reviews. Each SLA should carry order records, policy version, amount boundary, or stock boundary. These numbers are staffing examples. Define the time zone, business hours, and person responsible; they are not legal deadlines or refund-receipt guarantees.
- Can I send review requests or repeat-purchase discounts while a support case is still open?
- Keep unresolved refunds, delays, damage, wrong-item cases, or disputes with a person and pause promotions and review reminders. Use objective open-case criteria and resume consistently after completion. Do not permanently exclude expected criticism or tie a refund to review removal.
- Why can Feed, SKU, GTIN, or inventory errors become support issues?
- Buyers care whether the product page, ad, order, and delivered product match. Feed inventory, SKU naming, GTIN, price, or image drift can create complaints about wrong items, stockouts, price mismatch, or ads showing in-stock products that the store cannot ship, so support records need a product-data write-back path.