BCBuyerCare AI

30-day tag export

Share the support signal, not the customer data.

BuyerCare AI only needs a recent anonymized tag, macro, or intent summary to recommend the first post-purchase workflow, held-risk tags, and whether a paid pilot clears the value threshold.

Validate the export Review data handling See stack fit
Safe export No production access
created_at Date only recent 30-day window
primary_tag Intent return_request
macro Optional policy-safe label
customer_email Remove PII not needed
Window30d

Use a recent support window so the mix reflects current volume and policy pressure.

Fields5-8

Date, tag or intent, macro, channel, status, escalation, and count are enough.

AccessNone

Paste a CSV into validation. Do not grant helpdesk, Shopify, or returns-platform access yet.

OutputScope

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

Include

Fields that make the proof useful.

  • created_atDate or week. Exact timestamps are fine, but not required.
  • tag, topic, or intentUse the column that best describes the customer request.
  • macro or reply familyOptional, but helpful for identifying draftable response lanes.
  • channel and statusEmail, chat, social, closed, open, solved, pending, or escalated.
  • human escalationTrue/false, escalation tag, or review reason if available.

Remove

Data BuyerCare does not need.

  • Customer identifiersRemove names, email addresses, phone numbers, postal addresses, and order numbers.
  • Raw conversationsSubjects or short sanitized examples are enough if tags are thin.
  • SecretsNever include passwords, API keys, tokens, private links, or admin exports.
  • Payment dataRefund amount bands are fine; card, bank, or payment details are not.
  • Medical or legal detailsUse a neutral tag such as health_question or legal_review instead.

Template

Copy this header into your export.

Download CSV template
ColumnExampleWhy it mattersRequired
created_at2026-06-01Shows recency and weekly volume shape.Yes
primary_tagreturn_requestIdentifies the first workflow candidate.Yes
macroreturn_label_stepsShows which replies may be safe to draft.No
channelemailSeparates inbox, chat, social, and phone follow-up.No
statusclosedHelps estimate resolution load and open risk.No
human_escalationfalseMarks tags that should stay reviewed.No

Helpdesk notes

Use the simplest export your team already trusts.

Gorgias, Zendesk, Freshdesk, Kustomer, Re:amaze, and similar helpdesks can usually export tickets or report tag counts. BuyerCare can use either row-level anonymized tickets or summarized counts by tag, macro, channel, and escalation.

Gorgias export guide Zendesk export guide

Submit

Turn the export into a workflow recommendation.

Once the CSV is anonymized, paste it into the validation page. BuyerCare returns the safest first workflow, which tags remain human-reviewed, and whether the economics support a paid Growth or Scale pilot.

Download template Validate tags
  1. Export a recent 30-day ticket, tag, or macro report.
  2. Remove customer identifiers, raw customer records, payment data, and secrets.
  3. Keep tag, intent, macro, channel, status, escalation, and rough volume columns.
  4. Paste the sanitized CSV into BuyerCare validation.
  5. Use the returned workflow scorecard to decide whether to start a paid pilot.