The hardest part of setting up an AI agent is often the first paragraph of the brief. "Find customers and sound professional" feels clear until you need to judge an actual reply. Which customers, which facts and what should happen next?
Before configuring a Telegram scenario in KUZKO, prepare a short description your own team could use. It will make the generated wording easier to review and give you something concrete to correct.
Prepare a business brief
Describe the offer in plain language. Include who it helps, the problem it addresses and the conditions that matter to a potential customer. Remove old offers and claims you cannot confirm.
Separate known facts from details that require a person. If pricing depends on a consultation, the scenario should explain the next step instead of inventing a quote. The same applies to availability and delivery conditions.
Use the audience research checklist to describe the situation the campaign will address. A broad job title rarely gives an agent enough context for a useful conversation.
Define one purpose for the scenario
Choose the next action you want to support. It could be clarifying the person's task or inviting an appropriate inquiry. Write down how you will recognize a suitable response.
Keep the first scenario narrow enough to inspect manually. You can add a different offer or audience later, with its own brief. Combining them immediately makes it harder to identify which assumption caused an awkward reply.
Work through the KUZKO preparation flow
KUZKO / Black Bull provides a workspace for business context, Telegram AI agents and advertising scenarios. Start with the business description in the onboarding flow, then review the prepared context and scenario rather than accepting the first draft unchanged.
Check that the agent's role matches your business, that it uses approved facts and that the wording belongs in the intended conversation. Controls and account access can depend on your workspace and current plan, so use the options actually available to you.
This guide describes the preparation sequence. It does not imply that KUZKO is a general-purpose bot builder or that every possible external integration is connected.
Test ordinary and awkward questions
Prepare examples your team controls before a real launch. Include a normal question, a request for conditions, missing information and a refusal. Add a question that the company itself cannot answer without checking.
For each response, note the exact issue. "Too robotic" is harder to fix than "repeats the offer after the person declines" or "states a delivery time absent from the brief".
Review how the process is stopped before starting it. Someone should know who owns the scenario and what to do when it needs correction.
Keep a small change record
Save the brief version, the purpose of the test and examples of the responses you reviewed. When product conditions change, check the scenario again. A fluent reply can become inaccurate simply because the offer is no longer current.
After launch, use conversation history to review context and adjust the instructions. The guides to marketing automation and lead quality cover the next decisions: which steps to repeat and how to assess the inquiries they produce.