Skip to content

Customer support

Find and export
your Gorgias data.

Gorgias ticket exports and analytics message exports contain different parts of the support history. Start with ticket quantities, then check whether the desired replies and notes are available through the chosen route.

Report in
Records
Category
Customer support
Last checked

Find your Gorgias data size

  1. Use an account owner, admin or lead with ticket-export access.
  2. Open an Inbox view covering the tickets in scope.
  3. Select the relevant tickets and choose Export tickets from the action menu.
  4. Count the rows in the emailed CSV, recording the view filters and dates.
An Inbox view can exclude older or differently assigned tickets. Describe the view scope beside the count.

What to include in your data inventory

Report in records, giving ticket count, dates and channels. Describe public messages and identify excluded internal notes or media.

Use the earliest included ticket date and the agents represented. Separate any wider support-provided export from the standard report.

Add the dates covered and the people who use this software. Label estimates and describe how you calculated them.

Export your Gorgias history

  1. Export the Inbox ticket metadata for the agreed scope.
  2. For message text, open an eligible Analytics metric drill-down.
  3. Choose Export → Export with message content and collect the resulting file.
  4. Ask Gorgias support about a broader historical collection when the built-in message export is too limited.

Gorgias documents message-content exports for the most recent 30 days of the selected period, up to 100,000 tickets.

That route includes public messages, with internal notes, ticket events and certain social content excluded. Check coverage before planning delivery.

Why Gorgias data has value for AI training

Commerce support threads can connect an order issue with the information requested and action taken.

Channel and ticket context helps explain how agents handle returns, delivery questions and other customer requests.

What stays private

Select the stores, tickets and fields in scope, reviewing customer identifiers and order details.

Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.

Common questions about Gorgias data

Does Export tickets include all message text?

Use the appropriate message-content route and check its period and exclusions.

Can the message export cover years at once?

The documented drill-down message export has a recent-period limit. Ask support about a broader collection.

Are internal notes included?

Gorgias lists internal notes among the exclusions of the documented export.

Why is our count lower than expected?

Review the Inbox view's filters, dates and ticket-selection scope.

Your data inventory

Add your numbers to the picture.

Enter the quantities and years covered in your data inventory, then share it with your Telegraph Lab contact. We’ll review the material and discuss the next step with you.

Discuss your data