Skip to main content

Export support history

Users can export their own retained . Authorized staff can export conversations they may currently read. Each page checks permission again; losing access stops the export.

User exports exclude . Private screenshots require authenticated links and current conversation access. An export cannot restore deleted content or bypass retention rules.

Hosted storage lifecycle and cost checks remain required before exports are advertised as verified. Check feature availability when planning a rollout.

API​

GET /rooms/:workspaceId/conversations/:conversationId/export returns a JSON page with conversation, messages, nextBefore and export metadata. Start without a cursor, then pass before with the returned nextBefore value for the next page. A null nextBefore ends the export. The and conversation IDs identify the thread; knowing them grants no access.

Honor the response's pacing and Retry-After. Stop on an authorization error. Save all pages before labeling an export complete. A canceled export is a partial file.

When Support coverage ends, the team has 30 days to read and export under current permissions. Then Templ deletes every conversation with its notes, activity and screenshots. While coverage lasts, resolved and spam conversations are deleted 365 days after their last message. Trust lists every retention time. Once downloaded, an export can be copied outside Templ; revoking staff access cannot recall that file.