Can Shopify Sidekick write your Zendesk or Gorgias macros for you? Yes, for the text — no, for the setup. Sidekick can draft accurate, policy-based macro copy in seconds, but it cannot open your helpdesk, create the macro, or send it to a customer. Every macro it writes still needs a human to paste it in. Here’s how to brief it so the draft comes out usable on the first try.
Why this matters
Most merchants either write macros from scratch (slow, and easy to leave a policy detail out) or copy generic templates off a blog (fast, but they don’t match your actual return window, shipping times, or exchange rules). Sidekick sits in between: it writes fast, but only if you feed it your real policy numbers instead of letting it guess.
The mistake to avoid is asking Sidekick something vague like “write a return macro for me.” Without your actual numbers, it will either invent plausible-sounding policy details or write something so generic it needs a full rewrite anyway. Neither saves you time.
What Sidekick can and can’t do here
Can do:
- Draft macro text for common support scenarios (returns, order status, damaged items, shipping delays, exchanges) using the policy details you give it.
- Keep each macro within a word limit and end with a clear next step for the customer.
- Insert bracketed placeholders (like
[ORDER_NUMBER]) anywhere order-specific detail belongs.
Can’t do:
- Read your actual support tickets.
- Reply to a customer, in Zendesk, Gorgias, or anywhere else.
- Create, edit, or publish a macro inside your helpdesk.
- Know when a macro has gone stale because your policy changed.
Step-by-step: briefing Sidekick for support macros
- Gather your real policy numbers first. Return window in days, who pays return shipping, standard processing + transit time, your exchange policy, and your damaged/wrong-item process. Sidekick’s output is only as accurate as what you feed it — don’t leave a field for it to guess.
- Ask for macros scenario by scenario, not one generic block. Request separate drafts for: return within window, return outside window, order status inquiry, damaged/wrong item, shipping delay, and exchange request. Each scenario needs its own tone and next step.
- Set a hard word limit. Ask for something like “under 120 words, warm but efficient tone” so the output pastes in clean instead of needing to be trimmed.
- Check the placeholders before you paste. Sidekick writes plain-text placeholders like
[TRACKING_LINK], not your helpdesk’s live merge-field syntax. You’ll need to swap these for Gorgias’s `` style tags or Zendesk’s own variable format. - Paste into your helpdesk manually. In Zendesk: Admin → Macros → Add macro. In Gorgias: Settings → Macros → New macro. Sidekick’s job ends at the draft; this step is on you.
- Set a reminder to re-brief when policy changes. Any time your return window, shipping times, or exchange rules change, re-run the brief with the new numbers and manually update the macro. Sidekick won’t flag that an old macro is now wrong.
A quick example of what “good input” looks like
Instead of “write me a return macro,” give Sidekick something like:
Return window: 30 days from delivery. Condition: unused, tags attached. Return shipping: customer pays unless item arrived damaged. Draft a macro for a return request within this window, under 120 words, with
[ORDER_NUMBER]and[RETURN_LABEL_LINK]as placeholders.
That level of detail is the difference between a macro you paste as-is and one you end up rewriting anyway.
Where this pairs well
If you’re also documenting the process behind your support workflow — not just the customer-facing macro — the same “give Sidekick real detail, paste the output yourself” approach works for writing an SOP to drop into Notion. Same limitation applies: Sidekick can write the structured text, but it can’t touch Notion directly either.
Bottom line
Sidekick is a fast first-draft writer for support macros, not a helpdesk integration. Brief it with your real policy numbers, ask for one scenario at a time, and budget five minutes to map placeholders and paste the results in yourself. That’s the realistic workflow — and it’s still a lot faster than writing six macros from a blank page.