Conversation export

Two export paths

Export a filtered dataset

• Set responder, scope, site, contact, label, date, and search filters in History.
• Review the result count to confirm the intended population.
• Choose Download filtered conversations as JSON.
• Stand prepares the export, then the browser starts the file download.
• Keep the file only in tools and locations approved for the organization’s customer data.

What an export represents

• Conversation and responder metadata available to the requesting member.
• Retained transcript content and structured conversation records included by the export format.
• The effective visitor name where present; private page-known external IDs are excluded.
• Only data still present under the current retention policy at export time.

After the data leaves Stand

Limitations

• Copy requires browser clipboard access and can fail when permission is denied.
• A bulk export is constrained by the current user’s authorization and active filters.
• The JSON file is intended for customer-controlled analysis; Stand does not automatically import edits back into History.
• Expired or already-deleted content is not reconstructed for export.

Example

The screen below shows the feature in its normal Stand context. Labels and surrounding controls may vary with account state and plan.

Related features

• Conversation History — History is the searchable record of completed human and AI conversations, including their transcripts, captured outcomes, origin, timing, and assigned responder.
• History search and filters — History filters narrow the completed-conversation record by responder, member scope, site, visitor contact, label, date, and transcript text.
• Conversation retention — Conversation retention controls how long completed chat content and visitor-supplied fields remain searchable before Stand clears them.