A plain-language request becomes an action in your systems.
The Hub is where your teams, your agents and your IT systems meet. It understands the request, picks the right access path, runs the right actions, and reports on every step.
Channels The request comes in through the user's own channel, or from another application. The Hub Agents understand the request, read the attachments and prepare the operation. Action The operation goes through the most direct access path, or through the Studio, and the user is notified.
“Create a purchase request from the attached quote.”
One sentence, typed in Teams. The Hub reads the quote, extracts the details, picks the operation, validates the parameters and hands data entry to the right access path. The user gets the request number, and the audit trail stays.
- 1The request comes inin Teams, with the quote attachedChannel
- 2The agent reads the quotesupplier, line items, amountsAgent
- 3The agent picks the operationcreate a purchase requestAgent
- 4Clear governance checks the parametersdata types, required fields, permissionsGovernance
- 5The request is entered in the ERPthrough an API, or by a Studio botExecution
- 6The user gets the numberthe action is logged under their nameReply
An agent combines skills. Each skill acts directly on your systems.
Agents work as a team: each one has its own role, skills and permissions. A skill built for one use case carries over to the next.
Reasons and orchestrates
It understands the request, decides the sequence and calls its skills. It never touches your systems except through them.
Read, anonymize, assess, notify
Specific, tested, reusable capabilities built on what your systems expose.
MCP, database, API, automation, files
Your system access points, declared once. When the screen is the only way in, the Studio provides the capability through its bots.
Your systems, open to every business team.
- A single conversational entry point, whatever the channel: Teams, WhatsApp, phone (IVR), portal.
- A request, or any interaction with your systems, turned automatically into a concrete action.
- System access open to every business team, with no technical skills required.
- Rigorous traceability of every action taken on the user's behalf.
- Simple configuration of connectors, prompts and orchestration, with teams of specialized agents.
- Model-agnostic by design: you choose your LLM, including on your own subscription.
Direct when your systems allow it. Through the Studio when they don't.
An API, a database, an MCP server, a file: the Hub uses it directly. A screen with no API: the Hub hands the task to the Studio. And when a Studio bot needs to reason or understand a document, it calls on the Hub.
Direct access When your systems expose the operation, through an API, a database, an MCP server or a file, the Hub acts directly. Through the Studio When your systems expose nothing, the Hub relies on the Studio: a workflow or a bot carries out the operation, exactly the same way every time. The other way around When a bot needs to understand a document or make a judgment call, the Studio calls on a Hub agent, then picks up where it left off.
Ready to change how your teams work with your systems?
A 30-minute intro call to talk about your needs.