# Freshdesk export missing context: before and after | SourceX

Canonical: https://refer.sourcex.si/guides/complaint-to-retention-decision-missing-context
Last updated: 2026-11-04

A standalone Freshdesk export loses the decision and its cost. The ticket list export shows that a customer complained, when and how the ticket was categorized, but it does not include the full conversation or archived tickets, and nothing in it says whether the account team offered a credit, held the price or let the customer go. That reasoning sits in HubSpot property history, and the money sits in Xero, sometimes in two organizations at once.

This before-and-after comparison is part of the [complaint-to-retention-decision guide](/guides/chain-complaint-to-retention-decision), which maps the joins between Freshdesk, HubSpot and Xero. Here one case is read twice.

## Before: the ticket as a list export shows it

Illustrative. A fictional 300-person facilities services group runs a U.S. operating company and a Canadian subsidiary. A national customer with sites in both countries complains about missed service visits. An admin exports the ticket list during a support review. The row for this case reads:

| Field | Value in the ticket list export |
|---|---|
| Subject | Missed visits at several sites |
| Requester | Customer's facilities manager |
| Type and priority | Complaint, high |
| Status | Closed |
| Created and resolved | Two dates about five weeks apart |
| Group | Key accounts |

From this row a reader learns that a valued customer was unhappy and that the ticket was closed. That is all. Closed could mean the problem was fixed, the customer was compensated, or the customer left. Freshdesk's own help center says the ticket list export lets an admin pick fields and a file format but leaves out the full conversation and archived tickets, so even the complaint's own detail is missing from this file.

## After: the same case with HubSpot and Xero beside it

Restore the surrounding records, one system at a time.

**The thread, from the Freshdesk API.** The Freshdesk API lists every conversation on a ticket, with a separate path for archived tickets. Pulled that way, the case shows the escalation note that tagged the account owner and the reply offering a three-month service credit.

**The decision, from HubSpot.** On the customer's company record, the retention offer property changed to the three-month credit, dated two days after escalation. HubSpot shows past property values with the date and the source of each change, so who changed the field and when is recorded.

**The cost, from Xero.** A credit note was raised in the U.S. organization. The invoices it was meant to offset were billed by the Canadian subsidiary, which keeps its own books. Xero's credit note guidance adds a second complication: a credit raised against an invoice that is already paid stays awaiting payment until it is applied to a later invoice, so the offset can land weeks afterward on an unrelated bill.

**The outcome, from HubSpot.** Months later the renewal was recorded on the same company record. The credit worked.

## Side by side: what is lost and where it lives

| Context | Freshdesk ticket list export | Where it lives once connected |
|---|---|---|
| The complaint itself | Subject and status only | Freshdesk conversations pulled through the API, including archived tickets |
| Who decided | Not included | HubSpot company record: account owner and the source of the property change |
| What was decided | Not included | HubSpot retention offer property and its change date |
| What it cost | Not included | Xero credit note in the U.S. organization |
| What it offset | Not included | Xero invoices in the Canadian organization, under a different contact |
| Whether it worked | Not included | HubSpot renewal recorded months later |

Five of six rows are empty in the export. The fifth row is the one most likely to stay empty even after joining, because the two Xero organizations share no key for this customer. The [completeness checklist](/resources/complaint-to-retention-decision-completeness-checklist) scores that entity gap directly.

## Why the connected reading is the valuable one

The export alone supports one claim: complaints happen and tickets close. The connected history supports a much more useful one: this kind of complaint, escalated this way, led to this offer, at this cost, and the customer stayed. That decision-and-consequence middle is what public data rarely contains, as [what data is missing from AI training](/questions/what-data-is-missing-from-ai-training) explains, and it is what makes a support and account history useful for training or evaluating systems that recommend retention actions.

It also shows why the losses matter in both directions. A history full of credits with no outcomes cannot tell good offers from wasted ones. A history of outcomes with no recorded decision cannot say what caused them. The value is in the joined row, not in any one system's file.

## Confirming the context exists without opening it

A partner can test all of this from metadata. Ask whether the conversations were ever pulled through the API, which HubSpot company properties hold retention decisions and since when, how many Xero organizations bill customers, and whether credit notes carry a ticket or deal reference. The [metadata packet](/resources/complaint-to-retention-decision-metadata-packet) lays those answers out field by field. System detail is on the [Freshdesk](/systems/freshdesk) and [HubSpot](/systems/hubspot) pages, and the record type on [complaint handling records](/data-types/complaint-handling-records).

Check fit before introducing: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact with authority over every billing entity involved. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Unknown until SourceX reviews it: what customer contracts allow, what must be removed, how many cases join across both entities, and whether a buyer wants the set. Ticket text, customer names and credit amounts stay with the company throughout.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If your client's complaints can be read next to their retention decisions and credits, entity by entity, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [terms](/terms) before submitting the introduction.

## Sources

- https://support.freshdesk.com/support/solutions/articles/225158-how-do-i-export-my-tickets-from-freshdesk-
- https://developers.freshdesk.com/api/
- https://knowledge.hubspot.com/records/view-record-property-history
- https://central.xero.com/s/article/Common-scenarios-for-credit-notes-US
- https://refer.sourcex.si/terms
