Skip to content

What to do after identifying a visiting company

Identification is only the first step. The value comes from turning a company signal into a qualified account, a relevant contact and a commercial action that respects the limits of the data.

Updated November 8, 2026Kiodo research8 min read

The wrong workflow

The wrong workflow is: visit identified → reveal every contact → send the same template to everyone → count the alert as a lead. It produces activity, not learning, and it often annoys the people you most want to reach.

The right workflow starts with a qualification question: is this account worth a human look?

1. Qualify the account

  • ICP fit: industry, size, country and business model.
  • Intent: which pages, how often, how recently and with what confidence.
  • Account state: existing customer, open opportunity, competitor, partner or excluded company.
  • Signal quality: corporate network versus hosting, VPN, mobile or residential traffic.

A high score is not automatically a qualified account. A low score can still matter when the page and account fit are strong.

2. Read the page context

A pricing visit, a security page, a comparison page and a careers page mean different things. Build intent weights that reflect your business. A visit to “pricing” may be commercial; a visit to “careers” may be irrelevant to sales.

Kiodo lets you assign page weights and exclude paths. The goal is not to score every page equally; it is to make the queue reflect your actual buying process.

3. Choose a relevant contact

Start with the role that owns the problem suggested by the page. A pricing visit may justify a founder, VP or growth leader. A security page may justify a technical or compliance role. A comparison page may justify the person evaluating alternatives.

Kiodo can suggest contacts at the company and reveal available data on paid plans. The contact is a person at the account, not proof that the person visited.

4. Write a contextual first touch

Use the company context, not a fake personal claim. For example:

“I saw that Example Co has been reviewing pricing and comparison pages this week. If you are evaluating visitor identification, I can share a short example of how teams separate company-level intent from person-level claims.”

This is honest: it references the company activity without pretending to know which employee visited.

5. Route and own the signal

A Slack alert should include the account, domain, score, last page, visit count, suggested contact and a clear owner. If two reps receive the same alert with no owner, the signal becomes noise.

Use deduplication and a cooldown window. A company that visited yesterday does not need five identical alerts today.

6. Measure the useful outcome

  • Qualified accounts identified
  • Contacts revealed per qualified account
  • Reply rate and meeting rate
  • Pipeline created from identified accounts
  • Time from visit to first human action

Impressions and page views are diagnostic. They are not the goal.

An illustrative example

A company visits a pricing page and a comparison page twice in three days. Kiodo identifies the account, scores the activity and shows a relevant growth contact. The rep checks the account, sends a contextual note and logs the outreach. The contact did not necessarily visit the site, but the account did show intent.

That distinction keeps the workflow useful and defensible.

What not to do

  • Do not claim that a suggested contact visited the site.
  • Do not reveal contacts without a clear reason and credit budget.
  • Do not treat every identified network as a qualified company.
  • Do not send a generic template to every contact at the account.
  • Do not optimize for alert volume instead of qualified conversations.

Post-identification FAQ

What should I do first after identifying a company?

Qualify the account before contacting anyone. Check the pages visited, intent score, recency, whether the company fits your ICP and whether the visit looks like a real buying signal rather than a network artifact.

Should I contact the person who visited?

You usually cannot know who visited. Use the company signal to choose a relevant contact, then make it clear in your outreach that you are reaching out because the company was researching the topic, not because you know that person visited.

How many contacts should I reveal?

Start with one or two relevant roles. Revealing every contact at a company wastes credits and encourages generic outreach. Match the contact to the page and the problem.

What should the Slack alert contain?

Company, domain, score, last page, visit count, first seen, owner and a short reason for the alert. The alert should create an action, not just announce a visit.

How do I measure success?

Track qualified accounts, contacts revealed, replies, meetings and pipeline. A visit is an input. The useful output is a qualified conversation, not a larger dashboard count.

Build the workflow in Kiodo.

Start free