Ecommerce support macros and saved replies

Saved replies save time only when they make the next answer more accurate. A library of vague apologies or overconfident promises can make support faster and worse at the same time. Ecommerce teams need reusable language for predictable stages—order received, dispatched, delayed, return requested, item inspected—while leaving room to check the specific order and customer.

Freshdesk calls its reusable text “canned responses” and documents dynamic placeholders such as requester name and ticket details. Zendesk's macros can add a public reply and perform ticket actions. This distinction matters: an agent selecting what looks like a paragraph might also change the status or ownership. The team should understand what each item does.

Build the library from real demand

Sample a recent month of conversations and group them by the customer's question, not the team's department. Separate “has not dispatched” from “carrier delayed” and “tracking says delivered but missing”. Separate “request a return label” from “when will my refund arrive?”. One generic template for each broad category usually hides the exact stage and creates a second contact.

Choose the first ten or so intents by frequency and consequence. For each, write the facts the agent must verify, the action the agent must take, the customer-facing message and the failure path. Add a short internal note to the macro description so a new colleague knows when not to use it. Do not make a template for an uncertain policy until the policy owner settles it.

Use a compact reply structure

A useful ecommerce reply has four parts: acknowledge the specific issue; state the checked fact; describe the next action and owner; say when or how the customer will hear back. For example, a delayed-parcel response should identify the verified carrier event and say whether support has opened an investigation. It should not simply say “your item is on its way” when the tracking feed has not moved.

Write one version for each significant state. An item awaiting warehouse inspection needs different wording from a refund already issued. A message should not say “your refund is being processed” if the request has merely been received. Use plain UK English, short sentences and customer-facing links. Put internal policy language in an agent note, not in the reply.

Test placeholders and permissions

Dynamic fields can insert a name, order number or ticket link, but they can also be empty or wrong. Test each template against a ticket with no matched order, several orders, a different recipient email and an international address. Zendesk's documentation warns that some ticket URL placeholders may point to the agent interface rather than an end-user page. Check the rendered message before making it widely available.

Avoid sensitive personal data, full addresses and payment details in a template. Keep the minimum useful order reference and direct customers to an authenticated view when more detail is needed. Use group-level visibility for specialist replies such as refunds or disputes. A public macro should not be able to imply a decision the agent lacks authority to make.

Separate an agent shortcut from automation

An agent-selected saved reply leaves a person to check context. A rule that sends the same message automatically needs stronger conditions and a stop rule. For WISMO, require a reliable order match and current status. For a return, automatic acknowledgement is usually safer than automatic eligibility. If the customer replies that the data is wrong, stop the automated path and assign a human owner.

Where a macro also changes ticket status, test whether it closes a case prematurely. “Awaiting warehouse” and “resolved” are not equivalent. Zendesk describes macros, triggers and automations as different tools; use the one that matches the intended action instead of stacking all three on a common ticket.

Keep templates accurate

Assign a named owner and review trigger to every high-volume reply. Seasonal dispatch cut-offs, return policy changes, carrier incidents and new fulfilment partners should put relevant templates into review immediately. Track repeat contacts and “macro was unhelpful” feedback, not just usage count. If agents edit the same template heavily every time, either the wording is wrong or the intent category is too broad.

Archive duplicates. Search the library by customer language, such as “address change before dispatch”, rather than an internal code only a veteran remembers. Test a new starter's ability to find the right response and notice when it should not be used. Good macros are small, current tools for judgement—not a substitute for it.

Sources

• Freshdesk guide to canned responses and placeholders
• Zendesk lesson on macros and placeholders
• Zendesk guide to macros, triggers and automations

Product capabilities come from provider documentation. Template design and review advice are Support Sorted's editorial judgement.