Skip to main content

Microsoft Teams

RefineAI Answers works where your team already talks: ask the bot a question in a Teams channel or chat and it replies with the same cited, confidence-badged answers as the web app — drawn only from your organisation's documents.

Everything about answers in Asking questions applies in Teams too; this page covers what's different in Teams: how a channel decides which documents it answers from.

Where an answer comes from​

Every bot reply begins with an Answered from line, so you always know the scope it used:

  • Answered from: all documents — the whole library.
  • Answered from: Product (channel default) — the channel is mapped to collections by an admin.
  • Answered from: HR Policies (requested) — you asked for that scope with in: or a picker card.
  • Answered from: HR Policies (conversation scope) — a scope chosen earlier in the thread is still in effect.

When several scopes could apply, the most specific wins: your explicit choice beats the thread's earlier choice, which beats the channel default, which beats all documents.

in: — scoping a question as you type​

Prefix your question with in: and a collection name:

in:Product what does the Growth tier cost per month?
in:"HR Policies" how much annual leave can be carried over?
in:all who owns the Aurora roadmap?
  • Quote names that contain spaces: in:"HR Policies".
  • The choice sticks for the thread — follow-ups stay scoped until you change it.
  • in:all (or in:*) clears back to all documents — including in a mapped channel, where it deliberately overrides the channel default for that thread.
  • Names are matched case-insensitively. If the name doesn't match a collection exactly, the bot never guesses — it shows a picker instead.

Picker cards​

You don't have to remember collection names. The bot offers buttons in two situations:

  • Unrecognised or ambiguous in: name — a card lists your collections (plus All documents); choosing one answers your original question with that scope and keeps it for the thread. Very large organisations see the first ten collections with a hint to use in:"exact name" for the rest.
  • First question in an unmapped thread — the bot answers straight away from all documents, then attaches a one-time "narrow this thread?" offer underneath. Ignore it and it won't ask again; in: remains available whenever you want it.

For admins​

Channel-to-collection mapping — the zero-effort default everyone in a channel inherits — is configured in the web app under Settings → Teams.