> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getwhys.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Citations

> Every claim links to its source. When someone asks "how do we know?", you can show them.

Every answer GetWhys produces is grounded in sources. Citations are the inline references that show you exactly which research interview, document, or web result informed each insight. Click into any of them to inspect the underlying material.

This is the "how do we know?" answer baked into the product. You stop defending your sources and start proving your impact.

<AccordionGroup>
  <Accordion title="What's in a citation">
    When the source is a GetWhys research interview or one of your uploaded documents, the citation includes:

    * **When the interview took place**
    * **Job title** of the interviewee
    * **Industry** and **company size** (FTE count)
    * **Summary of the interview context** and key insights
    * **Brief summary of the snippet** that informs the cited line
    * **Excerpt from the interview transcript** that's the underlying source material

    That's a lot of context per citation. It's there so you can verify the insight, learn about the buyer, and pull direct buyer language into the work you're producing.
  </Accordion>

  <Accordion title="Three source types">
    GetWhys answers can pull from three places:

    1. **GetWhys Data** — the proprietary research interview corpus. Every cited insight links to a specific interview snippet.
    2. **Organization Data** — your uploaded files (sales calls, win/loss interviews, internal research). Every cited insight links to the specific document and excerpt.
    3. **The open web** — used by some Chat queries. Citations link to the underlying URL.

    <Warning>
      When an answer has few or no citations, it's leaning on the language model's general training data rather than first-party research. Those answers are still useful for orientation, but they're your signal to verify before you ship anything based on them, or to file a [Research Request](/features/research-requests) and get firsthand interviews.
    </Warning>
  </Accordion>

  <Accordion title="Reading the citation panel">
    Click any inline citation in a Chat answer to open the citation panel on the right side. You'll see the full transcript excerpt, the interviewee context, and a link to the original source. The panel stays open as you scroll, so you can read the source while reading the answer.
  </Accordion>

  <Accordion title="Citations when sharing">
    When you share a conversation or Artifact, citations come with it. Anyone with access can open the underlying source the same way you can. Useful when you're handing work to leadership, sales, or other teams that want to see the receipts.
  </Accordion>

  <Accordion title="When citations aren't enough">
    If an answer's citations don't go deep enough, file a [Research Request](/features/research-requests). Our team will interview more people on your specific question and the new interviews get added to your account.
  </Accordion>
</AccordionGroup>