Skip to main content

​
Overview

This recipe builds a chat agent for end users — your clients’ employees — and deploys it into a client tenant as your own branded Teams bot. Users ask IT questions, check on their tickets, and file new ones, all in Teams.
This is a chat agent connected through a channel. See Chat Agents and Channels for how this works.

​
How it works

  • An employee at your client messages your branded bot in Teams; their company is recognized automatically from the Microsoft 365 tenant
  • The agent answers from your knowledge base and their company’s ticket history
  • It can create a ticket when the issue needs a technician — and that’s its only write

​
Setup

1

Create the chat agent

  • Name: “IT Support Assistant”
  • Type: Chat Agent (Chat → New Chat Agent)
2

Enable tools — read-only plus ticket creation

  • Find Documentation — answer from your KB
  • Find Tickets by Content — “what’s the status of my request?”
  • Create New Ticket — escalate to a technician
  • PSA permissions: Read Only
Avoid write permissions and M365 tools on end-user-facing agents — prefer “file a ticket” over direct action.
In end-user conversations (through a channel), Neo enforces company scoping on top of the toolbox: tools that operate across your whole client base never run for end users, regardless of what’s enabled here. The toolbox above applies in full to dashboard testing; see what end users can access for what’s available in the deployed bot.
3

Set where tickets land — and the ticket's statuses

The bot’s own ticket tools need a destination before the agent can be saved: the board/queue/type, plus the initial status (the bot has it) and the resolved status (done).There’s a third, optional one: the escalation status, where the bot moves a ticket when it can’t finish the job. Either way it leaves a handover note for the technician — the status just decides whether the ticket also moves. Set one if your tickets open somewhere your queue doesn’t triage, or they’ll sit there. Leave it empty if they already open in a status a technician sees.See where end-user tickets land and handing a ticket to a technician.
4

Write custom instructions

5

Add per-client instructions (optional)

On Companies → edit a client → Chat Instructions, add company-specific guidance — their VIPs, their escalation contact, software they use.
6

Test in the dashboard

Chat with the agent on the Chat page. Ask the questions an end user would. Tune instructions until the tone and escalation behavior are right.
7

Create the channel and deploy

Chat → Channels → New Channel: transport Teams, assign the agent, set your branding, activate. Then follow End-user Teams bot to install it in the client tenant — test against your own tenant first.

​
Variations

​
Password-reset triage

Add instructions to walk users through self-service password reset first, and only create a ticket if that fails. Keep the agent itself without M365 write access.

​
Status-only bot

Drop Create New Ticket for a purely informational bot — useful as a first rollout while you build trust in the agent’s tone.

​
Best practices

  • Re-read transcripts weekly at first — end users phrase things in ways technicians don’t
  • Set the welcome message to state what the bot can do, so users don’t ask for the impossible