> For the complete documentation index, see [llms.txt](https://docs.patagon.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patagon.ai/en/sales-performance/lead-details.md).

# How to read a lead's details

Lead Details gives you the full context on a contact. Open it by clicking any conversation in Leads > Conversations. The detail panel opens on the right side.

![Lead details panel](/files/HohMnSf9FSlWuBalLvUa)

## The 6 tabs

**Information —** Qualification score, sentiment, contact data, assigned team member, first and last activity dates, AI-generated intent summary, conversation summary, and tags. Also shows Billing Status and a Dispute Lead button (7-day window).

**Attribution —** UTM parameters: Source, Medium, Campaign, Content, Term, and the Facebook Click ID. Also shows the full referral URL.

**Notes —** Internal notes visible only to your team. Click + Add note to add insights, reminders, or follow-up actions.

**Outcome —** Mark the lead as Won or Lost and save.

**Media —** Any media files shared during the conversation.

**Journey —** Chronological timeline of every event: lead created, conversation started, messages sent, qualification changes, and assignments.

The conversation header shows the rating assigned by ILA. Read the qualification rationale to understand the evidence behind it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.patagon.ai/en/sales-performance/lead-details.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.