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.

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

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 lead and session records, enriched visitor details are included when available
• In notifications, teams can receive a Visitor Identified notification

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 lead record for enriched fields
3. Notification preferences for "Visitor Identified" alerts

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 lead capture behavior.