Not every legal question needs a lawyer
Risotto answers the routine legal questions in Slack and Microsoft Teams, from the policies and templates Legal has already approved, and cites them. Do we need an NDA? Can I use this customer’s logo? The answer comes back with its source, and the template linked. The questions that need judgment, and every contract review, go to Legal’s own queue with the details already collected.
Answers from the documents Legal approved
Risotto answers NDA, data retention, privacy and contract-template questions from Legal’s own documents in Confluence, Notion, Google Drive, SharePoint, OneNote, Guru or Coda, and cites the page it used. When the policy doesn’t cover the question, or it needs a lawyer’s judgment, Risotto passes it to Legal with what it found.
Legal approves the answer before it’s sent
Some answers should get a lawyer’s eyes first. Turn on answer review for Legal’s department, and Risotto holds every answer it drafts from Legal’s documents, or from a Legal runbook, in Legal’s agent channel in Slack. The draft arrives with Approve and Reject. Approve it, and Risotto sends it to the employee as written. Reject it, reply in the thread, and the employee gets your answer instead. The ticket records who approved each one, and analytics shows how many drafts your team approved.
Your playbook stays with Legal
Counsel’s fallback positions and negotiation notes shouldn’t answer a sales rep’s question. Connect them to Risotto with the audience set to Assistant only, and only Legal working in Risotto’s Assistant can draw on them: employees never get an answer from them or see them referenced. Scope Legal’s other sources to the Legal department, and they answer Legal’s requests.
Contract requests that arrive complete
A contract review starts with the same questions every time: who’s the counterparty, what kind of contract, how much, whose paper, and by when. Attach a form to Legal’s runbook, and Risotto collects them before counsel opens the request: a Slack form, a Teams card, or one question at a time anywhere else. The contract the requester drops in the thread is saved to the ticket.
Policy acknowledgments from the whole company
Rolling out a new code of conduct? Send it as a Risotto campaign: one direct message in Slack to everyone in an Okta or Google Workspace group, with a checkbox to acknowledge it and any questions you need answered. You see who has answered, remind the rest, and export every response to a CSV for your records.
Code of Conduct 2027 Live
88% complete527 of 600 responded
527 submitted70 awaiting response3 declined
Send reminderExport CSV
Sensitive folders, for as long as they’re needed
Access to a litigation folder or a deal room goes through the Google Workspace or Okta group that protects it. Risotto asks the approver your policy names, such as Legal, and removes the access on the end date the rule sets. Every grant is on the record.
“For sensitive tools and resources Risotto’s automated time-based access has been a game-changer.”
Legal’s work stays Legal’s
Risotto keeps Legal’s requests and documents inside limits you can check.
- A private queue. Only Legal’s Agents and Supervisors see Legal’s tickets, and an admin role elsewhere in Risotto doesn’t add them.
- A record of who’s in it. Every change to who’s in Legal’s department is recorded in the audit log.
- Answers Legal signs off. With answer review on, no answer from Legal’s documents reaches an employee until someone on Legal approves it.
- Playbooks kept internal. Sources set to Assistant only never answer an employee.
- A record of every request. Who asked, who answered, what was approved and when, on the ticket.
- Zero data retention. Risotto’s model providers keep no copy of your data. SOC 2 Type II.
Frequently asked questions
What legal questions can Risotto answer?
Routine policy, compliance and template questions, such as whether a vendor call needs an NDA or how long to keep a customer’s data. Risotto answers from Legal’s approved documents with the source cited, and passes anything that needs a lawyer to Legal’s queue. Knowledge
How does Risotto keep legal requests confidential?
Only Legal’s Agents and Supervisors see Legal’s tickets, and an admin role elsewhere in Risotto doesn’t add them. Which documents can answer whom is set in Risotto for each knowledge source, and Risotto’s model providers keep no copy of your data. Security and trust
Can Legal approve Risotto’s answers before employees see them?
Yes. Turn on answer review for Legal’s department, and Risotto holds each answer it drafts from knowledge or a runbook in Legal’s agent channel in Slack. Approve sends it as written; reject it and reply, and the employee gets your answer instead.
Can Legal’s negotiation playbook stay internal?
Yes. Set the knowledge source’s audience to Assistant only, and only the Assistant draws on it: employees never get an answer from it or see it referenced. Knowledge
Can Risotto collect policy acknowledgments from employees?
Yes. A Risotto campaign sends each person a direct message in Slack with a form, such as a checkbox to acknowledge the code of conduct, shows who has answered, and exports the responses to a CSV.
Does Risotto keep an audit trail of legal requests?
Yes. Each request keeps who asked, who answered, what was approved and when on its ticket, and the audit log records every change to who’s in Legal’s department. Security and trust




