For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Login
HomeDocsAPI ReferenceMCP ServerChat SDKsRelease Notes
HomeDocsAPI ReferenceMCP ServerChat SDKsRelease Notes
  • Introduction
    • Overview
    • Getting started
    • Authentication
    • Data privacy
    • Built-in prompts
    • FAQ
    • Troubleshooting
  • Tools
    • Overview
    • get_ada_configuration
    • get_ada_metric
    • get_available_filters
    • get_conversations
    • get_conversation
    • search_knowledge
    • search_coaching
    • get_improvement_guide
    • list_entities
    • propose_change
    • get_test_cases
    • get_test_runs
    • get_test_run_quota
    • send_feedback
  • Prompt library
    • Overview
    • Improvement recommendations
    • Quick health checks
    • Create visualizations
    • Diagnose performance issues
    • Identify optimization opportunities
    • Review configuration
    • Search knowledge and coaching
    • Test agent responses
    • Deep-dive analysis
Login
LogoLogo
On this page
  • Example prompts
  • Parameters
  • Response
Tools

get_conversation

Was this page helpful?
Previous

search_knowledge

Next
Built with

Retrieves the full transcript for a given conversation ID, including message content, reasoning history, and metadata.

Conversation transcripts may contain personally identifiable information (PII). Review data privacy before enabling this tool in production workflows.

Example prompts

  • “Show me the transcript for conversation abc123.”
  • “Review this conversation and tell me what the Agent got wrong.”
  • “Pull the transcripts for these 5 unresolved conversations and summarize the common failure mode.”

Parameters

ParameterTypeDescription
conversation_idstringThe unique identifier for the conversation, returned by get_ada_metric or get_conversations.

Response

Returns the transcript and associated metadata:

  • Message-by-message exchange between end user and Agent.
  • Reasoning history (why the Agent responded the way it did).
  • customer_inquiry_summary.
  • automated_resolution_status and automated_resolution_reason.
  • Applied playbooks, actions, and coaching.
  • Handoff status and reason (if applicable).