​

Lead Identification

Agentsy helps you turn anonymous interest in your expertise into conversations you can better understand. When visitors interact with your branded AI Experience, their questions can reveal what they are trying to solve, what information they need, and whether speaking with a person would be useful. Lead identification is not the same as lead qualification. A visitor who registers has shared an identity; a visitor who expresses a relevant need or asks for next steps may show stronger commercial intent. Neither automatically guarantees a sale.

​

How lead identification works

An AI Experience can create several useful signals:

1. Visitor identity: Where registration is enabled and completed, you may be able to associate conversations with the information provided by the visitor.
2. Conversation context: Questions and topics can reveal what visitors are interested in.
3. Expressed intent: A visitor might ask about your process, suitability, pricing, availability, or how to work with you.
4. Human follow-up: When appropriate, the assistant can recommend the contact or booking path configured for your experience.

​

Understand different levels of interest

Not every conversation represents the same opportunity. Use these examples as interpretive guidance, not as an automatic scoring system. A single question is rarely enough to determine someone’s readiness. Consider the conversation in context, and avoid drawing conclusions from sensitive or unrelated personal details.

​

Example: A business consultant

Imagine a consultant whose AI Experience helps business owners explore operational challenges. Visitor A: “What is process automation?” This is an educational question. The assistant should answer it clearly without immediately pushing for a meeting. Visitor B: “We have three teams manually transferring data between systems. How would you evaluate what to automate first?” This suggests a more specific operational need. The assistant can outline an evaluation framework, ask one relevant follow-up question if necessary, and help the visitor think through priorities. Visitor C: “Can I book a session to discuss our processes?” This is an explicit request for human contact. The assistant should explain the available next step and point to the booking or contact option configured for the AI Experience.

​

Review conversation context responsibly

When reviewing visitor activity available in your Agentsy workspace, consider:

• What problem is the visitor trying to solve?
• What stage are they at? Learning, comparing, planning, or ready to speak?
• Which part of your expertise attracted their interest?
• Did they explicitly request a next step?
• What would make a follow-up genuinely helpful?

Do not assume a visitor’s budget, purchasing authority, personal circumstances, or intent unless they have clearly provided that information and it is appropriate to use.

​

Create a natural path to human conversation

A good AI Experience can help visitors progress through three broad stages:

1. Understand: The visitor explores a question and receives useful information.
2. Clarify: The assistant helps them evaluate options or frame their needs.
3. Connect: If the visitor expresses interest or reaches a point requiring personal assistance, the assistant recommends an appropriate human next step.

This progression is flexible. Visitors may begin at any stage, move backward, or prefer to continue learning without contacting anyone.

​

Example handoff language

“Based on what you’ve described, it could be useful to discuss the specifics with our team. You can use the booking option on this page if you’d like to take that next step.”

Only refer to a booking button, contact form, or other action if it actually exists on your AI Experience.

​

Registration and guest conversations

Registration and access settings influence whether you can connect a conversation to a known visitor.

• Registered visitors: May provide identifying details as part of the configured registration process.
• Guest visitors: May be able to explore the experience without first registering, depending on your setup.
• Invite-only experiences: Restrict who can access the experience; this is separate from determining whether someone is a qualified lead.

For access and registration details, see User Registration and Guest Chat and Registration.

​

Protect visitor privacy

Lead identification should support helpful communication, not intrusive profiling.

• Collect only the information needed for your stated purpose.
• Explain how visitor information and conversations may be used in your applicable privacy notice.
• Avoid asking visitors to share passwords, financial account details, medical records, or other unnecessary sensitive information.
• Follow applicable privacy and data-protection requirements, including consent requirements where relevant.
• Restrict access to visitor information to authorized people.
• Respect requests concerning personal data according to your policies and applicable law.

For regulated or sensitive subjects, design the assistant to stay within an appropriate educational scope and direct visitors to qualified professionals when needed.

​

Test your lead-identification experience

Before publishing, test the following scenarios:

• A visitor asks a general question and receives a useful answer without a premature sales pitch.
• A visitor describes a concrete business need and receives relevant guidance.
• A visitor asks to speak with a person and receives the correct next step.
• A guest visitor is not incorrectly presented as a registered lead.
• Registration works as expected on desktop and mobile.
• The assistant does not invent availability, prices, appointments, or other information it cannot verify.
• The assistant does not request unnecessary sensitive information.
• Any booking or contact link actually works.

​

Common mistakes to avoid

​

Related guides

• Conversation Experience
• User Registration
• Conversation Insights
• Understanding User Intent
• Human Handoff
• Privacy and Access