Open any store’s inbox and you will see the same messages arriving in slightly different words. Where is my order? Can I change my address? How do I return this? Does it come in blue? A support person writes the same replies over and over, retyping, searching old tickets for a good phrasing, forgetting a detail, sometimes contradicting a colleague. Macros, also called canned responses, saved replies or templates, turn that repetition into a library. Done well, they make replies faster, more accurate and more consistent. Done badly, they make customers feel processed.
This guide gives you twelve macros that cover most of the traffic in a typical store, with the variables each needs, the tone rules that keep them human and a process for keeping them accurate. It also covers when to avoid a macro altogether. The macros here are the human-written foundation that an assistant or chatbot can later draw on, as described in AI chatbots for ecommerce customer service, and they support the refund and returns thinking in refund rules to automate.
Principles for macros that do not sound canned
- One situation per macro. A macro that tries to cover every delay or every return will be wrong for most of them.
- Variables, not blanks. Insert name, order number, item, date and tracking link automatically; a reply with a missing variable looks careless.
- A personal first line. Add one sentence that shows you read the message, such as acknowledging the detail they gave.
- Say what happens next. Every macro should end with the next step and when it will happen.
- Plain language. Short sentences, no jargon, no corporate phrases.
- Match the brand voice. If your site is playful, the macros should be warm, not stiff.
- Keep it short. Most macros can be under a hundred words.
The twelve macros
1. Order status
2. Delay apology
3. Address change
4. Cancellation
5. Start a return
6. Refund timing
7. Damaged item
8. Wrong item
9. Sizing and fit
10. Discount code problem
11. Payment problem
12. No confirmation email
Variables worth having
| Variable | What it fills in | Source |
|---|---|---|
| first_name | The customer’s first name | Customer record, with a fallback such as there |
| order_number, order_date, amount | Order details | Order record |
| item | The product name | Line items |
| ship_date, carrier, tracking_link, tracking_status, eta | Shipping details | Fulfilment and carrier data |
| window, refund_days, bank_days | Policy numbers | A single policy table, so that changes update every macro |
| return_link, size_guide | Useful links | Your site |
The policy numbers deserve special care. If the return window is thirty days, it should live in one place and flow into every macro that mentions it. Otherwise a policy change leaves a trail of out-of-date replies, which is the commonest reason customers receive contradictory answers.
When not to use a macro
- An angry or upset customer. A template feels dismissive; write a short personal reply.
- Complaints about safety, health or legal matters. Escalate to the right person.
- High-value customers and high-value orders. A personal touch is worth the minutes.
- Anything with several issues in one message. Answer each, in your own words.
- Cases outside policy. Decide as a person; see the three zones in our refund rules guide.
- Repeat contact on the same issue. If the customer is writing a third time, a template makes it worse.
Keep the library healthy
| Habit | How | Frequency |
|---|---|---|
| Owner and version | One person owns the library; changes are dated | Always |
| Policy sync | Update macros whenever a policy changes | On change |
| Link check | Test every link and variable | Monthly |
| Usage review | See which macros are used and which are edited most | Quarterly |
| Tone read-through | Read each macro aloud for stiffness | Quarterly |
| Retire and merge | Remove duplicates and unused macros | Quarterly |
The usage review is a source of insight. A macro that agents edit heavily every time is a macro that does not fit the situation, and the edits show what it should say. A topic that has no macro but appears in many tickets is a candidate for a new one, and possibly for a fix elsewhere: a confusing page, an unclear policy or a missing notification.
Macros as a foundation for automation
A tidy macro library is the best preparation for automation. The same replies, with the same variables and policies, can be used by a support assistant that drafts responses for approval, or by an automatic message that goes out when an order is delayed. Writing them once, carefully, saves rewriting them for every tool. Our customer support chatbot and order status updates services build on exactly this material, and customer support and order care automation connects macros, order data and rules into one system.
A worked example
A store answers 1,000 tickets a month. Analysis shows that 600 fall into the twelve macro topics, and that composing each from scratch takes about four minutes while a macro takes about ninety seconds, including checking the variables. The saving is about 2.5 minutes on each of 600 tickets, which is 25 hours a month. At twenty-five dollars an hour, that is about $625 a month, before counting the gain in consistency and the shorter time to first reply. Building the macros takes a day or two once, and maintaining them takes an hour a quarter. These are illustrative numbers, but they show why macros are usually the first and cheapest support improvement, well before any AI.
Sources and further reading
Figures and rules in this guide come from the primary pages below. Platform limits and prices change, so open the page before you build on a number.
- Shopify Help Center: customer notifications, what notifications customers already receive
- FTC: advertising and marketing basics, honest claims in customer communications
- Baymard Institute research library, published ecommerce usability research