Invorto Voice Bot – Feature Guide

Zaid Assadi

Updated 21 Sep 2026 | 05:54 PM

1. Feature Overview

Invorto Voice Bot is LeadSquared’s AI voice agent platform. It holds phone conversations for you, and it turns those conversations into structured data your team can act on.

Invorto has two products.

• Invorto Voice – You build a voice bot, then upload a contact list to a campaign. Invorto dials each contact and the bot runs the conversation.
• Invorto Insight – You upload recordings of calls your team already made. Invorto transcribes each recording and analyzes it. Insight campaigns do not place calls.

Both products end in the same place. Invorto produces a set of insights for every conversation, such as a call summary, the sentiment, the outcome, and the custom fields you defined.

Everything a call needs is bundled into your subscription: the telephony, the AI models, and the language and voice providers. You do not open separate accounts or hold separate contracts with those providers.

This article introduces the product and the portal. Each section points to the article that covers that area in full.

2. Prerequisites

• An active Invorto Voice Bot account. Your LeadSquared account manager sets this up for your organization.
• Creating bots, campaigns, phone numbers, users, and API keys are admin actions.
• A DID number registered from your telephony provider, if you plan to place or receive calls. See Phone Numbers.

3. Key Concepts

These terms appear throughout the Invorto portal and the rest of this documentation set.

4. How It Works

4.1 From Setup to Results

Running calls on Invorto follows the path below. The rest of this article covers each stage in the order you work through it.

1. Register the phone number your calls go out from, or come in on.
2. Build a voice bot: what it says, the AI model behind it, and the language and voice it speaks in.
3. Give the bot the reference content it answers from, and the tools it can use during a call.
4. Test the bot on your own phone, then publish it.
5. Create a campaign, select the published bot, and upload your contacts. Invorto queues each number and dials it.
6. Review the recordings, transcripts, and insights, and use them to improve the bot.

4.2 What Happens on a Call

Inside a single call, the bot works in four layers: it hears the contact, decides what to say, speaks the reply, and takes notes once the call ends.

1. Invorto dials the contact. The bot speaks the greeting message, with that contact’s values filled into the variables.
2. The contact replies. The bot converts their speech into text.
3. The AI model decides what to say next, based on your system prompt, your knowledge base, and any tools you attached.
4. The bot speaks the reply.
5. Steps 2 to 4 repeat until the call ends. Invorto then analyzes the call, generates the insights, and posts them to your webhook if you configured one.

5. Navigate the Portal

The left navigation is the same on every screen. You spend most of your time in Voice Bots, where you build the bot, and Campaigns, where you run it.

6. Register Your Phone Numbers

Before you can place or receive a call, Invorto needs to know which number to use. Register your DID numbers on the Phone Numbers page and set how each one routes calls.

For the fields on each direction, overflow handling, and where to copy the Phone Number ID, see Phone Numbers.

7. Build a Voice Bot

A bot stores everything a call needs, and a campaign supplies the contacts. Because the two are separate, you can improve a bot at any time without rebuilding your campaigns, and one bot can run any number of campaigns.

A bot has six setup tabs. Each one controls a layer of the call described in section 4.2.

The Call History and Version History tabs sit alongside the setup tabs. For the full configuration of every field, see Creating a Voice Bot.

8. Add Knowledge

The system prompt tells the bot how to behave. The knowledge base gives it the facts. Use it for content that changes independently of the bot, such as a product catalog, a price list, or a set of frequently asked questions.

Content is organized in two levels. A folder holds sources, and a source is a document you upload, a web page you point Invorto at, or text you type in directly. You add content from the Knowledge Base page, then connect it to a bot on the bot’s AI & Knowledge tab. Adding content to the knowledge base does not by itself change how any bot answers.

For folders, source types, and file limits, see Knowledge Base.

9. Add Tools

Without tools, a bot can only talk. A tool is a saved API call the bot makes in the middle of a conversation. The bot reads the live response and keeps talking with that information in hand. A bot can check open appointment slots and confirm a booking while the caller is still on the line, look up the status of an order and read it back, or send a payment link during the call.

Call Transfer moves a live call off the bot. You can transfer to a person or hand the call to another voice bot that specializes in a different topic. A warm transfer summarizes the conversation before connecting, so the person who picks up hears what was discussed. A cold transfer connects the call directly.

For the full setup, including parameters, secrets, response mapping, and transfer rules, see Create and Manage Tools and Call Transfers.

10. Run a Campaign

You select the campaign type when you create it, and the type decides what the rest of the wizard asks you for.

10.1 Invorto Voice Campaigns

