How to use Help Scout conversations as chargeback evidence

Email support creates exactly the kind of record a dispute reviewer trusts: dated messages, sent from the customer’s own address, in their own words. If you use Help Scout, every one of those messages is there. The difficulty is getting them out in a form that a reviewer at a card issuer can read in a few minutes, because Help Scout has no single “export this conversation as PDF” button documented.

This guide covers what to collect, how to extract complete threads with their timestamps, and how to present them on Stripe or Braintree. Help Scout details come from its documentation: customer profiles, merging conversations, exporting reporting data, data export options, and the Inbox API’s List Conversations and List Threads endpoints. Dispute details come from Stripe’s dispute categories, best practices and Update a dispute, and Braintree’s evidence requirements (all accessed November 2026).

Why email threads make good evidence

A reviewer is trying to answer a few questions. For subscriptions:

• Did the customer know they would be charged?
• Did they use the service after the charge?
• Did they ask to cancel, and what happened?

An email thread can answer all three with the customer’s own words and a date the customer cannot easily contest, because it came from their address. That makes it stronger than an internal log or a summary you write after the fact.

On Stripe, these messages fit the customer_communication field; Stripe’s best practices recommend combining several communications into one file. Text fields such as uncategorized_text accept up to 20,000 characters (Update a dispute). On Braintree, the evidence requirements guide lists emails or other correspondence with the customer among helpful evidence; whether it goes in as text or as a file depends on the reason code.

What to collect

Item	Why it helps	Where in Help Scout
Messages after the disputed charge	Shows continued use	The customer’s conversations
Questions that mention the plan, invoice or renewal	Shows awareness of the subscription	Same
Any cancellation request and your reply	Shows what was asked and what you did	Same, often tagged
Your confirmation of cancellation or refund	Shows the resolution	Your reply in the thread
Satisfaction rating on that reply, if any	Context only	The conversation

Leave out internal notes. Help Scout threads include notes alongside customer and agent messages; notes are written for colleagues, are rarely useful to a reviewer, and can read badly out of context.

Step 1: find all the customer’s conversations

Open the customer profile: it shows the full conversation history for that contact. Two things to check:

• Permissions. Help Scout’s customers list documentation says account owners and administrators see all of a customer’s conversations, while users only see conversations in inboxes they can access. Have an admin collect the evidence, or you may miss a thread.
• Other addresses. Customers write from work and personal addresses. Search for their name and company too.

Step 2: get each thread with its timestamps

Two ways, depending on volume.

One dispute, a few conversations. Open each conversation and print it from your browser to PDF. Check that every message in the printout shows its date and time; if your browser view hides them, use the API route instead.

Regular disputes. Use the Inbox API:

1. Collect the customer’s conversation IDs from their profile, or find them with List Conversations. Pass status=all: by default the endpoint lists only active conversations, and a closed cancellation thread is exactly what you need.
2. For each conversation, call List Threads. Each thread has a type (customer, message, note, chat and others) and a createdAt.
3. Keep customer and message threads, drop note, and sort everything by createdAt.
4. Render the result as a simple document: date and time with time zone, sender, full text.

Help Scout’s reporting exports (CSV or XLSX) do not include thread contents, so they help you find conversations but cannot serve as evidence themselves.

Step 3: build one timeline

Put Help Scout messages and billing events on the same timeline:

• Signup, renewal reminders, the disputed charge, any refund.
• Each relevant message from the customer, quoted in full.
• Each relevant reply from your team.

Put all times in one time zone and say which. Help Scout and your payment provider may display different zones; a message that looks like it came before a charge in one zone can come after it in another.

Step 4: write the cover note and submit

A short paragraph in plain language, then the evidence. For example:

The customer renewed on [date]. On [date] and [date], after the renewal, they wrote to support about [feature] (messages 1 and 2, sent from the account email). They did not ask to cancel before opening the dispute. Complete conversation history attached.

Rules for the quotes:

1. Quote, don’t paraphrase. Full messages, or excerpts marked with “[…]”.
2. Don’t edit. No corrected typos, no translations without the original next to them.
3. Include what hurts. If the customer asked to cancel and the reply was late, say so. If the request was missed, accepting the dispute and fixing the process may be the right call.
4. Remove what isn’t needed. Other people’s details in forwarded emails, internal notes, anything resembling card data.

What a finished timeline looks like

A reviewer should be able to read the whole story in under a minute. A simple table at the top of the file works well, with the full messages attached below it:

Date (UTC)	Event	Source
[date]	Annual plan renewed, receipt emailed	Billing system
[date]	Customer asks how to add a teammate	Help Scout, message 1
[date]	Agent replies with instructions	Help Scout, message 2
[date]	Customer thanks the agent, asks about exports	Help Scout, message 3
[date]	Dispute opened	Stripe or Braintree

Every row that cites Help Scout points to a full quote further down. Keep the table factual: no adjectives, no conclusions. The conclusion belongs in the cover note, and it should follow obviously from the rows.

Prepare before the next one

• Tag cancellation and refund conversations when they happen, so you can find them in seconds.
• Confirm every cancellation in writing with the date it takes effect; that reply becomes your evidence.
• Merge conversations from the same customer about the same topic, so the story is in one place.
• Keep one contact per person. Duplicates split the history.

For the full dispute process on Stripe, see how to win chargebacks on Stripe.

Doing this with NoChurn

NoChurn’s Help Scout connector is read-only: it reads conversations and never changes anything in Help Scout. Conversations are matched to your customers by email; doubtful matches are suggested for you to confirm and never merged automatically. When a dispute opens on Stripe or Braintree, NoChurn gathers the evidence (cancel flow answers, emails sent, usage, and matched Help Scout messages quoted verbatim with their dates), drafts the response with AI, and submits it only after you review it. The decision stays with the card issuer. See NoChurn + Help Scout.