> 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/delpha-for-salesforce/how-to-faq/delpha-ultimate-parents.md).

# Delpha Ultimate Parents

Automate B2B account hierarchies in Salesforce with Delpha. Detect, validate, and map ultimate parent holding companies to prevent territory conflicts, and enable enterprise roll-up reporting.

An Ultimate Parent is the top-level legal entity or holding company at the head of a complex corporate hierarchy. Delpha automatically detects, validates, and maps these global relationships in your CRM to clean up fragmented account structures, prevent territory conflicts, and ensure accurate enterprise roll-up reporting.

* [What are the Delpha Ultimate Parent fields](/delpha-for-salesforce/how-to-faq/delpha-ultimate-parents/what-are-the-delpha-ultimate-parent-fields.md): This reference details the custom Salesforce fields used by Delpha to analyze, enrich, and automate corporate hierarchy data. Use the tables below to find exact field labels, API names, and functional roles across four key areas: Data Health Analysis, AI Recommendations, Audit Metadata, and Calculated Account Relationships.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-ultimate-parents.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 `build a script that syncs our docs to a CMS` 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.