Visitor Identification

Aimdoc includes built-in visitor identification to help you understand who is engaging with your agent, even when the visitor does not fill out a form.

This page covers anonymous website enrichment. To identify signed-in users inside your application—and associate them with your application accounts—use the identify method in the Aimdoc SDK with Identity Verification on the Activate plan.

What it does

When identification is available for a session, Aimdoc can:

• Identify visitors from available network and enrichment signals
• Enrich conversations with person and company context
• Personalize responses using that context in real time
• Support routing and follow-up by giving your team better lead intelligence
• Link company context to an Account when a company domain is known

How it appears in Aimdoc

Identification data is surfaced directly in your existing workflow:

• In conversations, the agent can use enriched context to personalize replies
• In contact and session records, enriched visitor details are included when available
• In Accounts, enrichment can create or update an enriched account and show company facts
• In notifications, teams can receive a Visitor Identified notification

Account owners and notifications

When Aimdoc resolves a company domain from enrichment (or from a later work-email contact), it can match that domain to a Salesforce or HubSpot account and surface the CRM account owner.

If a teammate in Aimdoc matches that CRM owner and has Visitor Identified (or other relevant) notifications enabled, their email and Slack alerts can call out the account they own. Enriched matches include a disclaimer that the association is a signal, not a confirmed work-email identity.

For Salesforce, configure the Account Match Field on the agent so Aimdoc can find the right CRM account by domain. See Accounts: CRM account owners and Salesforce.

Setup

No standalone integration setup is required for customers.

If you want to validate how identification appears in your workspace, check:

1. A live conversation where a visitor can be enriched
2. The session or contact record for enriched fields
3. Notification preferences for "Visitor Identified" alerts
4. The Accounts page when a company domain is available

Notes and expectations

• Identification coverage varies by traffic source, geography, and data availability.
• Not every anonymous visitor can be resolved to a person.
• When no enrichment is available, Aimdoc continues operating normally with standard conversation and contact capture behavior.
• Enriched account matches are lower trust than confirmed work-email accounts.