Intempt Docs
GuidesCustomer Data Platform

Intempt Enrich

Three AI verbs in the CRM: Discover finds net-new prospects from a plain-language ICP, Enrich fills in a known record's attributes, and Verify confirms an identity. Use them in Blu chat or from the CLI and MCP.

Overview

Intempt Enrich adds three AI verbs to your CRM:

  • Discover – find net-new prospects from a plain-language description of who you want.
  • Enrich – resolve a known user or account and fill in its attributes from third-party data.
  • Verify – confirm that an enriched user or account is who the record says it is.

You can run all three from Blu chat, and the same verbs are available from the CLI and the MCP server for scripted or agent-driven work.

Discovering and enriching prospects uses third-party data. See the pricing page for details.

How it works

Discover

Discover finds prospects you don't have yet. Describe your ideal customer in plain language, for example "VPs of Marketing at Series B SaaS companies," and Blu returns a list of matching people. The search is grounded on your project's brand kit and knowledge base, so the results reflect who you actually sell to. This is different from CDP search, which looks through records you already have.

Discovered prospects are not written to your CDP right away. They appear as a preview list that lives only on the chat message that produced them, so you can review the matches before anything lands in the CRM.

In Blu chat:

  1. Ask Blu to find the prospects you want, in plain language.
  2. A list of discovered prospects appears in the chat.
  3. Review the rows, then click Save to CDP. The prospects you keep become real CDP records.

Saved prospects are created as Users. Saving them as Accounts is coming soon.

📘 Media pending

Screenshot of the Discover result list hasn't been captured yet.

Enrich

Enrich works on a record you already have. Point it at a user or account and Blu resolves the identity, then fills in attributes like email, title, company, location, and social profiles from third-party data. The result is written back to the record as a dossier.

Enrich runs only when there's a strong anchor to match on: an email, a LinkedIn profile, or a phone number. Blu also applies a match gate, so it writes attributes only when it's confident the third-party data belongs to the same person or company. A record with no strong anchor can't be enriched until you add one.

Verify

Verify confirms the identity on an enriched user or account. Run it after Enrich when you want a check that the resolved identity is correct before you act on it.

Also in the CLI and MCP

The same three verbs are available outside the console.

From the CLI:

  • intempt discover "<icp prompt>" [--limit N] – start a discovery run. Returns a run_id.
  • intempt discover preview <run_id> – preview the prospects parked on that run.
  • intempt discover save <run_id> – save the run's prospects into the CDP.
  • intempt enrich <entity_id> [--account] [--force] – enrich a user, or an account with --account.
  • intempt verify <entity_id> [--account] – verify a user, or an account with --account.

From the MCP server:

  • intempt_discover, intempt_discover_preview, intempt_discover_save – the Discover run, preview, and save steps.
  • intempt_enrich – enrich a user or account.
  • intempt_verify – verify a user or account.

The CLI splits Discover into run, preview, and save so you can check the matches before they reach the CDP, the same two-step flow as the Save to CDP button in chat.

Use cases

  1. Build a target list from a description. Use Discover to turn an ICP sentence into a reviewable list of net-new prospects.
  2. Keep new prospects out of the CRM until you've checked them. Preview a Discover run, then save only the rows you want.
  3. Fill the gaps on a thin record. Enrich a user who has an email but little else to pull in title, company, and socials.
  4. Enrich an account, not just a person. Pass --account to resolve and enrich a company record.
  5. Confirm an identity before you act. Verify an enriched record before adding it to a journey or handing it to sales.
  6. Script discovery into your own tools. Drive the Discover run, preview, and save steps from the CLI or MCP.

Where to go next

On this page