- Getting started
- UiPath Agents in Studio Web
- UiPath Coded agents
Agents user guide
Conversational agents
Conversational agents are a new class of UiPath agents designed to engage in dynamic, multi-turn, and real-time dialogues with users. Unlike autonomous agents that respond to a single prompt, conversational agents interpret and react to a continuous stream of user messages. They manage conversation context, tool execution, human escalations, and memory, enabling a richer, more adaptive automation experience. Think of them as intelligent digital assistants that understand context and handle ambiguity naturally.
Conversational agents are particularly useful for scenarios that require:
- Ongoing clarification or back-and-forth exchange
- Personalized guidance based on user intent
- Seamless human fallback when confidence is low
Table 1. Key differences from autonomous agents
| Feature | Conversational agent | Autonomous agent |
|---|---|---|
| Interaction model | Multi-turn, back-and-forth dialogue | Single-turn, task execution based on an initial prompt |
| Primary use case | Real-time user support and assistance, interactive information gathering | Executing a task from a defined prompt |
| User input | Continuous user chat messages | Single structured prompt |
| Core strength | Maintaining conversation and handling ambiguity | Executing a plan across tools |
When to use conversational agents
Use conversational agents when your automation scenario involves real-time, context-aware interaction. These agents are best suited for:
- Self-service experiences for customers or employees, such as helpdesk support or onboarding assistants.
- Interactive guidance through multi-step processes, forms, or decision trees.
- Contextual conversations where users may ask follow-up questions or provide information incrementally.
- Natural language interfaces for applications, systems, or knowledge bases, allowing users to query information conversationally.
Use autonomous agents instead when the task can be fully described in a single prompt with all required inputs provided upfront. Ideal examples include:
- Structured document processing (e.g., extracting data from invoices or contracts)
- Automated report generation based on predefined logic
- Summarization or transformation tasks with clear, one-shot requirements
Conversational agents versus Autopilot
How do conversational agents relate to Autopilot for Everyone?
With several chat experiences available, it's important to know which one to use and when.
Conversational Agents vs. Autopilot for Everyone:
- Working together: These two experiences work side-by-side. Conversational agents are not a replacement for Autopilot for Everyone.
- Different purposes: Think of Autopilot for Everyone as UiPath's general-purpose agent, optimized for productivity tasks and interacting with the UiPath platform. Conversational agents are specialists that you build for a specific use case (e.g., an HR policy assistant).
- Access: You can access your specialized conversational agents directly from within Autopilot for Everyone, making it a central hub for all your conversational needs.
Conversational Agents vs. specialized Autopilots:
- Overlap: Both are designed for use-case-specific purposes.
- Our recommendation: We recommend building with conversational agents. They provide a much richer and more robust design-time experience for building, testing, and refining your use-case-specific agent.
- Key difference: Conversational agents do not currently support local desktop automation, whereas specialized autopilots do.
Licensing for conversational agents
Conversational agents use the same consumption-based model as other UiPath services. Each user message is measured as an action and draws from the organization’s available Agent Units or Platform Units, depending on the licensing plan. External users can interact with agents without a named license, with usage automatically deducted from the tenant’s consumption pool.
Standard consumption model
- Action definition: Each user message sent to a conversational agent counts as one action.
- The cost per action depends on your licensing plan:
- Flex: One action consumes one Agent Unit.
- Unified Pricing: One action consumes 0.2 Platform Units.
- Additional units may be consumed depending on the type of tool executed. Please refer to the tool consumption table below.
- Actions are not consumed for prompts with eight (8) characters or fewer that don’t execute a tool.
- Chat interactions performed during design-time debugging consume from your daily design-time LLM call allotment. One LLM call equates to one user message.
Unlicensed access for external users
The unlicensed access path applies to both licensing plans and is designed for public-facing or anonymous users.
- Intended use: External and anonymous users, such as public-facing chatbots on websites, portals, or custom applications.
- Deployment options: IFrame in UiPath Public Apps, or external apps and SDKs (Headless or UI).
- Licensing and consumption:
- No user license is required.
- Requires an external application token, created in the Admin portal.
- Actions consume units from the tenant’s Agent Unit or Platform Unit pool starting with the first user message.
- Capabilities:
- Full conversational functionality is supported.
- Tool execution may require additional licensing, such as Unattended Robot licenses.
Flex licensing
The Flex licensing plan uses Agent Units for consumption and is based on the following license types for authenticated users:
| License type | Use case | Licensing and cost | Key capabilities |
|---|---|---|---|
Automation Express Autopilot Express | Designed for broad internal rollouts, enabling users to interact with Q&A chatbots or trigger simple, cross-platform automations. This license type serves as the default starting point for most users. | A free license for Enterprise customers. Includes 50 free actions per user, per year. After the free allowance is used, it consumes from the tenant's Agent Unit pool. | Allows full capabilities, except for running local Windows desktop automations via the user's attended robot. Allows user-level observability. |
Attended Citizen Developer Automation Developer | Intended for professional developers, power users, and large-scale attended automation programs. This option provides predictable costs and eliminates the need for consumption tracking. | Requires a paid user license. Includes unlimited usage (subject to fair use throttles, e.g., 500 prompts/day). | Allows full capabilities, including running local Windows desktop automations via the user's attended robot.1 Allows user-level observability. |
1 This feature is not currently available. Once released, it will be accessible to the license types mentioned above.
Unified Pricing licensing
The Unified Pricing licensing plan Platform Units for consumption and is based on the following license types for authenticated users:
| License type | Use case | Licensing and cost | Key capabilities |
|---|---|---|---|
| Express | Designed for broad internal rollouts, allowing users to use Q&A chatbots or trigger simple, cross-platform automations. This license type is the default starting point for most users. | A free license for Enterprise customers. Includes 50 free actions per user, per year. After the free allowance is used, it consumes from the tenant's Platform Unit pool. | Allows full capabilities, except for running local Windows desktop automations via the user's attended robot. Allows user-level observability. |
| Basic | Intended for authenticated power users and citizen developers who run local desktop tasks conversationally and prefer metered, predictable costs. | Requires a paid user license. Includes 50 free actions per user, per month. After the monthly allowance is used, it draws from the tenant's Platform Unit pool. | Allows full capabilities, including running local Windows desktop automations via the user's attended robot.1 Allows user-level observability. |
Plus Pro | Suited for professional developers, heavy users, and large-scale attended automation programs that require cost certainty and do not rely on consumption tracking. | Requires a paid user license. Includes unlimited usage (subject to fair use throttles, e.g., 500 prompts/day). | Allows full capabilities, including running local Windows desktop automations via the user's attended robot.1 Allows user-level observability. |
1 This feature is not currently available. Once released, it will be accessible to the license types mentioned above.
Tool licensing and usage costs
While most tool costs are included in the base action, certain advanced capabilities have specific licensing or consumption requirements regardless of your licensing plan.
| Tool / capability | Licensing and consumption requirement |
|---|---|
| Analyze Attachment | Consumes one Agent Unit / 0.2 Platform Units. |
| Integration Service activity tools | Included in the base action cost. |
| Basic Context Grounding | Included in the base action cost. |
| Context Grounding: advanced ingestion and DeepRAG | Charged as per the existing pricing mechanism for those services. |
| Cross-Platform automations | Consumes 1 Agent Unit (and Robot Units) / 0.2 Platform Units. |
| API workflows | Consumes 0.1 Agent Unit / 0.02 Platform Units for each Integration Service connector executed inside the workflow. |
| Running autonomous agents | The nested agent's execution consumes its own Agent / Platform Units. |
| Running Maestro workflows | The nested agent's execution consumes its own Agent / Platform Units. |
| Running Windows automations (Unattended) | Requires an Unattended Robot to run on a separate machine. |
Bring your own model
Currently, conversational agents are available only with UiPath-managed models. Support for integrating your own models will be introduced in a future release.
