---
title: "Virtual agents"
slug: "virtual-agents"
description: "Set up a SIP based Virtual agent that joins dialer campaigns, manages calls (answer, transfer, conference), and is included in recordings and reports with no softphone required."
updated: 2026-04-30T09:51:20Z
published: 2026-04-30T09:51:20Z
canonical: "docs.voiso.com/virtual-agents"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voiso.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Virtual agents

**Who should read this article**: Administrators

Set up a SIP based Virtual agent that joins dialer campaigns, manages calls (answer, transfer, conference), and is included in recordings and reports with no softphone required.

          Note

    

The **Virtual agent** feature is available for contact centers on the Pro plan or higher.

## Introduction

A Virtual agent is a SIP based calling user that behaves like a live agent in your contact center. It can answer and transfer calls, join three way conferences, send and receive DTMF, and participate in dialer campaigns without using **Agent Panel**. All calls with a Virtual agent are recorded and included in [real time](/v1/docs/reporting-real-time-dashboard-overview) and [historical reports](/v1/docs/reporting-historical-reports-overview), so operations and [analytics](/v1/docs/speech-analytics) work the same way as with [Standard Users](/v1/docs/users-users).

### Choosing the user type

When creating a user, an admin can choose either [Standard User](/v1/docs/users-users#standard-users) or Virtual agent. Standard Users have configurable permissions and privileges that you can tailor to each role. Virtual agents have a fixed set of capabilities that are enabled by design, including manual outbound calls, click-to-call, and external transfers. Because Virtual agents connect through a SIP URI and do not sign in to **Agent Panel**, they do not require statuses or presence to participate in [routing](/v1/docs/flow-builder-route) or [Dialer campaigns](/v1/docs/outbound-dialer-campaigns-overview).

### Prerequisites for creating a Virtual agent

- The Virtual user feature is enabled for the contact center in the Pro plan
- The [queues](/v1/docs/inbound-queues), [skills](/v1/docs/users-skills), and [teams](/v1/docs/users-teams) you plan to assign to the Virtual agent
- The speech language to use if [Speech Analytics](/v1/docs/speech-analytics) is enabled

Note

- If a virtual agent does not respond within two seconds the call is terminated automatically.
- Each virtual agent may only handle one call at a time, whether inbound, outbound, or click-to-call.

## Adding a virtual agent

To add a single virtual agent, follow these steps:

1. From the Voiso main menu, navigate to **Users > Users**.
2. Click **Add user**.
3. In the **Add user** dialog, choose **Virtual agent**, then click **Continue**.  

![Users Add User Select Standard User Or Virtual Agent](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Users%20Add%20User%20Select%20Standard%20User%20Or%20Virtual%20Agent.png)
4. The **Add virtual agent** page is displayed.  

![Users Add Virtual Agent View](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Users%20Add%20Virtual%20Agent%20View.png)
  1. In the **General** section, enter the following information:
    1. **Name**: A unique name for the virtual agent.
    2. **SIP URI**: A SIP URI from your bot provider in the format `sip:user@domain[:port]`.
    3. **Extension**: An internal extension for transfers and routing purposes.
  2. (Optional) In the **Assigned teams** section, click **Manage**, then assign the virtual agent to one or more [teams](/v1/docs/users-teams).
  3. (Optional) If the virtual agent will handle inbound calls and your contact center uses skills-based writing, then in the **Assigned skills** section, click **Manage**, then assign [skills](/v1/docs/users-skills) to the virtual agent.
  4. (Optional) If the virtual agent will handle inbound calls, then in the **Assigned queues** section, click **Manage**, the assign the virtual agent to one or more inbound queues.
5. Click **Save**.

## Adding bulk virtual agents

When you are ready to add multiple virtual, as well as standard, agents to you contact center you can import a CSV containing agents of both types.

To get started, [download the user CSV template](/v1/docs/users-users#user-template-with-security-access-groups) from the **Users** page. The template contains sample users to get you started. Just delete them and add your own standard users and virtual agents.

Note

The CSV template contains all parameters used to configure both standard users and virtual agents: however, only certain parameters are used for virtual agents. If you add parameters that are not supported for virtual users, the unsupported parameters will be ignored. For details about bulk importing users, refer to [Bulk User Account Management](/v1/docs/users-users#bulk-user-account-management).

Use the following information to guide you to set up your CSV file.

**Virtual agent parameters**

  

| Parameter | Example Value | Required | Notes |
| --- | --- | --- | --- |
| Name | Support Bot | Yes |  |
| Type | Virtual | Yes |  |
| SIP URI | sip:supportbot@sip.provider.com:5060 | Yes | Must follow the format sip:user@domain[:port]. |
| Email |  | No |  |
| Password |  | No |  |
| Sip account |  | No |  |
| Access Group |  | No |  |
| Extension | 0666 | No | Used for internal transfers within the contact center. |
| CallerID |  | No |  |
| CTI |  | No |  |
| Timezone |  | No |  |
| Queues | First queue;Second queue | No |  |
| Skills | Speaking: 1;Learning: 1 | No |  |
| Teams Supervisor |  | No |  |
| Teams Agent |  | No |  |
| WebRTC Ringtone |  | No |  |
| Speech language | en_us | Yes | Use ISO standard language and country codes. |
| Allow Manual Outbound Calls |  | No |  |
| Enable Answering Machine Detection |  | No |  |
| Allow Feature Access Code |  | No |  |
| WebRTC Enabled |  | No |  |
| SMS Enabled |  | No |  |
| Call Notes Enabled |  | No |  |
| Replace client numbers with Acc IDs |  | No |  |
| Enable selective recording |  | No |  |
| Dashboard Number Masking |  | No |  |
| Disable recordings download |  | No |  |
| Click-to-call Client Number Masking |  | No |  |
| Allow click-to-call |  | No |  |
| Allow CDR Downloads |  | No |  |
| Allow HLR Lookup requests |  | No |  |
| Allow external transfers |  | No |  |
| CDR enabled |  | No |  |
| Historic report enabled |  | No |  |
| Speech recognition enabled |  | No |  |
| Omnichannel Workspace Enabled |  | No |  |
| Enable Mobile application |  | No |  |
| Enable access to support chat |  | No |  |
| Channels |  | No |  |
| Instant Messaging Capacity |  | No |  |
| Webchat Capacity |  | No |  |
| WhatsApp Outbound Numbers |  | No |  |
| Viber Sender IDs |  | No |  |
| 2FA Enabled | n | N |  |

## Speech Analytics

If [Speech Analytics](/v1/docs/speech-analytics) is enabled in your contact center, the **Speech language** menu is included on the **Add virtual agent** page. The first available language from the enabled languages is selected by default. Use the menu to select the language to be used for speech analytics.

![Users Add Virtual Agent Speech Analytics View](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Users%20Add%20Virtual%20Agent%20Speech%20Analytics%20View.png)

## Assign to, route to, and report on virtual agents

Virtual agents are bot platforms that connect to Voiso through a SIP URI and appear alongside standard users in the product. You can assign virtual agents, route interactions to them, and include them in analytics just like any other user entity. To make this clear across the application, Voiso displays a consistent visual indicator wherever virtual agents can be selected or where their activity is shown.

This section explains how different Voiso interfaces handle virtual agents, including where you can assign them, how routing and distribution treat them, and how their activity appears in real time dashboards, historical reports, extended interaction records, skills, queues, dialer campaigns, and others.

### Teams, Skills, Queues

Virtual agents may be assigned to [teams](/v1/docs/users-teams), [skills](/v1/docs/users-skills), and [queues](/v1/docs/inbound-queues). In the **Agent assignment** panel of the respective interfaces, human and virtual agents are easily distinguished from one another:

![Users Virtual Users Assignment](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Users%20Virtual%20Users%20Assignment.png)

### Flow builder

You can route calls to a Virtual agent in [Flow builder](/v1/docs/inbound-flow-builder-overview) using the **[Route](/v1/docs/flow-builder-route)** node. From the **Route to** menu, select one of these destinations:

- **SIP URI**: Send the call directly to the SIP address configured on the Virtual agent’s profile.
- **Virtual agent (by name)**: Select the Virtual agent from the user list.
- **[Queue](/v1/docs/inbound-queues)**: Route to a queue that includes the Virtual agent; the call is offered according to your queue’s routing rules.

Note

Virtual agents do not sign in to **Agent Panel**. If the Virtual agent is already on a call, the flow follows your queue and overflow logic. If there is no response from the bot within two seconds, the call is ended automatically.

### Dialer campaigns

Virtual agents may only be assigned to one [Dialer campaign](/v1/docs/outbound-dialer-campaigns-overview) at a time. Calls are directed to virtual agents when they complete a call.

![Users Dialer Campaigns Virtual Users Assignment](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Users%20Dialer%20Campaigns%20Virtual%20Users%20Assignment.png)

In the **Agent assignment** panel of the **Add Campaign** view, human and virtual agents are distinguished from one another in the **Type** column.

### Click-to-call

You can create an application that uses the Voiso API [Startcall](https://developers.voiso.com/reference/startclicktocall#/) and [Stopcall](https://developers.voiso.com/reference/stopclicktocall#/) endpoints to initiate calls to your virtual agent bot. Your bot must have an extension that the Endpoint uses to connect the call to the bot.

### Reporting

Virtual agent activity appears in reporting in the same way as standard users, with a clear visual indicator to help you distinguish between them. In **Extended call details**, Voiso shows when a virtual agent participated in or handled an interaction. In the **real time dashboard**, widgets such as Agent list and related performance views include virtual agents so you can monitor their live workload and outcomes. In **historical reports**, virtual agents are listed alongside other users, and their metrics are aggregated using the same logic as agent metrics, making it easy to review bot performance over time.

#### Extended Call Details

Virtual agents are shown as the **Agent/Supervisor** of voice calls in the [Extended Call Details: Voice](/v1/docs/extended-call-details-voice) just like standard users.

In the **Call recording** and **Transcript** sections, virtual agents are indicated both by a label and a "robot" icon.

![Reporting Extended Call Details Voice Virtual Agents](https://cdn.document360.io/44ae307a-3737-4fbf-98e0-9b888deb90dc/Images/Documentation/Reporting%20Extended%20Call%20Details%20Voice%20Virtual%20Agents.png)

#### Real-time dashboard

Virtual agents are supported in the following [real-time dashboards](/v1/docs/reporting-real-time-dashboard-overview) widgets:

- [Agent List](/v1/docs/reporting-agent-list-dashboard): The **Agent type** column indicates whether an agent is **Virtual** or **Standard**.
- [Agent Zoom](/v1/docs/supervisor-workflows-agent-zoom): As with the Extended Call Details view, virtual agents are indicated  both by a label and a "robot" icon.
- [Redial Counter](/v1/docs/reporting-redial-counter-dashboard): The **Agent type** column indicates whether an agent is **Virtual** or **Standard**.
- [Talk Time/Unique Clients](/v1/docs/reporting-talk-time-unique-clients): Tooltips on the graph indicate whether an agent is **Virtual** or **Standard**.

#### Historical reports

Virtual agents are supported in the following [historical reports](/v1/docs/reporting-historical-reports-overview):

- [Agent List](/v1/docs/reporting-agent-list)
- [Agent List - Per Hour](/v1/docs/reporting-agent-list-per-hour)
- [Agent - Daily Sign-in and Sign-out](/v1/docs/agent-daily-sign-in-and-sign-out)
- [Redial Counter](/v1/docs/reporting-redial-counter)
- [Keyword Groups](/v1/docs/keyword-groups-report)
- [Sensitive Data Access Report](/v1/docs/reporting-sensitive-data-access-report)
- [Billing Unit](/v1/docs/billing-unit)

In the **Agent assignment** panel of the **Add report** view, human and virtual agents are distinguished from one another in the **Type** column.

In the reports' **Assigned agents** or **Assigned users** sections, human and virtual agents are grouped in separate **Standard agents**, **Standard users**, and **Virtual agents** subsections.

In generated reports and CSVs, depending on report type, either an **Agent type** or **User type** column is added to the report.

Dual Tone Multifrequency. A system that uses audio tones to represent digits on a keypad. When a person presses the numbers on their phone to dial a number or make a selection in an IVR, they are sending DTMF audio tones to the phone system.

A SIP URI (Session Initiation Protocol Uniform Resource Identifier) is a unique address to locate and communicate with endpoints in a SIP-based contact center. It is similar to a URL (Uniform Resource Locator) used on the world wide web. SIP URIs allow SIP endpoints to locate and connect with each other.

A complete SIP URI looks similar to an email address, with the user part followed by the at symbol "@" and the domain part. For example, "alice@example.com" or "+15551234567@sip.provider.com"

## Related

- [Users](/users-users.md)
- [Queues](/inbound-queues.md)
- [Skills](/users-skills.md)
- [Teams](/users-teams.md)
- [Route](/flow-builder-route.md)
