Ada empowers support to manage knowledge, scripts, and rules of human turn referrals.
When an employee is needed
The reference agent can answer according to the approved rules, while the question fits into the knowledge base. If the user describes an exception or directly asks for a person, you need a pre-configured transition. In Ada, transmission rules are set in the workspace. Specify which channel, queue and opening hours are used so that the agent can give an understandable continuation of the conversation.
Two runs instead of one dialogue
In the fictional store published the usual conditions of return, but the delivery of large goods requires clarification. Check first a simple request for a deadline. Then ask about returning the goods with non-standard delivery and make sure that the conversation comes in a suitable queue. An employee should see the context that he is supposed to see. When testing, use fictitious data and do not include payment information in the script text.
Repeat the same request in a closed queue. If a live response is not available, it is important for the user to get an understandable next step. Separately, check that the agent does not promise a specific period if such a period is not specified by the rules.
What to check after changing the base
The new instruction can change which responses are considered reference and when transmission is required. Take a few requests from the control set and repeat them after editing. Compare sources and route. If the answer looks plausible but disagrees with the internal rule, find out what material is used before changing the general behavior setting.
Suitable tasks
- Check the exit from the reference script.
- Sets the exception request to be transmitted.
Strengths
- Works with an connected knowledge base.
- There are separate rules for transferring employees to the queue.
Limitations
- Channel and queue reception require integration setup.
- The quality of the answer depends on the materials and regulations in force.
Selection and conditions
- Free access
- Not confirmed
- Trial period
- Not confirmed
- No sign-up required
- Not confirmed
- Russian interface
- Not confirmed
- Local installation
- Not confirmed
- API
- Not confirmed
“Not confirmed” means there is not enough information. The feature may still be available; check the developer’s terms.
- Input formats
- Text, Document
- Result
- Text
Terms
Connect the allowed base and check the behavior when the queue is closed.From task to first result
Practical example
- Task
- Check the exit from the reference script.
- What to prepare
- Authorized test article about the return of the order. The text indicates the deadline for ordinary purchases and a separate exception.
Task brief or prompt
Prepare a reference answer for your regular purchase. Then, in a test conversation, describe the case that is not in the reference and check the transmission of the request to the person.
Expected result
A draft answer from the instruction and an understandable continuation for the treatment that the employee requires.
How to check the result
- Find the rule and exception in the article.
- Make sure that the answer does not promise to return funds or change the order without authority.
An editorial teaching example of a task brief, not the result of hands-on testing of the service. Check that the required mode is available, that you have rights to the source material and that the intended use of the result is permitted.
Check details
Official sources
This description is based on the developer’s material. Features, prices and availability may change; check the primary source before use.
