Shopify customer support
Draft Shopify support replies from your own policy and order facts
Paste the customer's message, the order details and the policy that applies. ZeroTwo drafts the reply, keeps a fallback resolution ready and marks what it was not told. You check the facts and send it yourself.
A drafting workflow for merchants who answer tickets themselves. It is not a helpdesk and does not read your store.
Anatomy of a drafted reply
- AcknowledgeTone
Names the problem in the customer's terms, without excuses.
- State the factsYour order data
Dates, carrier status and amounts exactly as you pasted them.
- Offer the pathYour policy
Exchange, replacement, reship or refund, whichever your policy allows.
- Give a timelineYou confirm
Left as a placeholder until you supply a date you can keep.
- Say what happens nextYour policy
Who writes again, by when, and what the fallback is.
A drafting workflow, not a helpdesk integration
The workflow runs on what you paste in. ZeroTwo writes; the facts, the policy and the send button stay with you. Check the connectors page for what ZeroTwo can connect to.
You provide
- The customer's message, pasted as written
- Order facts from your Shopify admin: dates, items, amounts, carrier and tracking status
- The part of your policy that applies, in your own words
ZeroTwo drafts
- A reply that uses only the facts you supplied
- A first-choice resolution and a fallback, as your policy defines them
- Bracketed placeholders for anything it was not given
You decide
- Whether every date, amount and promise is true
- Whether this ticket needs an exception or a person
- Sending the reply from your own helpdesk or inbox
One ticket, start to finish
An illustrative example with a fictional customer and store. It shows the shape of the work, not a customer result, and every bracket is something you would fill in from your records.
What you paste
- Customer message
- “My order was due last week and tracking has not moved in four days. Can you tell me what is going on? If it is lost, I would like my money back.”
- Order facts from your admin
- Placed [date], shipped [date] with [carrier], last scan [date, location], order total [amount].
- Your policy, as you would write it
- Lost in transit: reship or refund after [N] business days with no tracking movement.
What the draft must not fill in
- A new delivery date the carrier has not confirmed
- Whether your policy says reship or refund at this point
- Whether a carrier trace has been opened
The draft you would review
Hi [name],
I am sorry the order has gone quiet. That is frustrating when you were expecting it last week. Here is what I can see: it shipped on [ship date] with [carrier], and the last tracking scan was on [date] at [location].
I am contacting [carrier] today to ask for a status. If there is still no movement by [date from policy], I will [reship / refund, per policy] without you needing to ask again. Either way, I will write to you by [date].
[Sign-off]
- Order number and name match the ticket
- Every date comes from the carrier or the order record
- The resolution matches your written policy
- No new promise that was not in the policy
What to supply, and when to hand it to a person
Exchange-first is a policy choice, not a default. For each common exception, here is what the draft needs from you and where a template stops being the right tool.
| Exception | Facts to paste in | Paths to define in your policy | Hand to a person when |
|---|---|---|---|
| Refund request | Order and delivery dates, item, return window in your policy, whether the item has come back | Exchange or store credit first, full refund as the fallback, but only if your policy allows each. Say which to lead with. | Outside the window with a credible reason; high-value order; the customer cites a legal right |
| Delayed shipment | Carrier name, last tracking scan, original estimate, any carrier-confirmed new date | Report the carrier's own status; reship or refund when your policy says a parcel counts as lost. | Tracking shows returned or lost; the customer has already written twice; a carrier claim is needed |
| Wrong item received | Order line versus what the customer says arrived, a photo if you ask for one, stock of the right item | Send the correct item, with a prepaid return label or keep-it, or refund. | The same mix-up shows up on several orders; a high-value item |
| Damaged on arrival | Photos, packaging notes, your carrier's claim window | Replace, refund, or partial refund. Ask for a photo only if your policy requires one. | A carrier claim is needed; repeated damage on the same product |
| Cancellation | Order status (unfulfilled or fulfilled), whether a label is already printed | Cancel if not shipped. If shipped, explain your return or refuse-delivery steps. | Personalised or made-to-order items; a fraud flag on the order |
| Chargeback threat | Dispute status, full order and message history | A calm, factual reply with one concrete resolution. No arguing, no new promises. | Always. A person owns anything that touches a payment dispute. |
Editorial guidance for a small store, not legal advice. Your own policy and your carrier's terms decide the real answer.
From one ticket to a playbook you trust
A playbook is only as good as the replies you approved. Save the ones you actually sent, not the first drafts.
Paste the ticket and the facts
Put the customer's message, the order facts and the relevant policy in one message. Tell ZeroTwo which resolution to lead with and to use a bracketed placeholder for anything missing.
Read the draft against your records
Check each date, amount and carrier detail against the order and tracking page. Fix or remove anything the draft assumed, and decide whether the ticket is an exception.
Edit and send from your own tools
ZeroTwo does not send anything to customers. Copy the approved reply into your helpdesk or inbox and send it there.
Save only approved replies as templates
Keep the version you actually sent, with its policy condition written beside it, in a Project. Recurring ticket patterns are evidence of what your help centre is missing; the support-ticket deflection audit is the next step for that.
Support ticket deflection audit
Starter prompts that ask for placeholders, not guesses
Each one opens in ZeroTwo with the prompt filled in. Add your ticket, order facts and policy before you run it.
Refund request
Draft a reply to the refund request below using the return policy I paste after it. Lead with an exchange or store credit only if the policy allows it, include a full-refund fallback, and put any date or amount I have not given you in [brackets] instead of guessing.
Open in ZeroTwoDelayed shipment
Draft a reply for a customer whose order has not moved in tracking. Use only the carrier status I paste, do not promise a delivery date, and state what I will do if there is still no movement by [date per policy].
Open in ZeroTwoWrong item
Draft a reply for a customer who received the wrong item. Apologise once, offer the correct item or a refund as my policy states, explain the return steps, and list the facts I still need to check before sending.
Open in ZeroTwoDamaged on arrival
Draft a reply for a customer whose item arrived damaged. Ask for a photo only if my policy says so, offer replacement or refund as the policy allows, and note which carrier claim deadline I need to check.
Open in ZeroTwoUpset customer, chargeback mentioned
Write a calm, factual reply to a customer who mentions a chargeback. Acknowledge the problem, offer one concrete resolution from my policy, make no new promises, and add a note for me on what to document before responding to any dispute.
Open in ZeroTwoPlain-English policy summary
Rewrite my return policy below as a short customer-facing summary I can reuse in replies. Keep every condition and deadline from the original and flag anything ambiguous for me to clarify.
Open in ZeroTwo
Questions merchants ask first
Does ZeroTwo connect to my Shopify store?
The workflow on this page does not depend on a store connection. You paste or attach the order details you want the reply to use. See the connectors page for the current list of integrations.
Can ZeroTwo send the replies to customers?
No. It writes drafts. You review them and send them from your own helpdesk or email, so nothing reaches a customer without you.
Will it make up order details or refund promises?
It drafts from what you give it, but language models can still get things wrong. Ask it to leave a bracketed placeholder for anything missing, and check every date, amount and promise against your records before sending.
Is exchange-first the right default for my store?
That is a policy decision, not a built-in setting. If your policy is refund-first, or you offer a refund on request, say so in the prompt and the draft will follow it.
How much time will this save me?
It depends on your queue. To find out, time five tickets you answer by hand, then time five of the same kind with a draft and your review. Compare the two before you rely on any number.
What does ZeroTwo cost?
There is a Free plan with 100 free credits to start plus 20 bonus credits every day you log in, and no card required. Plus is $14.99/month and Pro is $29.99/month ($26.99/month billed annually). The pricing page lists what each plan includes.
Around the support queue
- Shopify returns and exchanges
Beyond one reply: write the returns and exchange process the replies point customers to.
- Shopify fulfillment operations
Many delay and wrong-item tickets start in fulfillment. Write the checklists that prevent them.
- Shopify performance reporting
Turn support volume and refund reasons you track into a regular report.
- Support ticket deflection audit
Once the same tickets keep coming back, audit which ones a better help page could answer.