Conversations & Notes
Chat Record API: Messages, History, and Sync
Keep message identities, edits, replies, attachments, and reconnects aligned with the conversation people actually had.
Read guide →💬 MESSAGES / TRANSCRIPTS / CONTEXT
Chat & Conversation Records.
Keep what was said connected to why it matters.
Connect chat history, recorded speech, reviewed transcripts, and meeting notes without blending their different sources. Use the guides to build records that survive edits, reconnects, and a later request to verify the original context.
Keep authored messages identifiable
A chat event model can represent sends, edits, reactions, and attachments while maintaining a readable current view. The chat guide covers message identity, continuation cursors, permissions, and exports that preserve thread relationships.
Give spoken turns a timeline
Conversation records add timed segments, uncertain speaker labels, and transcript revisions. Keep calendar time separate from media offsets and preserve the original timeline when clips are edited.
Make decisions reviewable
A summary is a derived interpretation. Separate decisions from proposals and unresolved questions, and link claims back to source passages. Approval of an action item is a different event from extracting it from text.
Read the complete guides.
Conversations & Notes
Conversation Record API: Transcripts with Context
Turn recorded conversations into reviewable transcripts and evidence-linked summaries without treating interpretation as fact.
Read guide →Questions, answered.
Is a meeting summary the original record?
A summary is a derivative. Keep it linked to the transcript revision or media segments used to produce it when the workflow requires source verification.
Can chat and spoken conversation share a session?
Yes, as a design choice, while keeping typed messages and transcribed turns separately identified.