---
title: "Reach the real owner, not the wrong person - Atlan MCP Cookbook"
url: "https://atlan.com/mcp-cookbook/find-the-right-owner-to-contact/"
description: "Trace a failing number back to the asset behind it, then find out who owns that dataset, so the problem reaches the team accountable for it."
---

> Atlan is hosting Context Conference, bringing together the leaders and builders at the frontier of giving AI the context it needs to understand their business. It runs online on October 28, 2026, from 11:00 AM to 2:00 PM ET. Atlan co-founder Prukalpa Sankar opens and closes the day. Leaders from AstraZeneca, BNY and Verizon share why they invest in context and what they get from it. Registrants get early access to The AI Context Gap, a new study from MIT Technology Review Insights. Register: https://atlan.com/context-conference/

Recipe 32 in [The Atlan MCP Cookbook](https://atlan.com/mcp-cookbook/). Trace a failing number back to the asset behind it, then find out who owns that dataset, so the problem reaches the team accountable for it instead of a general channel.

Use case: Govern & keep trusted / Action: Look up / Persona: Data/Business User, Data Engineer, Data Governance Lead / Effort: Quick / Runs in: any AI tool

Requires Atlan MCP connected to your AI tool: [set up Atlan MCP](https://docs.atlan.com/product/capabilities/atlan-ai/how-tos/remote-mcp-overview).

## 1. The task

**Scenario.** A revenue dashboard is showing figures that don't reconcile, and the analyst who spotted it has no idea which upstream asset is actually at fault or who to tell. Posting "revenue looks wrong" in a general channel gets a day of guessing and no owner. The fix is to identify the asset behind the number first, then resolve who's accountable for that specific asset - because the right contact depends entirely on which asset turns out to be the problem.

The ask:
- The asset the failing number actually comes from
- Its data quality status, including whether the failure is already known
- Who owns that dataset, and the team accountable for it

Hero prompt: "Revenue numbers aren't reconciling. Find the asset behind the revenue figures, check its data quality status, and tell me who owns it so I can raise this with the right team."

Step by step:

1. Find the asset behind the number. Prompt: "Find the certified asset that the [revenue] figures come from, so I know which one is actually behind the number that's wrong."
2. Check what its data quality status says. Prompt: "Show me that asset's data quality status and any recent failures or incidents on it, so I know whether the problem is already known."
3. Resolve who's accountable for it. Prompt: "Show me the owner of that asset, so I can raise this with the team accountable for it rather than a general channel."

## 2. What you'll give it

Required context:
- The number, metric, or dashboard that looks wrong

Optional context:
- Where you saw it, if the same figure appears in more than one place
- How urgent it is, which changes whether you raise it now or queue it

## 3. What Atlan creates

Outputs:
- The asset the failing number actually comes from
- Its data quality status, including whether the failure is already known
- The owner accountable for that asset, so you know who to raise it with

**Summary.** The problem goes to whoever is accountable for the specific asset at fault, with the quality status already attached, instead of a general channel where it waits for someone to guess which table is wrong.

**Read-only.** Read-only. Nothing is updated in Atlan; this identifies the asset, its status, and its owner.

## 4. Follow-up prompts

- **Look further upstream:** "Trace the lineage upstream from that asset to see whether the problem starts further back."
- **Find ownership gaps:** "Check ownership coverage across this domain."
- **See who else is affected:** "Show me everything else that depends on that asset."

## 5. Tips & troubleshooting

**Cook's note.** Find the asset before you look for the owner. Ownership is only useful once you know which asset is actually at fault - reaching the owner of the dashboard when the problem is three tables upstream just moves the guessing to someone else's inbox.

- Match the client to the work.** Any client works here; this is a short lookup, not a multi-step reasoning job.
- Automate or chain it.** Wire this into the channel where quality alerts land, so an alert arrives with its asset and owner already resolved.
- Recheck before you escalate.** Ownership and quality status both change. Re-pull them right before you raise it, not from a check you ran days ago - otherwise you escalate a failure that's already been fixed, or route it to someone who's handed the asset on.

## Related recipes

- [Route data requests to right assets](https://atlan.com/mcp-cookbook/route-data-requests-to-right-assets/): Surface certified, well-documented assets in response to a business request.
- [Warn downstream owners before a change lands](https://atlan.com/mcp-cookbook/warn-downstream-owners-before-a-change-lands/): Find every downstream consumer of a changing asset and warn their owners first.
- [Triage a data-quality failure with full context](https://atlan.com/mcp-cookbook/triage-a-data-quality-failure-with-full-context/): Enrich quality failures with lineage, ownership, and downstream impact for faster triage.

[Browse all recipes](https://atlan.com/mcp-cookbook/) / [Set up Atlan MCP](https://docs.atlan.com/product/capabilities/atlan-ai/how-tos/remote-mcp-overview)