What is it?

The Enricher agent in AgentFlow validates and corrects problematic addresses in Organization (or equivalent) profiles using evidence from authoritative external sources. It can search for entities with addresses marked as Partially Verified or Ambiguous, retrieve full profiles, research addresses across multiple sources, and then propose corrections or new Locations with a clear before-and-after summary.

When you approve its recommendations, the agent updates Location entities using auditable writes under the Agent source, helping you maintain a trusted address baseline for downstream matching, segmentation, and reporting.

For more information, see Address Enricher.

Find profiles with partially verified or ambiguous addresses

✅ Prompt: Find organizations with addresses marked as Partially Verified or Ambiguous.

Why it works: This prompt clearly names the entity type (organizations) and uses the verification status values that the agent expects (Partially Verified and Ambiguous). The agent can translate this into a filtered search for entities whose primary Location matches those statuses and return a manageable list for you to work through.

⚠️ Prompt: Search for HCP/HCO with addresses marked as “Partially Verified” or “Ambiguous”.

Issue: In early tests, this type of broad search returned only partially verified addresses and missed some ambiguous ones. When re-run, the agent sometimes reported that no ambiguous addresses existed, even when they did. This suggests a combination of scanning limits and query interpretation issues. If you see unexpected results, narrow the scope (for example, a specific country or segment) or switch to a single known entity and validate that address first before scaling up.

Validate a specific address using external sources

✅ Prompt: Validate this organization's address using external sources and tell me whether it's correct: 123 Main Street, Springfield, IL 62701, United States.

Why it works: Providing the full address in plain text lets the agent focus on a single location. It can research postal authorities, maps, corporate registries, and official websites, then summarize whether the address is valid, partially valid, or likely incorrect, along with suggested corrections and evidence URLs.

⚠️ Prompt: There is an entity at this URL: …/profile?entityUri=entities%2F05sNTtr. It has an ambiguous address, could you please check and validate the address from external sources?

Issue: Using a UI URL instead of a direct entity ID can make it harder for the agent to resolve the correct profile. In tests, this pattern sometimes failed to retrieve the entity at all, even though it existed. For more reliable results, copy the underlying entity ID (for example, 05sNTtr) and reference it directly in your prompt.

⚠️ Prompt: There is an HCP with name LA CHANDA BROWN, NPI 1588141725, with an unverified address at “PSC 7085, Box 7396 APO AE 23950, Butlerbury, Mississippi, 02106, United States of America.” Could you please validate if this is the right address?

Issue: In tests, the agent’s suggested address did not align with the evidence URLs it provided, and it inferred an incorrect associated organization. When results look inconsistent with the evidence or your domain knowledge, treat the output as a starting point, not a final decision. Cross-check in Reltio and your reference tools before applying any changes.

Review and apply corrections

✅ Prompt: For this organization (entity ID 00INPUY), review its primary address against external sources and tell me whether you recommend correcting it or creating a new Location.

Why it works: This prompt anchors the agent on a single, known entity ID and asks for a clear recommendation: correct the existing Location or create a new one. The agent can retrieve the current address, research multiple sources, and then propose specific changes, including whether the new address should be a completely separate Location.

⚠️ Prompt: Fetch the full profile of entity ID 00INPUY and provide me with the address and other information.

Issue: In tests, generic “full profile” prompts sometimes returned incorrect or mismatched entities (for example, a profile with a different name than the requested ID). To reduce the risk of confusion, focus your prompts on address validation tasks (for example, “review and correct the primary address”) instead of broad profile retrieval, and verify entity details in the Hub if something looks off.

⚠️ Prompt: Fetch the full profile of entity ID 000I6vE and show me the addresses.

Issue: In one test, the agent retrieved information but returned a profile name that didn’t exist in the tenant (for example, JEFFREY TODD BRANDT instead of the expected profile). If a returned profile looks unfamiliar, confirm the entity in Reltio UI before acting on any proposed updates.

Best practices