> For the complete documentation index, see [llms.txt](https://docs.athenachat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.athenachat.ai/documentation/documentation-en/use-cases/prodazhi.md).

# Sales

Lead qualification, consultation, and closing the deal

The agent advises on the catalog, qualifies the lead, handles objections, and either places the order or hands the hot prospect over to a manager in the CRM.

Source on the website: [Sales](https://athenachat.ai/ru/use-cases/sells/).

## What it solves

* Customers message at night and on weekends — without a response, they go to competitors.
* Managers spend the day on “how much does it cost?” instead of complex deals.
* Leads from ads go cold, and inquiries from messengers don’t make it into the CRM.

## How it works

1. Instantly receives the lead in [channel](/documentation/documentation-en/channels.md) and engages them in dialogue.
2. Finds out the need, advises on prices and availability from [the knowledge base](/documentation/documentation-en/features/knowledge-base.md) or [tables](/documentation/documentation-en/features/tables.md).
3. Handles objections, suggests an alternative or a promotion.
4. Creates the order, sends payment, or creates a deal in the CRM with conversation history.

## What to configure

| In the dashboard                                                                                                                                                                                           | Why                                               |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
| [Role, instructions, task](/documentation/documentation-en/features/agent-setup/general.md)                                                                                                                | Sales script and goal of the conversation         |
| [Knowledge base](/documentation/documentation-en/features/knowledge-base.md) and [tables](/documentation/documentation-en/features/tables.md)                                                              | Catalog, prices, delivery                         |
| [Triggers](/documentation/documentation-en/features/agent-setup/triggers.md)                                                                                                                               | Call in a manager when the client is ready to buy |
| [amoCRM](/documentation/documentation-en/integrations/amocrm.md), [Bitrix24](/documentation/documentation-en/integrations/bitrix24.md), [HubSpot](/documentation/documentation-en/integrations/hubspot.md) | Deal and history in CRM                           |

**Example task:** “Find out the budget and deadlines, offer a suitable plan, collect the phone number and name, and when ready, send a payment link or hand off to a manager.”

## Examples

**Online store.** Catalog consultation 24/7, orders in [Telegram](/documentation/documentation-en/channels/messengers/telegram.md) or [WhatsApp\*](/documentation/documentation-en/channels/messengers/whatsapp.md), managers only on complex deals.

**Online school.** Answers about programs and prices, sign-up for a trial lesson, funnel in the CRM.


---

# 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://docs.athenachat.ai/documentation/documentation-en/use-cases/prodazhi.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.