CASEKIT
Support guide

Zendesk macros for ecommerce support teams

Useful Zendesk macro starters for ecommerce teams. Keep the public reply separate from internal investigation notes, map placeholders deliberately and inspect every action before applying a macro.

Updated 3 October 2026 · CaseKit team

Create a macro without hidden side effects

Zendesk macros are manually applied responses or actions and can change ticket fields as well as add a comment. Review all configured actions, including assignee, tags and status, before reuse. Follow the official macro guide for current permissions and setup.

Use clear folders and conditions

Name macros by category and stage, for example Shipping / Missing tracking / Review or Refund / Provider confirmed. Keep internal notes private. A customer-facing comment should not contain risk scores, warehouse disputes or another customer’s order facts. Test the comment visibility and recipient on a synthetic ticket before sharing a macro.

Map the editing placeholders

The single-brace fields below are manual editing prompts, not working Zendesk variables. Replace them or map them to documented ticket fields. Zendesk has its own placeholder syntax and rules; a missing value can yield blank text. Check the official placeholder guide and preview the populated reply.

Where the order facts come from

Confirm Shopify facts in the correct Shopify order, or WooCommerce facts in the correct WordPress order. CaseKit can help prepare a reviewed draft in those platforms; it does not provide a Zendesk integration or automatically synchronise Zendesk fields. Copy only the relevant information yourself. CaseKit is independent of Zendesk.

Copy-paste starters

Replace every placeholder, check the condition above each reply and remove any action or estimate that is not verified. These templates do not send messages or perform order actions.

Shipping / Missing tracking / Review

Use when: the order match is verified but shipment evidence is unavailable.

Hi {first_name},

I checked order {order_number}, but I do not yet have recorded tracking information to share.

I will check with {responsible_team} and update you by {next_update_date}.

Best,
{agent_name}

Return / Request received

Use when: eligibility is still under review.

Hi {first_name},

I received your return request for {item}. Please confirm {minimum_needed_detail}.

I will review the applicable policy and explain the available next steps by {next_update_date}.

Best,
{agent_name}

Refund / Provider confirmed

Use when: the provider’s successful refund record is verified.

Hi {first_name},

The payment record confirms a refund of {amount_and_currency} for order {order_number} on {date}.
{verified_provider_estimate}

Please reply if you need help checking the refund.

Best,
{agent_name}

Internal / Investigation handoff

Use when: the comment is configured as a private internal note and access is appropriate.

Order reference: {order_number}
Customer-reported issue: {brief_summary}
Verified facts and source: {facts}
Unknown facts: {unknowns}
Action requested from: {owner}
Next update due: {date}
Financial action approval: {status_or_not_applicable}

Primary sources

Checked 3 October 2026. Verify current platform instructions before taking an action.

Related guides