Wrong Domain

search_humans returns a company_domain that doesn’t match the person’s actual company. Here’s why and how to fix it.

Why it happens

Generic company names

Companies with common English words as names cause the most issues. Examples:

When the company name is ambiguous, the domain discovery step may pick the wrong website from SERP results.

Subsidiary vs parent company

A person might work at a subsidiary but the system returns the parent company’s domain, or vice versa.

Outdated SERP data

Google’s cached snippets may reference a person’s previous employer if they recently changed jobs.

How to fix it

Pass company_domain directly

If you know the company domain, pass it as a parameter. This skips domain discovery entirely.

1
// This might return the wrong domain
2
await search_humans({
3
  name: "Mathilde Collin",
4
  company_name: "Front"
5
});
6
7
// This always uses the correct domain
8
await search_humans({
9
  name: "Mathilde Collin",
10
  company_domain: "front.com"
11
});

Use a more specific company_name

Adding context to the company name can help disambiguation:

1
// Ambiguous
2
await search_humans({ name: "John Smith", company_name: "Pipe" });
3
4
// Better
5
await search_humans({ name: "John Smith", company_name: "Pipe fintech" });

Verify the domain yourself

If the returned company_domain looks wrong, check it before using it downstream (e.g. for email generation). A wrong domain means provide_email will search for emails at the wrong company.

Rule of thumb

If the company name is a common English word, always pass company_domain directly. This is the single most effective way to avoid domain errors.