Conversationsbeginner

Export a conversation

Export up to 50 conversations at once as PDF, Markdown, or plain text — with attachments bundled into a ZIP and optional toggles for internal comments and side conversations. Built for compliance handoffs and customer-facing archiving.

3 min read

Export a conversation

Sometimes you need a conversation outside Atender — for a compliance handoff, a legal request, a customer who wants a copy of their own thread, or just an offline archive. The Export action in the conversation detail panel generates a clean, downloadable copy in the format you need.

Where to find it

Open a conversation and look at the detail panel on the right. Below the conversation metadata, click Export conversation.

This opens the Export dialog, where you choose a format and what to include before downloading.

Choose a format

Three output formats are supported:

  • PDF — Sharing with customers, legal, or anyone outside your team — fixed layout, easy to print
  • Markdown — Pasting into docs, tickets, or other internal tooling
  • Plain text — Lightweight, no formatting, easiest to search or diff

Pick whichever matches where the export is headed. PDF is selected by default since it’s the most common choice for external sharing.

Choose what to include

Below the format picker, three toggles control what goes into the export:

  • Attachments — bundles the files sent in the conversation into a ZIP alongside the exported document. On by default. If you turn this on and the export contains at least one attachment, your download comes back as a .zip instead of a bare .pdf/.md/.txt file; if there is nothing to bundle you get the bare document.
  • Internal comments — includes your team’s internal notes in the export. These are clearly marked as internal in the output. Leave this off for anything going to a customer or external party — it’s off by default for exactly that reason.
  • Side conversations — includes any side conversations attached to the thread in the export.

What the export looks like

The exported document is written for external eyes: senders are labeled with your company name and “Customer” rather than individual agent names. Agent identities are never included in the message thread of the export, in any of the three formats. The exception is the Internal comments toggle: internal notes and comments are marked [Internal note] and carry the name of the person who wrote them, so leave that toggle off if the document is to go to a customer or outside party without a manual redaction pass.

Download

Click the export/download action once you’ve picked a format and the toggles you want. Atender generates the file and your browser downloads it directly — there’s no email step or async job to wait on for a normal-sized export.

Exporting multiple conversations

The same dialog supports exporting several conversations in one pass — useful when a compliance request or customer handoff spans more than one thread. You can export up to 50 conversations at a time; each selected conversation is included in the same document (or ZIP, if attachments are included) using the format and toggles you chose.

Notes and limits

  • Exports are generated on demand — there’s no saved export history to revisit later. If you need the file again, re-run the export.
  • The 50-conversation cap applies per export. For anything larger, split the request into batches.
  • Turning on Attachments produces a ZIP whenever the export contains at least one attachment, even if you only exported a single conversation — and the bare document when it contains none, so plan for both when scripting or automating downstream handling of the file.
  • Existing conversations, including archived conversations, can be exported. A conversation owned by a contact who has been fully erased under a GDPR deletion request may no longer be exportable. If the erased contact only joined a conversation owned by someone else, that surviving conversation can still appear in exports, and what remains of the erased contact in it depends on the keep-or-delete answer recorded for that conversation on the deletion request: answered deleted, the erased contact’s messages and comments are deleted, the conversation’s subject is replaced with “[content removed on a deletion request]”, and its original subject and AI summaries are cleared; answered kept, that content stays and is still exported. If a deletion request is pending, admins should export any legally appropriate records before the grace window ends, subject to your retention and legal policies.

Tags

How ToCompliance
Back to Conversations