Skip to main content
A chat agent is an agent you talk to. Same tools, same integrations, same custom instructions — but instead of firing on a ticket or a schedule, it answers messages in a conversation that remembers context across turns.

​
The three ways agents run

​
Who’s talking to whom

Every conversation has two parties, and keeping them straight explains everything else:
  • The owner — the MSP whose agent it is. The owner’s configuration runs and the owner is billed.
  • The user — the person typing. Either one of the MSP’s own technicians, or an end user at one of the MSP’s client companies.
The distinction isn’t cosmetic: technician conversations run with your full MSP-level tools, while end-user conversations are locked to the user’s own company with a separate, narrower capability set — see how end-user bots work.

​
The chat surfaces

A chat agent can run in the dashboard or in Microsoft Teams — and in Teams it can face either your own technicians or your clients’ employees. The same agent you build can be put on more than one surface.

Chat in the dashboard

Your technicians chat with your agents on the Chat page — sessions, history, sharing, feedback, inline approvals. Every agent works here; it’s where you build and test.

Your custom internal Teams bot

Put one of your own agents in front of your technicians in Microsoft Teams — your prompt, your tools, your branding. Runs with your full MSP toolbox, across all your companies.

Your branded end-user Teams bot

Put one of your chat agents in front of your clients’ employees as a branded Teams bot — your name, your icon. They get instant answers and file tickets right in Teams, scoped to their own company. The headline use case.

Neo Support Agent

A chat agent managed by Neo, available to every MSP. Answers “how do I configure X in Neo” and searches your docs and tickets. Reachable in the dashboard and through the Neo AI Agent Teams app.

​
Finding an agent’s ID

Every chat agent has a numeric ID. You’ll rarely need it day to day, but Neo Support will ask for it when you raise an issue about a specific agent — it identifies the agent unambiguously, where a name might be duplicated or since renamed. It’s shown in two places on the Chat page, each with a copy button:
  • In the ID column of the agents table, so you can read off any agent’s ID without opening it. The column sorts, which helps when you have many agents.
  • Under the agent’s name in the sidebar while you’re chatting with it.

​
When to use a chat agent

Use a chat agent when a person initiates and the value is back-and-forth: a technician asking “which mailboxes have forwarding enabled for Contoso Contractors?”, or an end user asking for a password reset. Use a triggered or scheduled agent when the work should start from an event or a clock — no one needs to ask. To get started: build a chat agent, validate it in the dashboard, then connect it to a channel to reach people in Teams — a custom internal bot for your technicians, or a branded end-user bot for your clients’ employees.