A voice campaign dials a list of contacts with a bot you published. You select the bot, the outbound phone number, and the analysis configuration, then control the pace and the timing of the calls with a concurrency limit and a schedule. Invorto queues every number you upload and dials it when the calling window is open and a slot is free.

Once the campaign is running, you watch the queue move on the campaign page, and open any completed call to hear the recording, read the transcript, and review the insights.

See Create and Run a Voice Campaign.

10.2 Invorto Insight Campaigns

An Insight campaign analyzes conversations that already happened, so it skips most of the flow above. You still need a bot, because the analysis comes from that bot’s call insights configuration, but the campaign has no bot conversation, no outbound phone number, no contact list, and no calling schedule.

Select an Insights Config, then upload recordings or submit an audio URL. Invorto transcribes each recording, runs the same analysis it runs after a bot call, and adds the results to Insight Analytics.

See Create and Run an Insight Campaign.

11. Review the Results

Invorto reports on your activity at three levels: the organization, the campaign, and the individual call.

11.1 Dashboard

The Dashboard is the first screen you see after you sign in. It shows the minutes your organization has used, the cost accrued, the number of campaigns running, and your channel limit, along with the products enabled for you and your latest campaigns. See Dashboard.

11.2 Consumption

Consumption breaks the Dashboard totals down by product and by campaign. Use the Invorto Voice and Invorto Insight tabs to see how many calls each voice campaign placed and how many recordings each Insight campaign processed. See Consumption.

11.3 Voice Analytics

Voice Analytics shows the volume and shape of your calling activity over time: calls per day, minutes per day, cost per day, and the mix of call outcomes. It counts calls, it does not judge them. Insight campaigns do not place calls, so they do not appear on this page. See Analytics.

11.4 Insight Analytics

Insight Analytics aggregates the analysis Invorto runs after each conversation. Where Voice Analytics counts calls, Insight Analytics tells you what happened inside them: the outcome mix, the spread of call scores, the follow-up actions raised, the tone of the customer, and the issues that came up most often. Both products feed this page. See Analytics.

11.5 Evaluations

Evaluations scores how well your bots hold a conversation. Invorto samples completed conversations, scores each one against five quality dimensions, and combines those scores into a single composite score. A separate System Health panel runs deterministic checks on latency, call success, early drop-off, script boundaries, and silence or barge-in anomalies. Use it after a campaign has run to decide whether a bot is ready for a wider audience. See Analytics.

11.6 Call History & Logs

Analytics tells you how a campaign performed as a whole. Call History & Logs tells you what happened on one specific call. Every call your organization placed or received appears here, whether it came from a campaign, from Quick Call, from a test call, from the API, or from an inbound number. Use it to trace a single call, to work out why a set of calls did not connect, and to find the Call ID to quote on a support ticket. See Call History & Logs.

12. Manage Your Organization

12.1 Users

The Users module lists everyone in your organization along with their role and status. Admins add colleagues, copy a user’s identifier for a support ticket, and deactivate someone who has left the team. Deactivating a member removes their access without deleting their history, so the campaigns and bots they created stay in place. See Manage Users.

12.2 Settings

The Settings page holds the details that apply to your whole organization: a read-only snapshot of your plan and channel limit, the Members can see all campaigns setting, the API keys external systems use to reach Invorto, and an audit log of what has happened to those keys. See Organization Settings.

13. Connect Invorto to LeadSquared

The campaign flow above is one way to run calls. The other is to let your CRM decide when a call should happen, for example one day before a scheduled appointment. In the standard integration, the flow runs as follows.

1. An automation on the lead in LeadSquared triggers when a condition is met.
2. The automation calls a Universal Data Sync (UDS) workflow.
3. The workflow calls the Invorto call initiation API with the Bot ID, the Phone Number ID, and the variable values for that lead.
4. Invorto places the call and the bot runs the conversation.
5. After the call, Invorto posts the insights, the transcript, and the recording to the webhook you configured.
6. UDS receives that payload and maps it onto the lead as activities, which can trigger further automations.

You need an API key from the Settings page, the Bot ID from the bot’s Details panel, and the Phone Number ID from the Phone Numbers page.

Refer to the UDS documentation to set up the flow: Universal Data Sync (UDS) | No Code Integration Platform.

Next Steps

• To build your first bot, see Creating a Voice Bot.
• Once you create you’re first bot, you can dial a contact list, see Create and Run a Voice Campaign.
• To analyze recordings your team already made, see Create and Run an Insight Campaign.

Any Questions?

Did you find this article helpful? Please let us know any feedback you may have in the comments section below. We’d love to hear from you and help you out!