Templates
Customer support macros for preorder questions
A longer, research-informed macro pack for preorder-heavy Shopify stores, combining current Zendesk and Intercom workflow guidance with recurring preorder questions pulled from public retailer help centers.
Copy block
Copy this template pack
Macro: mixed cart timing
Thanks for checking. Your order includes items with different availability timing, so shipment may follow the latest item in the order unless we confirm another arrangement. If you want us to review an earlier release for the available items, reply before dispatch and we will confirm what is possible for your order.
Macro: release-date moved
The expected ship window for this item has changed. The current estimate is [timing]. If the revised timing no longer works for you, reply with your order number and we will review the options available for your order.
Macro: address update
We can usually review address changes before the order has entered final processing. Please reply with your order number and the full updated address and we will check the current stage of the order.
In short
- Macros reduce variation best when they are paired with tags, fields, and a clear support workflow.
- Zendesk and Intercom both frame macros as repeatable actions that still need human editing, not final replies to paste without thought.
- The best preorder macros handle mixed carts, release-date movement, payment timing, address changes, and cancellation review paths.
Why preorder macros need more than canned text
Zendesk's macro documentation and Intercom's macro guidance are directionally aligned: macros are there to speed up repetitive work, standardize common actions, and reduce error. They are not there to remove judgment. That matters more in preorder support than in many other queues because the details of the order often determine the answer.
The most useful macro system for preorder-heavy stores combines three things: a short reusable answer, fields or tags that capture the order context, and a clear rule for when the ticket must escalate. Zendesk's current guidance on custom ticket fields is particularly useful here because it shows how issue-specific fields can feed reports, automations, views, and macro usage later.
- Use macros to standardize policy language.
- Use tags or ticket fields to capture the reason the customer wrote in.
- Use escalation rules when the macro depends on live order state or payment exceptions.
The core preorder macro pack
Macro: when will my preorder ship?
Thanks for reaching out. The current estimated ship window for this preorder is [timing]. This is our best confirmed estimate at the moment, not a guaranteed ship date. If the estimate changes again, we will update the order timing accordingly.
Macro: why did the date change?
The expected timing moved after the item went on sale. That can happen because of manufacturing, allocation, freight, or supplier updates. We know that is frustrating, so we are sharing the revised estimate instead of leaving the old one in place.
Macro: can I ship the in-stock items first?
Your order contains items with different availability timing. We do not automatically split mixed orders, but we can review whether an earlier release is possible for the available items. If a split shipment is possible, additional shipping charges may apply.
Macro: when do you charge?
Payment timing depends on the purchase option and the order setup for the item. If payment is due now, partial now, or later, that is shown during checkout and on the product page. If you want us to review the payment timing on your order specifically, reply with your order number.
Macro: can I cancel?
We can review that for you. Cancellation options depend on the order stage and whether any non-refundable payment terms applied when the preorder was placed. Reply with your order number and we will confirm the current status.
Macro: can I update my address?
We can often review address changes before final processing. Reply with your order number and the full updated address and we will check whether the order is still editable.
How to keep macros from sounding robotic
Intercom's support style guidance is still the right correction here: sound like a person, not a function. The macro should do the hard part of staying accurate and consistent, while the agent does the smaller human part of customizing the opening line, choosing the right amount of empathy, and removing any irrelevant sentence before sending.
- Do not stack three unrelated macros into one wall of text.
- Replace placeholders before sending, every time.
- Cut any sentence that does not help this customer on this ticket.
- Keep one canonical mixed-cart explanation so agents do not improvise different promises.
If the macro triggers a refund argument, it is too late
Macros should answer clearly enough that customers do not have to write back just to learn the next rule. If a macro keeps producing second-contact tickets, rewrite it.
Maintenance cadence for preorder-heavy teams
Zendesk's suggested macro workflow is also a useful reminder that macro performance can be measured. Shared macros build better support systems when they are reviewed monthly, retired when the policy changes, and named so agents can find the right one in seconds.
A good monthly review looks at ticket reasons, top macro usage, reopened tickets after macro use, and any mismatch between customer-facing policy pages and agent responses.
Related: preorder FAQ template for Shopify stores, how collectible stores can reduce WISMO tickets
FAQ
Should every preorder ticket receive a macro?
No. Every repetitive question should have a macro available, but some tickets still need manual review because the answer depends on the payment state, order stage, or a store exception.
Should macros include tags or actions?
Usually yes. Zendesk and Intercom both treat macros as repeatable actions, not only text snippets. Tags, assignment, and status changes are part of what makes them useful.
Sources
- Zendesk Help: Organizing and managing your macros - Current official guidance on naming, organizing, and maintaining macros.
- Zendesk Help: Adding custom ticket fields to tickets and forms - Useful for turning preorder reasons into fields that can be used in macros, reporting, and automations.
- Zendesk Help: Applying suggested macros to tickets - Useful for thinking about macro standardization and usage patterns.
- Intercom Help: Creating and managing macros - Useful for macro-as-workflow guidance rather than text-only snippets.
- Intercom Help: Our best practice guide to customer support - Useful for avoiding robotic macro tone.
- BigBadToyStore: Pre-orders - Public preorder policy inputs that inform common ticket questions.
Related resources
Keep tightening the support flow
Preorder FAQ template for Shopify stores
A longer-form preorder FAQ template for Shopify merchants, built from Shopify's current pre-order rules and public collectible-store policies so merchants can explain timing, payment, mixed carts, delays, and cancellations more clearly.
Shipping delay email templates that do not sound robotic
Longer, more useful shipping delay email templates for Shopify stores, informed by current Shopify pre-order obligations, Baymard's research on delivery-date clarity, and customer-support writing guidance from Intercom.