What is Verbo?

Verbo is Versa Networks’ intelligent, context-sensitive chatbot assistant, embedded directly in the Director, Analytics, and Concerto GUIs. Using natural language processing, AI, and machine learning, it answers technology questions, assists with configuration, and guides troubleshooting – all through one conversational interface inside the console a user is already working in.

Key takeaways

• Chatbot assistant embedded in Director, Analytics, and Concerto GUIs.
• Uses NLP, AI, and ML to answer questions and guide troubleshooting.
• Routes queries to TroubleShooter, VersaGPT, or ToolCaller components.
• ToolCaller uses MCP connectors to call Director and Concerto APIs.
• Chat sessions enforce the same RBAC as the user’s Director role.

On this page: Why it matters · How it works · Verbo components · Verbo & the VersaONE platform · FAQ

Why is Verbo important?

In a platform as broad as VersaONE – Director, Concerto, Analytics, and dozens of feature areas beneath them – the fastest path to an answer is often not a menu search but a question asked in plain language. Verbo exists to be that question box: an administrator types “branch is down” or “how do I configure SNMP” and gets a routed, contextual answer inside the same console they’re already using, instead of hunting through documentation or submenus.

It also matters for the routine grind of operations. Checking a branch’s connectivity, reading CPU and memory load, or inspecting an Analytics cluster historically meant knowing which screen, command, or support case to open. Verbo automates that diagnostic legwork behind a conversational front end, and when a problem still needs a human, it produces a downloadable transcript a user can hand straight to Versa Networks Customer Support.

What is Verbo?

Verbo is a chatbot icon always present in the Director and Concerto GUIs. Clicking it opens a chat window where a user types a query in natural language; Verbo interprets intent, asks for missing parameters – a branch name, a tenant organization – and returns an answer or a diagnosis. Every session honors the same role-based access control (RBAC) as the user’s Director login, so a user only sees data their role permits.

Behind that single interface, Verbo routes each query to one of three components: TroubleShooter, which diagnoses and resolves issues; VersaGPT, which handles conversational, documentation-grounded answers; and ToolCaller, which executes specific actions through Model Context Protocol (MCP) connectors for Director, Concerto, and other services. Users can copy responses, rate them with feedback icons, download a transcript of an entire interaction, and track a running count of the messages left in their license quota.

Verbo components

Verbo’s architecture has changed across releases. For Release 23.1.1 and later, it uses this MCP-based, component-routed design, exposing API documentation so it can request access to specific APIs – such as ones returning appliance counts – based on the query, rather than being limited to a fixed set of pre-defined diagnostic flows. For Release 22.1.4 and earlier, Verbo instead used Google Dialogflow, converting a typed question into a function call handled by on-premises infrastructure with no query data leaving the deployment, layering progressively more rules onto a rule-based debugging assistant as it ran CLI checks like ping and traceroute. VersaGPT is the generative-AI component embedded in Verbo – and, separately, in the Versa Networks website search – that answers configuration questions with guided steps and links directly into the relevant Director or Concerto screens.

Verbo & the VersaONE platform

Within VersaONE, Verbo is the conversational front end laid over Director, Analytics, and Concerto rather than a separate product: it reads the same appliance, tenant, and telemetry data those consoles expose, and – through ToolCaller’s MCP connectors – can act on live systems on a user’s behalf. A provider tenant administrator configures Verbo’s connector details (service URL, API key, and authentication certificate) to point it at a cloud-hosted or on-premises backend, and any administrator can toggle the chatbot icon on or off entirely. See the Director GUI overview for where the chatbot icon sits alongside the rest of the console.

Frequently asked questions

What can I ask Verbo?

Verbo answers questions about Versa Networks technology and the Director, Analytics, and Concerto GUIs, and it can diagnose common issues such as branch connectivity, QoS, CPU and memory load, and Analytics cluster health, asking for details like a branch or organization name as needed.

How does Verbo differ from VersaGPT?

Verbo is the chatbot interface and routing engine; VersaGPT is one of the components it routes to – the generative-AI engine that answers configuration questions with guided how-to steps and links into relevant Director or Concerto screens, also embedded in Versa’s website search.

Does Verbo require an internet connection?

Yes. The browser running the Director or Concerto GUI must reach the internet for Verbo to function, whether it queries an on-premises or cloud-hosted backend; an administrator configures which backend Verbo connects to through its connector settings, including the URL, certificate, and API key.

Who can use the Verbo chatbot, and what can they see?

Any user with GUI access sees the chatbot icon, but each session enforces the same role-based access control as their Director login – a user can only query and view the data their assigned role already permits them to access elsewhere.

Can I turn off the Verbo chatbot?

Yes. An administrator can toggle the chatbot from the Director GUI’s Administration menu (Toggle Chatbot), which removes the icon from view entirely. Selecting Toggle Chatbot a second time re-enables it, restoring the icon for every user of that Director instance.

More on Verbo

If you want to learn more, these are sources we trust.

Related terms

If you’re reading about Verbo, these are worth looking at next.