Task
Understand the desired result and request conditions without replacing unknown information with assumptions.
Example scenario · Lead qualification
Preparing an enquiry for a productive conversation with a manager
An example for incoming service requests: the assistant clarifies the task, collects known conditions and passes the manager an enquiry with an explainable next step.
Scenario scope
Scenario scope
We start after a person expresses interest in a service. The task is to prepare useful information for continuing the conversation.
Solution
Configure brief clarification, answer-recording rules and routes based on enquiry content.
Expected effect
During the pilot, check whether the prepared enquiry lets the manager choose a next step without unnecessary repetition.
Solution architecture
Solution architecture
The conversation gathers facts, rules determine the route, and the manager makes individual commercial decisions.
Offer description
Agreed service areas, permitted terms and questions affecting the next step.
Clarifying needs
The desired result, starting situation, known constraints and parameters still to be established.
Sales handoff
An answer summary, explanation of the chosen route and open questions for the manager.
From interest to the next step
An unknown budget or deadline can remain a question; people do not need to invent answers to finish a form.
- 01
Initial request
Record the task of interest and conditions the person has already stated.
- 02
Key clarifications
Ask questions that actually help choose the service area and continue the conversation.
- 03
Checking understanding
Briefly restate the request and let the person correct or add to the answers.
- 04
Selecting a route
Apply agreed content-based enquiry rules and show the reason for the next step.
- 05
Handoff to a manager
Transfer confirmed information and unresolved questions through an available method.
Implementation stages
Implementation stages
We discuss clarification rules with those who receive enquiries and prepare proposals.
01
Assessment
Compare incoming request examples and identify what managers need to know to continue.
02
Architecture
Agree on field meanings, required and optional questions, statuses and routes.
03
Pilot
Test incomplete answers, changed conditions, a manager request and an enquiry outside the selected area.
Test criteria
Test criteria
Qualification should explain an enquiry's state rather than attach an unsupported judgment to a person.
- 01
Information accuracy
The enquiry reflects stated conditions; unknown information does not become a refusal or negative answer.
- 02
An explainable route
The next step follows an agreed rule and is supported by the conversation.
- 03
Usefulness for the manager
The recipient sees the need, selection criteria and questions from which to continue.
Explore the topic
How to qualify an incoming request without losing its meaning
The person has already shown interest in a service
Imagine a company with several service areas. An incoming request may be detailed or simply say, “We want to solve this task; what would you suggest?” The manager needs to understand the starting situation, desired result and known conditions. In this example, the assistant prepares that basis for conversation without replacing discussion of an individual proposal.
This concerns people who initiated contact or agreed to continue a conversation. Mass messaging and independently finding contacts are outside the example. Qualification here means clarifying the enquiry and choosing the next step. It does not promise to predict who will buy or assess a person's value from incomplete information.
First decide what the manager needs to know
Base the questions on the sales team's actual tasks. For example, which result the customer needs, how the process works now and which systems are already used. For each question, explain how its answer affects the next step: choosing a specialist, preparing an example or arranging a separate discussion. A field collected merely out of habit and never used may be unnecessary.
The meaning of an answer also needs agreement. A preferred start date and final delivery deadline are different facts. A budget indication differs from an approved project budget. If the person does not yet know a parameter, record that. A missing answer must not automatically become a negative indicator: the manager needs to understand uncertainty, not receive a seemingly complete questionnaire.
The conversation should not feel like a repetitive form
The assistant starts with the existing context and asks brief questions appropriate to the conversation. If the person already described the current process and desired result, there is no need to ask again. For ambiguous wording, explain which detail needs clarification. “Integration”, for example, may mean retrieving information, writing results or exchanging data in both directions.
The person may ask about the service during clarification. An answer based on approved materials helps them decide whether further discussion fits. Then return to any remaining question while retaining earlier answers. A direct request for a manager follows a separate route. Collecting more detail must not obstruct a conversation with a specialist.
How to separate a need from a proposed solution
A customer may name a specific tool even though the described problem concerns a wider process. Retain both the preference and underlying need in the enquiry. For example, someone wants a messenger assistant so employees can more conveniently obtain information from internal files. The interface is a preference; access to the information is the desired result.
The assistant does not confirm technical compatibility or scope from a service name alone. Those details require separate checks. The summary can record existing tools and required actions while leaving an unconfirmed connection as a question for the manager. This allows alternatives to be discussed without making the customer think a specific solution has already been promised.
Why the selected route should be explainable
After clarification, an enquiry can go to the appropriate specialist or remain for further review. Routing criteria are defined in advance and tied to actual answers. For example, a request explicitly requires internal document work or discusses hosting on the customer's infrastructure. The reason should be clear to the receiving employee, who can check it against the conversation.
This example uses no invented purchase-probability percentage. If the company needs statuses, agree on each one's meaning separately. “Needs clarification” differs from “outside the selected area”, and no budget differs from refusing to discuss a project. A status helps organise work only if it does not conceal these distinctions.
What happens when answers change
During the conversation, someone may recall an important restriction or correct an initial deadline. The assistant should update the current summary and reconsider the route if needed. Otherwise, the manager receives an outdated request even though the necessary information has appeared. Show the user a brief final statement and let them confirm or correct it.
Returning to an enquiry later requires rules for saved context. Distinguish information from the previous conversation from what changed now. Continuation depends on the interface, identification and permissions. Do not promise recognition across every channel or merge enquiries solely because answers are similar.
What information reaches the manager
The final record should help prepare a productive conversation. It can separate the need, current situation, selection criteria and open questions. Customer wishes remain wishes, and confirmed constraints remain constraints. The assistant must not add unconfirmed readiness to sign a contract, the speaker's authority or consent to proposed terms.
Discuss CRM or other tool transfer according to available interfaces and required fields. Check record creation or updates, answer retention and repeat submission handling. If the system does not confirm the operation, the status must not report successful transfer. The manager and user need a clear next step, not merely a formally closed conversation.
How to assess the pilot and prepare a brief
Choose enquiries with varying certainty: detailed, short, with conflicting dates, without a budget and outside the selected area. Separately test answer corrections and a request to speak directly to a person. The manager compares the result with the original conversation and notes which details helped, which were lost and which questions were unnecessary.
To discuss implementation with ASK ARMONIVO, prepare anonymised enquiry examples and explain what is needed before the first substantive conversation. You can show the existing record format and sales routes. After clarifying scenarios, fields, rules and connections, scope and price are determined. Assess pilot results against your process rather than replace them with a conversion promise made in advance.
Questions and answers
Key points
01Is this a real sales-team case study?+
No. It is an example of preparing an enquiry. It does not substantiate a particular company's results or sales growth.
02How does it differ from receiving a website enquiry?+
Intake records the question and contact details. This example examines needs, selection criteria, uncertain parameters and next-step rules in more depth before a manager's conversation.
03Must the person state a budget?+
No. An unknown parameter can remain a question for later discussion. Define required information around the task without forcing someone to invent an answer.
04Will the assistant estimate purchase probability?+
That prediction is outside the described scenario. Enquiry routes and statuses are determined by agreed rules applied to the conversation.
05Can previously stated conditions be corrected?+
Yes, the conversation should allow this. The final summary and next step must reflect the confirmed clarification.
06Can the customer go straight to a manager?+
In this example, requests for a specialist are handled separately. Additional questions must not obstruct the provided handoff.
07Does the assistant promise a specific integration or price?+
It can communicate only approved information. Individual pricing and technical compatibility require separate discussion and checking.
08What is needed to estimate this implementation?+
Incoming request examples, the information managers need, routing rules and tools used. After clarifying them, scope and cost are calculated.
Discuss your project
Let's define what matters before the conversation
Show us example enquiries and explain which information helps the manager choose a next step. We will discuss clarification and handoff.
Discuss your project