> For the complete documentation index, see [llms.txt](https://sayy-ai.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sayy-ai.gitbook.io/docs/business-features/acquiring-customer-leads.md).

# Acquiring Customer Leads

Sayy helps you capture high-intent leads right from the conversation. Whether your visitors are asking questions, browsing products, or booking a call, your AImployee knows when and how to collect the right information without interrupting the flow.

#### 🧠 Context-Aware Lead Capture

Your AImployee can intelligently prompt users for their name, email, phone number, or other details based on the conversation. If someone shows buying intent or requests specific information, the agent can ask for contact details naturally, without feeling robotic or intrusive.

#### 📥 Smart Forms, Inside Chat

There are no external forms or redirects. All lead capture happens inside the chat interface. Your AImployee collects the details, confirms them with the user, and stores them instantly in your Lead Inbox for follow-up.

#### 📁 Centralized Lead Inbox

All leads are saved in one place- your dashboard. You can view each profile, track their chat history, and see what they interacted with. This makes it easy to prioritize hot leads and follow up at the right time with the right message.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sayy-ai.gitbook.io/docs/business-features/acquiring-customer-leads.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.