Gorgias export guide

Turn Gorgias tags and macros into a safe workflow proof.

BuyerCare can validate the first automation lane from a 30-day Gorgias tag, macro, channel, and escalation summary. Keep customer data out; send the support pattern instead.

Validate Gorgias tags Gorgias automation Data handling Zendesk guide

tags Required return_request

macro Helpful return_label_steps

channel Optional email, chat, social

customer Remove name, email, order id

Window30d

Use the most recent month so returns, delivery, and subscription pressure is current.

RowsTags

Row-level anonymized tickets or summarized counts by tag and macro both work.

RiskHold

Refund, credit, VIP, chargeback, legal, and unclear-identity tags should stay human-reviewed.

Next stepProof

BuyerCare returns the first Gorgias workflow, held tags, and pilot economics.

Include

Gorgias fields that make the proof useful.

created_at or weekEnough date context to understand recent volume and spikes.
tagsThe best signal for returns, WISMO, damaged items, subscription changes, and policy questions.
macro or reply familyShows which replies already have approved language and which need human review.
channelEmail, chat, social, contact form, or marketplace messages if available.
assignee, team, or escalationUse broad team labels only; this helps identify review lanes.

Remove

Keep buyer data out of the first proof.

Customer identifiersRemove names, emails, phone numbers, shipping addresses, and order numbers.
Raw conversationsDo not paste full threads unless they are sanitized examples.
Private linksRemove admin URLs, attachment links, tokens, and internal notes with sensitive details.
Payment detailsRefund bands are fine; card, bank, and payment processor data are not needed.
CredentialsNever grant Gorgias access or share API keys before the paid pilot scope is approved.

Template

Use this CSV shape if the native export is noisy.

Download Gorgias CSV

ColumnExamplePurposeRequired

created_at2026-06-01Recent volume shape.Yes

primary_tagreturn_requestWorkflow candidate.Yes

macroreturn_label_stepsDraft-ready response family.No

channelchatSeparates inbox and live-support work.No

statusclosedShows unresolved queue pressure.No

human_escalationtrueMarks tags that should stay reviewed.No

Gorgias proof path

Validate the workflow before connecting the helpdesk.

BuyerCare uses the anonymized tag mix to recommend the first draft-first lane, usually return and exchange intake, verified order-status replies, damaged-item triage, or subscription support. Production Gorgias access waits until the paid pilot has an approved owner, scope, and guardrails.

Good first lanehigh-volume tags with clear policy language and low refund authority
Hold lanerefund approvals, credits, chargebacks, legal threats, VIPs, and identity uncertainty
Pilot triggervalidated monthly value above the Growth or Scale plan fee

Submit

Paste the anonymized Gorgias CSV into validation.

Use the generic validation form once the CSV is stripped of customer identifiers. If you only have counts by tag or macro, paste those counts; BuyerCare can still score the first workflow.

Download template Validate Gorgias tags

Export or summarize the last 30 days of Gorgias tags and macros.
Remove customer identifiers, order IDs, raw conversations, secrets, and payment details.
Keep tag, macro, channel, status, escalation, and rough volume columns.
Paste the sanitized CSV into BuyerCare validation.
Use the returned scorecard to decide whether to start a paid Gorgias pilot.