Skip to main content
This page is about Enterprise deployments only. Microsoft Teams is not available on SaaS.
The Neural Factory bot for Microsoft Teams lets people in your organization ask an agent something without opening the web app. They write to the bot in Teams, and the agent’s answer comes back in Teams.
Who: an Admin sets it up; people of your organization chat with it · Where: the bot in Microsoft Teams; its key under Integrations › API keys · Works on: Enterprise only

Set up the bot

Your Neural Factory contact installs the bot in your Microsoft Teams tenant with you, and you choose together which agent it talks to. Your part in the web app is one API key.
1

Create the bot's key

An Admin opens API keys and selects Create API Key. Give the key the Chat permission and turn on Microsoft Teams bot key. See API keys.
2

Hand the key over

Copy the secret from Copy your secret key now and give it to whoever installs the bot, through a secure channel.
3

Publish the agent

Check that the agent the bot talks to is published. The bot can reach any published agent of your organization.
Only a key marked Microsoft Teams bot key may send messages on behalf of the people writing in Teams. Mark that one key and leave every other key unmarked. You can set or clear the mark later in Edit API Key. Turning the key off or deleting it stops the bot within seconds.

Who can chat with it

The person writing in Teams must belong to your organization. Someone with an account in another organization, or with a deactivated account, is refused. Someone who writes to the bot for the first time and has no Neural Factory account yet gets one automatically, in your organization, with the Viewer role. A Viewer can chat with agents but can’t create or change anything in the web app. These people appear in Settings › Users & groups, with Teams in the Client column. An Admin can change their role there; see User management. When such a person later signs in to the web app with Microsoft, their account becomes an ordinary account of your organization. Each message counts as the work of the person who wrote it: toward their usage, and toward their limit of tasks running at the same time.

Where Teams conversations show up

  • Conversations held in Teams are not listed under Tasks in the web app.
  • They are recorded in Interactions, with Teams as the client, so Admins can review them like any other conversation. See Interactions.
Like every key, the bot’s key acts for the Admin who created it. It stops working if that person’s account is deactivated or they leave the organization. Create a new key in that case and hand it over the same way.