> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/use-cases/ultimate-parent.md).

# Ultimate Parent

Ultimate Parent resolves who really owns each account — what it does, how selection works, the JSON payload it returns, and how quality is scored. Channel-agnostic: same result via Salesforce, MCP, an

Delpha Ultimate Parent resolves the company at the top of each account's corporate hierarchy — the commercial parent an agent or a rep should route, plan, and report against — and returns the same verdict, evidence, and JSON payload through Salesforce, MCP, and API.

## In this section

[**What it does & when to use it**](/use-cases/ultimate-parent/what-it-does-and-when-to-use-it.md)\
The problem Ultimate Parent solves and the go-to-market situations it changes.

[**How selection works**](/use-cases/ultimate-parent/how-selection-works.md)\
Brands & operating structures, the 10 logic protocols, and the analysis behind each recommendation — with [Concepts](/use-cases/ultimate-parent/how-selection-works/ultimate-parent-concepts-brands-vs.-operating-structures.md), [Protocols](/use-cases/ultimate-parent/how-selection-works/how-delpha-selects-the-ultimate-parent-the-10-logic-protocols.md), and [Analysis](/use-cases/ultimate-parent/how-selection-works/understanding-the-ultimate-parent-analysis.md) detail pages.

[**Output — the JSON payload, field by field**](/use-cases/ultimate-parent/output-the-json-payload-field-by-field.md)\
The payload every channel returns, with the [Salesforce field reference](/delpha-for-salesforce/how-to-faq/delpha-ultimate-parents/what-are-the-delpha-ultimate-parent-fields.md).

[**Quality & confidence scoring**](/use-cases/ultimate-parent/quality-and-confidence-scoring.md)\
How Ultimate Parent records are scored against Delpha's data quality dimensions.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.delpha.io/use-cases/ultimate-parent.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.