A lead qualification bot collects information that helps route an inquiry to the right person and prepare for the conversation. Its task is to establish the customer's needs, conditions and next step.
Start with the manager's decisions: which answers change the inquiry's route, and which can be clarified later. If a question does not affect the next action, it usually does not need to be part of the mandatory dialogue.
Document the criteria together with the sales team. For a service, these might include the task, market, available scope of work and timing. For a wholesale order, they might include the product category, volume and ability to supply it.
Distinguish three states:
An unspecified budget does not mean a lack of money, and an urgent deadline does not mean readiness to buy. Do not turn a single answer into a final decision without context. If the problem starts with an advertising promise, review it alongside lead quality in Meta Ads.
A basic dialogue can cover the following topics:
Explain why you ask a question the customer may find sensitive. For example: “An indicative budget helps us suggest a suitable scope of work.” Do not promise an exact price based on a few answers if estimating requires reviewing the project.
A phone number should not be assumed to be automatically available from the profile. In Telegram, a contact request button shares the number after the user presses it and works in private chats. Bot API documentation.
If a customer selects support for an existing website, they need questions about the platform and problem. For a new website, goals, materials and languages matter more. One long questionnaire for all services forces people to answer irrelevant questions.
Provide options to go back, change an answer, cancel and contact a staff member. For an unusual task, save the description and pass it to a person rather than forcing the customer to choose an incorrect category.
For an unsuitable request, explain the specific limitation and offer an available next step. An automatic rejection should follow a verifiable business rule. Do not hide an inquiry simply because the bot gave it a low score.
Transition logic and exceptions can be documented in a Telegram bot specification.
A company accepts website inquiries. This example illustrates the dialogue structure, rather than a universal number of questions.
An inquiry without a budget is sent for clarification. A request with a fixed deadline that the team has not checked is marked “Timing needs agreement.” The bot confirms receipt of the inquiry but does not promise a launch by that date.
An inquiry record should usefully retain:
Do not replace the customer's answers with a short AI summary without providing access to the original text. The manager needs to understand which information the person supplied and which the system inferred.
Check what happens when the CRM is unavailable: where the inquiry is saved, who sees the error and how it is transferred again without duplication. The connection between inquiries and later outcomes is explained in the article on tracking advertising and sales in a CRM.
Track how many people start and complete the scenario, which questions they stop answering and how many request a staff member. An unfinished dialogue alone does not prove the inquiry was unsuitable.
Assess quality after a manager reviews the inquiries: the proportion that are suitable, reasons for clarification and incorrect rejection, and progression to discussions and sales. Use consistent criteria and periods for comparisons, accounting for the delay before a deal closes.
If the bot increases the proportion of suitable inquiries but loses some relevant customers, revise the questions and routing rules. Do not choose a stricter filter simply to make a metric look better.
To discuss Telegram bot and Mini App development, prepare inquiry criteria, question branches and the staff handover procedure. The commercial proposal provides a basis for agreeing on scenarios and integrations; approve the qualification rules with the sales team.