# Ask from a document or ticket

> How to address the AI agent in Notion, a Google Doc, Confluence, Figma or a tracker: forms of address, where the answer arrives, what the bot does not do.

You do not have to open the app. If your IT specialist has connected Notion, Google Drive, Confluence, Figma or a tracker to the space, you ask with a **comment** on a page, document, design or ticket — and the answer arrives in the same discussion. The answer draws on all the space’s documents and knowledge, not only on the page where you asked.

_Illustration: An ordinary ticket: a person mentioned the bot in a comment, and the bot replied in the same discussion._

## Where and how to ask

| Where you work | Where to write | How to address it |
| --- | --- | --- |
| **Notion** | a comment on a page | `@buff` as text (the alias from the connection settings) or `@` and the integration’s name; Notion’s mention menu does not offer integrations — type it by hand |
| **Google Docs, Sheets, Slides** | a comment on a file | `+address` of the bot’s account — the suggestion fills in the name — or `@buff` |
| **Confluence** | a comment on a page | `@buff` or the alias from the connection settings |
| **Figma** | a comment pinned to a spot on the design | `@buff`; the answer arrives in the same thread |
| **Tracker** — Jira, Jira Cloud, Redmine, GitLab, GitHub, Gitea and Forgejo, Bitbucket (in a pull request) | a comment on a ticket | `@buff …` or the `/ask …` command |
| **A folder on a server, a network folder** | nowhere — a folder has no comments | the question is asked in the app; the folder is a source for the answer |

Case does not matter: `@Buff`, `BUFF`, `/Research` — all of these are requests. The text around the mention is taken into account: you can describe the situation first and then ask. The `/ask …` command at the start of a line works in any system. A second request in the same thread or ticket continues the same conversation — even if a different person writes it.

## What you can ask for

| What to write | What happens |
| --- | --- |
| `@buff what response time is promised on the “Business” plan?` | a **question** — the answer as a comment in the same thread |
| `@buff research discrepancies between the policy, the FAQ and the contracts on response times` or `/research …` | a **deep research** — the document and a link arrive in the same place |
| `/ask …` | the same as a question without a command, only explicit |

The `task` command (`@buff task …`, `/task …`) **does not work** in a space: there is nothing to put a development task into here, and the bot says exactly that.

## What you get back

1. **Straight away** — a short “got it, working on it”: a research takes minutes, and without this you would not know whether the bot heard you.
2. **A link** — to the conversation or the research in the Buff app. In Jira it goes into the ticket’s links block rather than the comment feed.
3. **The result** — the finished answer as a comment in the same thread. If information is missing, the bot asks a clarifying question in the same place and waits for the answer.

## What a requested research looks like

| Where it was requested | What appears |
| --- | --- |
| Notion | a **child page** under the one where you asked — as text, with a PDF attached; in the thread — a comment with a link |
| Google Drive | a **new Google document** in the same folder as the document where you asked, with a PDF next to it; in the thread — an answer with a link |
| Confluence | a PDF document attached to the page, and a comment with a link |
| Figma | a comment with a link — files cannot be attached to a Figma comment |
| Tracker | a comment and a **PDF attachment** on the ticket where the tracker accepts attachments (in Jira — in Data Center and in Cloud) |

A page or document is created only inside the selected section or folder. Existing pages and documents are not changed.

## What the bot does not do

- **It only answers a direct request.** Labels, statuses, a ticket moving across the board are not requests; assigning a task to the bot is switched on separately, if in your team a person assigns it deliberately. The bot does not work through comments written before the connection was switched on.
- **It changes nothing.** It does not edit pages, documents, spreadsheets or designs, does not move statuses or labels, does not assign people. The only things it writes are a reply comment and, for a research, a document alongside.
- **It answers only where the connection works.** Sections, folders, files and projects are set by the connection. For trackers an empty list means nowhere; for Confluence, Notion, Google Drive and Figma an empty list means everything the connection’s account can access. If the bot is silent — [what to ask your administrator for](/en/docs/for-admin).
- **It signs comments with the connection’s account.** If Google Drive is connected by signing in with your own Google account rather than a service account, the answers will appear from that account.

## Who can ask and who sees the answer

- **Anyone can ask** who can leave a comment in a selected place: the bot does not check whether the person is a Buff member or has access to the space. A guest or a contractor in Jira, Confluence or Notion will get an answer too.
- **The answer draws on all of the space’s connections** — a question from a ticket can get an answer from the space’s wiki and Drive.
- **The answer is an ordinary comment.** Everyone who can see the page or ticket sees it. In GitLab and Redmine, an answer to an internal or private note is published as an open comment.
- **The usage is charged to the organisation,** as with any question.

So connect to the space only sections that outsiders — clients, contractors, guests — do not see or comment on, and do not connect a space with confidential documents — HR, legal — where pages and tickets are visible to other departments.

Details for each system are on the [Notion](/en/docs/connector/notion), [Google Drive](/en/docs/connector/google-drive), [Confluence and Figma](/en/docs/connector/knowledge), [Trackers](/en/docs/connector/trackers) and [Jira](/en/docs/connector/jira) pages.