Marketing reports a batch of new leads. Sales opens the conversations and finds a mix of potential buyers, job seekers and people asking about a service the company does not sell. Calling the whole batch "good" or "bad" hides what needs to change.
To qualify Telegram leads, review the original request and the next step. Your team needs a shared definition of a useful inquiry before it needs a complicated scoring system.
Agree what makes an inquiry relevant
Start with the offer. Which problem do you solve, for whom and under what conditions? A useful inquiry should have enough connection to that offer for someone to continue the conversation.
For an illustrative business selling commercial equipment, the intended use might matter more than an immediate budget figure. For another offer, geography may rule a request out early. Choose criteria that reflect the sale you actually make.
An incomplete inquiry is not automatically irrelevant. Put it in a separate category when a person could clarify the missing information.
Use reasons a person can act on
Replace "poor-quality lead" with a specific reason. This makes the review useful to whoever changes the campaign or handles the response.
| Observation | What to check next |
|---|---|
| The person needs another service | Audience selection and offer wording |
| Important context is missing | Questions in the scenario |
| A suitable request received no follow-up | The handoff and sales process |
| The person is interested but not ready | The agreed next step and timing |
Keep the categories separate. A request that went unanswered tells you something different from a request that never matched the offer.
Preserve the conversation for the handoff
The next person needs to know what was asked and what has already been said. Include the source, the problem, any agreed conditions and the next action. A note that merely says "interested" forces sales to repeat the opening questions.
Use one record for the inquiry, even if it contains several messages. If the person returns, update the same record rather than counting a second new lead for the same conversation.
Review the role of the AI agent
An AI-assisted scenario should gather or explain the information your process needs, using facts the company can support. It should handle missing information without inventing an answer and stop when the question needs a person.
In KUZKO, use conversation history to inspect the scenario in context. A confident sentence may look convincing alone and still be the wrong reply to the previous message. Review the thread, then adjust the business brief or the response boundaries that caused the problem.
Do not assume that the presence of an AI agent also means there is a built-in lead-scoring model or a CRM connection. Verify the workflow you need in the product.
Make the review a decision, not just a report
Group the reasons after reviewing a batch. If unsuitable requests repeat, revisit the audience or offer. If relevant requests stall after a handoff, fix the follow-up process before buying more activity.
Use the lead generation workflow to connect the stages. When comparing campaigns financially, distinguish a qualified inquiry from a customer in the CPL and CAC calculation.