Product·Agents

Every agent belongs somewhere.
A role, a team and a named person responsible.

Each agent holds a role in one of your departments and works for a named person who answers for its work. You set it up from a plain-language job description and rules written in plain English.

Book a discovery call→

A role, written down before it runs

You describe the job in ordinary words: what the agent does, which department it sits in and who it works for. Then you add the rules it follows, also in plain English.

Every task starts with a person approving each item the agent handles.

roleOne job in one department, in a sentence a manager would recognise

responsibleOne named person who answers for the agent’s work

rulesPlain-English rules, including what must always go to a person

starts fromEmail, Teams, Slack, files or a schedule

identityIts own Microsoft Entra identity, if you want one

Job description

example

“Answer supplier questions in the finance inbox about invoice status, payment dates and remittances. Follow up with the supplier when something is missing.”

department

Finance operations

responsible

Financial controller

rule

Bank-detail changes and payments always go to a person

autonomy

level 1, every item approved

starts from

Email to the finance inbox

Start at level 1Every item goes to the review queue first.

Where it starts, and where it works

An agent picks up work from the channels your team uses today and does it in the apps they already have.

01

Where the work arrives

An email, a message in Teams or Slack, a file landing in a folder, or a schedule. Nobody has to forward work into a new queue.

02

Where it does the work

In about 200 business apps, with the access an administrator grants for each connection.

03

What it leaves to a person

Whatever its rules send to a person, and every action you mark as serious. Those never run alone, at any level.

Example case

One supplier email,
from arrival to the record.

Work that takes more than one step is tracked as a case, so anyone on the team can see where it stands. This example comes from a finance inbox at level 1, where a person approves every item.

A leave request, a partner question or a new supplier follows the same pattern. Anything its rules hold back goes to a person, and the case keeps the history.

The email arrives

A supplier writes to the finance inbox asking when an invoice will be paid. The agent opens a case.

It finds the answer and its source

It looks up the invoice and the payment date, then drafts a reply that cites both.

It checks its rules

The same email asks to change the supplier’s bank details.

A serious action. Bank-detail changes are marked as serious, so the agent never makes one alone, at any level. It passes the request to the financial controller with the email attached.

Your team reviews the reply

The draft waits in the review queue. Someone on the team approves, edits or declines it before it goes.

The case goes on the record

The reply, the check that let it go out and the person who approved it are kept in one record.

What it can reach

An administrator grants each connection and names its scope when granting it. Read and write access are stated separately.

An agent can also carry its own Microsoft Entra identity, which your Microsoft 365 admin manages in Entra.

Who answers for it

Every agent works for a named person in the department it belongs to. Its work comes to that team’s review queue, where they approve, edit or decline it.

How much it does alone is set task by task by the team’s run of approvals.

What people ask first

“We already have Copilot.”Good. Xalios runs on your Microsoft 365 and Entra, and agents can carry their own Entra identity. It’s bought by the team that answers for the work and priced by the item handled, not as another seat.

Will it work in our apps?Agents work in about 200 business apps. Work that lives inside a system we don’t connect to, such as an ERP without a connector, isn’t a fit.

What about work that takes days?Long work is tracked as a case, so the team can follow it from the first message to the last action.

NextAutonomy set by the people who answer for it.More of a task alone after each run of approvals (30, 150 and 750 in a row by default), and a step back after 2 mistakes in the last 20.Autonomy →

Write one job description for one stream of work, and see every item come through your review queue first.