conversation_insights

1 row where conversation_id = "0ce90240-397e-463a-a066-c66d3161c5aa"

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: date (date), analyzed_at (date), participants (array), topics (array), needs_expressed (array), emotional_keywords (array)

conversation_id ▼ date title relationship_type participants topics arc_start arc_mid arc_end energy_direction jake_role key_moment needs_expressed connection_quality emotional_keywords analyzed_at prompt_tokens completion_tokens
0ce90240-397e-463a-a066-c66d3161c5aa 2026-04-16 Discussing Advanced Illness and Limited Options self ["User", "Speaker 3", "Speaker 0"] ["advanced_illness", "limited_options"] -0.5 -0.7 -0.8 draining speaker And there's nothing we can do about it now. ["validation", "clarity", "to_be_heard"]   ["sadness", "frustration", "helplessness"] 2026-04-16T06:03:03.628562 669 152

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE conversation_insights (
            conversation_id TEXT PRIMARY KEY,
            date TEXT NOT NULL,
            title TEXT,
            relationship_type TEXT,
            participants TEXT,       -- JSON array
            topics TEXT,             -- JSON array
            arc_start REAL,
            arc_mid REAL,
            arc_end REAL,
            energy_direction TEXT,
            jake_role TEXT,
            key_moment TEXT,
            needs_expressed TEXT,    -- JSON array
            connection_quality REAL,
            emotional_keywords TEXT, -- JSON array
            analyzed_at TEXT,
            prompt_tokens INTEGER,
            completion_tokens INTEGER,
            FOREIGN KEY (conversation_id) REFERENCES omi_conversations(id)
        );
CREATE INDEX idx_conv_insights_date ON conversation_insights(date);
CREATE INDEX idx_conv_insights_rel ON conversation_insights(relationship_type);