> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Branded End-User Support Bot in Teams

> Give a client's employees a Teams bot under your brand that answers questions, checks ticket status, and files tickets

## 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.

<Info>
  This is a **chat agent** connected through a **channel**. See [Chat Agents](/chat-agents/overview) and [Channels](/chat-agents/channels) for how this works.
</Info>

## 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

<Steps>
  <Step title="Create the chat agent">
    * **Name**: "IT Support Assistant"
    * **Type**: Chat Agent ([**Chat**](https://dashboard.neoagent.io/chat) → **New Chat Agent**)
  </Step>

  <Step title="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.

    <Warning>
      In end-user conversations (through a [channel](/chat-agents/channels)), 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](/integrations/teams/end-user-bot#what-end-users-can-access) for what's available in the deployed bot.
    </Warning>
  </Step>

  <Step title="Write custom instructions">
    ```
    You are the IT support assistant for our clients' employees.

    1. Answer how-to questions from the documentation. Keep answers short
       and non-technical.
    2. When asked about an existing issue, look up the user's recent tickets
       and report status in plain language.
    3. If the issue needs a technician (anything you cannot resolve by
       pointing at documentation), create a ticket. Collect: what happened,
       when it started, error messages, device affected. Confirm the ticket
       number back to the user.
    4. Never discuss other companies, pricing, or internal MSP matters.
    5. If the user is frustrated or the issue is urgent (outage, security),
       create the ticket immediately and say a technician will follow up.
    ```
  </Step>

  <Step title="Add per-client instructions (optional)">
    On [**Companies**](https://dashboard.neoagent.io/end-companies) → edit a client → **Chat Instructions**, add company-specific guidance — their VIPs, their escalation contact, software they use.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Create the channel and deploy">
    [**Chat** → **Channels**](https://dashboard.neoagent.io/chat?tab=channels) → **New Channel**: transport **Teams**, assign the agent, set your branding, activate. Then follow [End-user Teams bot](/integrations/teams/end-user-bot) to install it in the client tenant — test against your own tenant first.
  </Step>
</Steps>

## 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