Conversations and history
Multi-turn in the open widget; partner console inbox for review when history is enabled.
What works today
While a visitor keeps the Assistants widget open, they get multi-turn Q&A. Follow-up questions stay in the same thread so the assistant can use earlier turns in that session.
Transcripts for partner embed traffic are stored on our side in partner-isolated tables (for operations, metering, and legal process).
Partner console inbox
Workspace owners can open Conversations in the Assistants console at platform.ismscopilot.com/embed when history is enabled on that environment:
- List recent conversations (visitor embed by default; optional playground tests)
- Open a full transcript (text)
- Download one conversation as plain text
- Delete one conversation (confirm; moderation holds may block delete)
Public visitor chats expire about 30 days after last activity. Identified (JWT) conversations are kept until you delete them or complete offboarding.
What is not available yet
| Gap | Meaning |
|---|---|
| Visitor history sidebar | No list of past chats for the end visitor after close/reload |
| Resume after reload | A new open starts a fresh conversation in the widget UI |
| Full-text search / bulk export | Inbox is chronological; download is single-thread only |
Identified vs public installs
- Public key installs: short-lived public sessions; multi-turn while open; 30-day retention.
- Identified JWT installs: stronger end-user isolation; no auto-TTL today; still no visitor resume UI.
Do not market embed as a full white-label chat product with visitor-side history until those surfaces ship. Partners review transcripts in the console; visitors get multi-turn Q&A in the open widget.