“We want to automate everything” sounds energetic, but gives the implementer many ways to interpret “everything.” The owner has just as many ways to be surprised by the result.
A useful description starts with an ordinary working episode. You do not need server knowledge for an initial discussion. Explain what happens today and what should change for people.
Tell the story of one inquiry
In a hypothetical example, a buyer requests an estimate, a salesperson clarifies measurements, a specialist prepares a proposal, and the customer asks more questions. Mark where work waits for a person or information is copied manually.
Then answer five questions: what starts the work, which data arrives, who takes the next step, which outcome is expected, and where it is checked.
“The CRM will handle everything” is a wish. “After measurements are confirmed, the owner gets an estimate task linked to the source information” is a scenario to discuss.
Add the awkward cases
The system needs more than the perfect order. What happens when information is missing, the customer changes their mind, the owner is absent, or the same inquiry arrives twice?
Identify decisions that require a person. Automation should not guess an undocumented discount rule or disputed work scope.
A company in Kazakhstan should specify working languages and document formats. Do not present an employee’s habit as a legal requirement; check legal conditions separately when relevant.
Where AI can help
AI, or artificial intelligence, can edit a draft: organise an anonymised description, flag gaps, and propose questions for agreement. It should not become the unchecked author of business rules.
Do not send customer data, passwords or internal documents to an unapproved service. For a training example, replace real names and amounts with placeholders and check the tool’s rules.
In Bitrix24, BitrixGPT can help structure task descriptions, as the official task instructions show. Check AI availability and limits for the particular portal. A well-written description still needs employee review.
Turn wishes into an observable outcome
Write a short acceptance scenario: enter a training inquiry, confirm conditions, then check the assignee and task contents. Describe a separate expected outcome for an exception.
The absence of unwanted actions matters too. Repeated confirmation should not create uncontrolled extra assignments. Errors should be visible to someone able to fix them.
Separate the essential first outcome from future ideas. Otherwise accounting, a website, and “one tiny report” quietly attach themselves to a small assignment.
What to bring to a first meeting
One anonymised example, a participant list, current programs, and an explanation of how you will judge improvement are enough. Scope and timing are assessed after boundaries are clarified, rather than from polished AI text.
QQDev starts projects by examining the process and agreeing how to check results. Use the home page to discuss a task without a finished technical brief or an existing Bitrix24 installation. A clear starting story leaves fewer guesses in the future solution.