The features required to create a use case will depend on the specific goal of the use case, such as whether it involves using an API. These goals are reflected in the use case types, which are also linked to our pricing model.
It's important to note that the type of use case is independent of the interface used to build it, whether simple or advanced.
Available Use Case Types
When creating a new use case, you can select a goal from the following list. The selected goal can be modified later if needed:
Type | Description |
|---|---|
Informational - Q&A | Designed for basic flows where a single question leads to a single answer. |
Informational - Connected | Flows aimed at providing the right information for a specific context, typically using external data from APIs. |
Advanced - Qualification | Flows that qualify complex requests before redirecting to a bot answer, agent handover, or ticket creation. |
Advanced - Actions | Flows intended to perform a business action for the user, such as updating personal information, booking a trip, or canceling a service. |
Advanced - Sales | Flows where the goal is to facilitate a purchase through the conversation with the bot. |
"No Type" Option
If you're unsure which type to select, you can choose the "No Type" option to begin designing your use case. You can always consult with your Customer Success Manager (CSM) to determine the best option for your needs.