# Answers from your own docs, receipts included

Employees ask in Slack or Microsoft Teams, and Risotto answers from the pages your team already wrote, citing every one.

[Book a demo](/demo)

## Connect the docs you already keep

Your Confluence spaces, Notion pages and Google Drive folders stay where they are, and become answers once you connect them to Risotto. The Indexes page shows each source's sync state and document count, and any source reindexes from its menu.

[Every knowledge source](/integrations)

Each source with its department, audience and size, and a reindex running. Example data.

## Write the answer once

For answers that live in nobody's wiki, IT writes articles in Risotto, for the whole company or one department. Articles rank above synced docs in the agent's search. Already answered it in Slack? Add a ✍️ reaction to the thread, and it becomes an article.

The thread becomes an article, and the next answer cites it. Example data.

## Where did that answer come from?

Each claim in a Risotto answer ends with a numbered link to the page it came from. Before the reply posts, a second check compares every statement with those pages and asks for a rewrite of any they don't support. When nothing in your docs fits, the request goes to your team instead of getting a guess.

At Docker, **41%** of Finance requests are auto-resolved through approved policy documentation. [Read the Docker story](/customers/docker-automates-68-percent-it-tickets-with-risotto)

Each number links to the page it came from. A question your docs don't cover goes to your team. Example data.

## The right answer for the right team

Each source and article in Risotto belongs to one department or to the whole company.

- **Departments.** HR's handbook answers HR's requests, and IT's how-tos stay out of Finance answers.
- **Assistant only.** Admin-console how-tos and security procedures inform [the Assistant](/product/assistant) and never reach an employee.
- **Profile filters.** Match a source to people by fields such as location or role, so each person gets the policy written for them.
- **Runbook pins.** Type # in a [runbook](/product/runbooks) to make the agent use only one page or source, or to skip a source entirely.

Finance's UK policies, matched to people in the London office. Example data.

## Test a question before anyone asks it

Type a question into Risotto's Playground to see the pages the agent finds and the answer it writes from them. Pick an employee to see their answer, or a department to check its scope.

The question as someone in the London office would ask it, scoped to Finance. Example data.

## Find the questions your docs miss

Insights reads your last 90 days of tickets in Risotto and lists the questions no doc answered and the pages that may be out of date.

[See Insights](/product/insights)

Questions your docs missed, from 90 days of tickets. Example data.

## Frequently asked questions

### Can IT write knowledge articles in Risotto?

Yes. Risotto has its own articles, written in Markdown in the dashboard and scoped to the whole company or one department. A ✍️ reaction on a Slack thread creates one from the conversation.

### Does Risotto cite its sources?

Yes. Every answer Risotto gives from your knowledge links each claim to its source page, and each statement is checked against those pages before the reply posts. [The AI agent](/product/ai-agent)

### Can knowledge be limited to one department?

Yes. In Risotto, a department's requests get answers only from that department's sources and articles and the company-wide ones. A source marked Assistant only never reaches employees.

### Where do our docs need to live?

Where they already are. Risotto connects to [Confluence](/integrations/confluence), [Notion](/integrations/notion), [Google Drive](/integrations/google-drive), [SharePoint](/integrations/sharepoint), [OneNote](/integrations/onenote), [Guru](/integrations/guru), [Coda](/integrations/coda), Zendesk Guide, Freshservice, Jira, GitHub and Slack channel history. [Integrations](/integrations)

### How do we know how many requests Risotto answers from our docs?

The analytics dashboard shows it. "Solved with knowledge" is the share of solved tickets Risotto closed from your knowledge with no escalation. [Analytics and Insights](/product/insights)

## Your docs are already written. Put them to work.

[Book a demo](/demo)

Source: https://www.tryrisotto.com/product/knowledge
