Chat transcript· Support operations
Chat Transcript — The Written Record of a Conversation
Quick answer: A chat transcript is the full text of a chat conversation, kept after it ends. It serves three readers: the customer, who may want proof of what they were told; the support team, who need the history when the customer comes back; and whoever reviews quality (see chat quality assurance) or answers a data request later. Because customers type names, emails, order numbers and sometimes things they should not, a transcript is personal data, and how long you keep it is a decision, not a default.
What a transcript usually contains
| Part | Usually included | Watch for |
|---|---|---|
| Customer messages | Yes | Personal details the customer volunteered |
| Bot and agent replies | Yes, with sender names | Bot greetings can be missing; Zendesk notes the AI agent greeting may not appear in downloads |
| Timestamps | Yes | Time zone of the export |
| Attachments and images | Often as links | Links may stop working if files are deleted |
| Internal notes | Usually not in customer copies | Intercom excludes internal notes from transcripts it exports |
| Ratings, tags, routing data | Sometimes, in reports or API data | Often in a separate export, not in the text transcript |
The exact contents depend on the platform and the export method. A transcript emailed to a customer is usually the plain conversation; an API export usually carries more metadata.
How customers get a copy
- Download from the widget. Zendesk messaging lets admins turn on "End users can download a transcript of the conversation" for the Web Widget and supported mobile SDKs. Intercom's Messenger offers a "Download transcript" option that produces a .txt file.
- By email in the ticket. In Zendesk, when transcript visibility is set to public reply (the default), the transcript is added to the ticket and included in email notifications to the requester. Set it to internal note and only agents see it.
- On request in the chat. In Zendesk's legacy Live Chat, a customer can choose "Email transcript" from the chat window; the email is sent after the chat ends.
- From an agent. In LiveChat, an agent can open a chat in Archives and use "Send transcript" to email a copy to any address.
How teams keep and export transcripts
- LiveChat documents four routes: send a single transcript from Archives, forward every transcript automatically to company addresses with "Transcript forwarding" (past chats are not forwarded), pull single or bulk transcripts through its API, or fire a webhook when a chat ends and handle the payload on your own server. LiveChat does not name a file format for downloads in that article.
- Zendesk keeps messaging transcripts on the ticket, either as a public reply or an internal note; the public option also makes the conversation available through ticket APIs. Zendesk lists transcript visibility for all Suite plans. See Zendesk.
- Intercom exports a single conversation or a selected batch as text or PDF from the Inbox (its article gives roughly 200 to 300 conversations per bulk operation), and points larger volumes to the Conversations API. Its CSV and report exports carry metadata, not message content. See our Intercom review.
Why a transcript is personal data
A transcript names or identifies the customer and records what they said, so privacy law applies to it. GDPR Article 5 requires personal data to be limited to what is necessary and kept in identifiable form for no longer than necessary for its purpose. In California, the CCPA requires a business to tell consumers how long it intends to keep each category of personal information, or the criteria used to decide, and not to keep it longer than reasonably necessary. Neither text gives a number of days for chat transcripts; some regulated industries have their own record-keeping rules, which is a question for a lawyer, not a widget setting. Practical consequences: decide a retention period, mask card numbers and similar data with PII redaction, and make sure transcripts can be found when someone files a data subject access request.
Transcript, summary, log: the difference
A transcript is the full conversation. A conversation summary is a short version written for the next agent. An audit log records who did what in the system, such as who exported or deleted a transcript. Teams usually need all three, and they have different readers and retention needs.
FAQ
What is a chat transcript? The written record of a chat or messaging conversation, with every message from the customer, bot and agents in order, usually with timestamps.
Can customers get a copy of their chat transcript? On many platforms, yes: by downloading it from the chat widget, receiving it in a ticket email, or asking an agent to send it. It depends on the settings the business turns on.
How do I export chat transcripts? It depends on the platform. LiveChat offers single sends, automatic forwarding, an API and webhooks; Zendesk keeps transcripts on tickets; Intercom exports single or batched conversations as text or PDF and uses its API for larger volumes.
What does a chatbot conversation transcript include? The customer's messages, the bot's replies, any agent replies after a human handoff, and timestamps. Internal notes and bot greetings are not always included.
How long should a business keep chat transcripts? No general law sets one number. GDPR and the CCPA say no longer than necessary for the purpose, and the CCPA requires you to disclose the period. Set a period that matches why you keep them, and check sector rules with a lawyer. See data retention policy.
Are chat transcripts private? They contain personal data, so treat them like any customer record: limit who can export them, redact sensitive details and delete them on schedule.
Related terms
- Live chat — the channel most transcripts come from.
- Chat queue — the wait before an agent joins, which transcript timestamps make visible.
- Conversation summarization — the short version written for the next agent.
- Data retention policy — how long transcripts are kept.
- PII redaction — masking sensitive details before storage or reuse.
- Data subject access request — the request that can require you to find and hand over a customer's transcripts.
- Audit log — the record of who accessed or exported them.
Sources
- LiveChat, How to get chat transcripts — livechat.com/help/how-to-get-chat-transcripts/, read 13 November 2026. Source of sending from Archives, Transcript forwarding and its no-backfill note, API export and the chat-ends webhook.
- Zendesk, How can I send chat transcripts manually or automatically? — support.zendesk.com/hc/en-us/articles/4408833687450, read 13 November 2026. Source of customer downloads in messaging and the legacy Live Chat email transcript options.
- Zendesk, Managing messaging transcript visibility — support.zendesk.com/hc/en-us/articles/4408818625690, read 13 November 2026. Source of public reply versus internal note, the download setting, the plan list and the missing AI agent greeting.
- Intercom, Export your conversation data — intercom.com/help/en/articles/2046229-export-your-conversation-data, read 13 November 2026. Source of text and PDF exports, the Messenger download, bulk limits, the API route, metadata-only CSV exports and excluded internal notes.
- GDPR Article 5 — gdpr-info.eu/art-5/, read 13 November 2026. Source of the data minimisation and storage limitation principles.
- California Civil Code section 1798.100 — codes.findlaw.com/ca/civil-code/civ-sect-1798-100/, read 13 November 2026. Source of the retention disclosure and reasonably-necessary limit.
- Chatbotscape evaluation methodology. /methodology (continuously updated).