How to Export a WhatsApp Conversation for a Customer Data Request, a Dispute or an Audit

To export a WhatsApp conversation from a business inbox, open the conversation, choose the scope, the number of messages and the file format, and download the file when it is ready. The reasons are usually practical: a customer asks for a copy of what you hold about them, a payment or delivery dispute needs the chat as evidence, an auditor asks how you collected consent, or a manager wants to review a complaint away from the screen.

This guide covers what to decide before you export, how to export a conversation in MonoChat, what belongs in the file and what does not, and what the GDPR asks of you when the export answers a customer’s request.

When a business needs to export a conversation

Situation	What the file is for	Internal notes in the file?
Customer asks for a copy of their data	Sent to the customer	No
Payment or delivery dispute	Evidence for you, your payment provider or a marketplace	Usually no
Complaint or quality review	Read by a manager	Yes
Consent or compliance audit	Shows when and how the customer opted in	Yes, if the audit covers handling
Moving to another system	Imported elsewhere	Decide per field

Decide the audience first. The same conversation is a different file for a customer, a payment provider and an internal reviewer.

Export a conversation in MonoChat

1. Open the conversation in the team inbox.
2. In the session header, open the actions menu and choose Export. The Export Conversation drawer opens.
3. Choose the Scope: this session, or all sessions of this customer.
4. Choose the Range: last 10 messages, last 100, last 1000 or all messages.
5. Choose the Format: JSON, Markdown, CSV or Excel.
6. Decide on Include internal notes and system events. Assignment, flow and AI agent notices count as internal notes too, and they are marked [Internal note] in the file.
7. Click Export. The file is built in the background and appears under Exported Files in the same drawer. When it is ready, use the download button. The download link is valid for 7 days.

Only the sessions you can see in your own session list are exported, so your team inbox roles and permissions decide who can produce which file. Give export rights to the people who handle data requests and disputes, not to every agent.

Customer lists work the same way from the CRM: the Export button downloads the table as Excel or CSV, and the files appear in the Exported Files section, where you can download them or send them by email.

Which scope, range and format to choose

• A customer’s request for their data: all sessions of that customer and all messages, with internal notes off. A reply that leaves out part of the conversation needs a reason you can state.
• A dispute: the sessions around the order or payment, and the range that covers it. A narrow file is easier to read, but do not cut a conversation in the middle of a promise.
• A format for a person: Markdown reads like a transcript, and Excel suits a case file where someone adds columns.
• A format for a system: JSON or CSV, which another tool can read.

What to keep out of the file

• Internal notes and system events, unless the audience is internal. A note such as “customer is difficult” does not belong in a copy that goes to the customer.
• Other people’s data. A conversation with one customer should not carry another customer’s details in a forwarded message or a note. Read the file before you send it.
• Card numbers and ID documents. WhatsApp’s business policy says not to share or ask for full-length payment card numbers in the chat, so a clean conversation does not contain them. If a customer sent one anyway, handle it as a data protection matter before it leaves the building.

What the GDPR asks when the export answers a request

This is general information, not legal advice, and other countries have their own rules. Under the GDPR:

• A person has the right to get confirmation that you process their personal data, and a copy of it (Article 15).
• If the request is made by electronic means, you provide the information in a common electronic format unless the person asks for something else (Article 15).
• You must act without undue delay and within one month of receiving the request. For complex or numerous requests the period can be extended by up to two further months, and you must tell the person within the first month (Article 12).

A conversation export covers the messages. A full response may also include the customer’s profile, tags and anything else you hold about them in the CRM, and the purposes and recipients the law asks you to describe. Our AI chatbot privacy checklist covers mapping where customer data goes, which makes a request easier to answer.

A simple process for data requests and disputes

1. Log the request with the date you received it and who owns it.
2. Check who is asking. Reply only to the number or address the customer used before, or ask for confirmation.
3. Export with the scope and range above, internal notes off.
4. Read the file for other people’s data and for anything that should not leave.
5. Send it the way the request came in, and record the date.
6. Keep the export link short-lived. The download link in MonoChat is valid for 7 days; do not forward it to people who do not need it.

Make the export easy: keep good records

An export is only as good as the conversation behind it.

• Record consent where it happens. The opt-in line, the date and the channel should be findable. See our WhatsApp opt-in guide.
• Keep conversations in one place. When several people answer from one number, the shared team inbox keeps the whole conversation together. If your history lives in the WhatsApp Business app, see how to bring the chat history into MonoChat.
• Use tags for the outcome. A “dispute” or “data request” tag finds the conversations later.

How this works in MonoChat

MonoChat brings WhatsApp, Instagram, Facebook, TikTok, Telegram and web chat conversations into one team inbox. Any session can be exported from its actions menu in JSON, Markdown, CSV or Excel, with or without internal notes, and the file is built in the background so a long conversation does not hold up your work. Access follows your roles and permissions, and you can read about our approach on the security page.

Start on the free Basic plan at app.monochat.ai, and see the pricing page for larger teams.

Sources

• MonoChat help center: Chat screen, Exporting a conversation
• MonoChat help center: CRM overview, Export
• GDPR Article 15: Right of access by the data subject
• GDPR Article 12: Transparent information, communication and modalities
• WhatsApp Business Messaging Policy