> ## Documentation Index > Fetch the complete documentation index at: https://docs.qobra.co/llms.txt > Use this file to discover all available pages before exploring further. # get_sales_coach_discussion Full transcript of one Sales Coach discussion. A list\_sales\_coach\_discussions row plus every message in order — each question, the answer it got, the Qobra data tools the agent ran to ground that answer — and the escalations that opened a request. Reach for it to diagnose a single conversation: what was asked, what the agent answered, and where it fell back to a human. Reserved to full statement access, like list\_sales\_coach\_discussions. A discussion you cannot reach reads exactly like one that does not exist. ## Parameters Id of the discussion to read — the id returned by list\_sales\_coach\_discussions. ## Response Deep link to the statement the discussion is about, in the Qobra web app. Discussions have no page of their own. The user who asked the questions. Statement period, YYYY-MM. The user the statement belongs to. Usually also the discussion's author (a rep asking about their own statement), but an admin or manager can question someone else's statement. The opening question, verbatim — what the user came for. Null for a discussion with no user message yet. Number of questions the user asked. Excludes the replies they gave to the agent's own clarifying questions, which are stored as user messages too. Total messages in the transcript, questions and answers together. Number of times the agent escalated to a human, opening a request. Above zero means the agent could not answer on its own — fetch get\_sales\_coach\_discussion for the escalation detail. When the discussion was opened — the sort key, most recent first, and what the start/end filters match. Last activity on the discussion. The full transcript in chronological order — each question and the answer it got, with the tools that produced it. Who wrote the message: 'user' (the question asked), 'assistant' (the agent's answer) or 'system'. Tool traffic is folded into the answer's `tools` rather than surfacing as its own message. One of: `user`, `assistant`, `system`, `tool`. Names of the Qobra data tools the agent ran to produce this answer, in call order — how it grounded the reply. Empty on a user message, and on an answer that needed no lookup. The human hand-overs the agent opened, in order. The request the escalation opened, named after the escalation title. Null when you have no access to that request — the escalation still happened.