# Guru + Risotto: answers from your cards, right where employees ask

Risotto answers employee questions in Slack and Microsoft Teams from the Guru collections you index, and links the card under each answer. Your team keeps writing cards in Guru. When one changes, Guru tells Risotto, so the next answer comes from the new version.

[Book a demo](/demo)

## What Risotto does with your Guru cards

- **Answers with the card linked.** Risotto replies in plain words and links the Guru card it used, so anyone can check the source.
- **Card text and attached PDFs.** Risotto reads each card's body and the text of PDF files attached to it.
- **A collection per index.** Point an index at a collection by its slug. Add an index for each collection, and give each one the team it answers.
- **Updated card by card.** Connect Guru once and Risotto re-reads a card when it's created, edited or restored, and removes it when it's deleted. No full reindex.
- **One answer from every source.** Risotto combines Guru with Confluence, [Notion](/integrations/notion), Google Drive and your other sources, and returns one answer.
- **The next step, in the same thread.** If the answer is a request, such as access to an app, Risotto routes the approval and grants it there.
- **A ticket for every question.** When no card covers it, Risotto passes the question to your team with what it found.

## Live in three steps

1. **Get a Guru User Token.** Generate it in Guru for a user who can read the collection.
2. **Index the collection.** In Risotto, enter the user's email, pick the token from the credential vault, add the collection slug, and choose the department and audience. Connect Guru under Settings to receive card updates.
3. **Employees ask.** In Slack or Teams, and the answer arrives in the thread with the card linked.

[Read the setup guide](/docs/integrations/knowledge/guru)

## You choose the collections and who they answer

- Risotto reads Guru and never edits or deletes a card.
- It reads only the collections you index, as the token's user can see them.
- A collection can answer one department, so IT's cards answer IT's people and HR's answer HR's.
- Set a collection to Assistant only to keep it for IT's investigations and out of employee answers.
- In Slack, a department can hold knowledge answers in its agent channel until someone approves them.
- The User Token is a vault credential, write-only once saved. If Guru rejects it, Risotto alerts your org admins with a link to update it.

> "Risotto is providing immediate answers 24/7, even when IT isn't online. That's a game changer." — Head of IT, Hazel Health

## Frequently asked questions

### We already use Guru in Slack. Why add Risotto?

Risotto is the help desk around your cards. It answers in your help channel from Guru and every other source you connect, opens a ticket for each request, takes the action when the answer is a request, and hands off to your team when no card covers it. Your cards stay in Guru, and your team keeps writing them there. [Knowledge](/product/knowledge)

### What does Risotto read from Guru?

Every card in the collections you index: the card's title and body, and the text of attached PDFs up to 100 MB.

### How does Risotto stay current when a card changes?

Connect Guru under Settings with a User Token, and Guru sends Risotto a webhook when a card is created, updated, deleted or restored. Risotto re-reads or removes that one card, so there's no full reindex to schedule.

### Do employees need a Guru seat?

No. Employees ask in Slack or Teams and get the answer there, with the card linked for anyone who has Guru.

### Does Risotto change anything in Guru?

Not when it answers. Risotto reads cards to answer questions, and never edits or deletes one.

## Your cards already have the answers. Let them reply.

[Book a demo](/demo)

Source: https://www.tryrisotto.com/integrations/guru
