# CRM access, deal desk and pipeline questions, handled in Slack and Teams

Risotto takes the requests that pile up on Sales Ops. It answers process questions from your playbook, with the source cited. It gets reps into Salesforce, Gong or HubSpot once the right person approves. And it sends deal desk requests to your team with every detail already filled in.

[Book a demo](/demo)

**41%** Revenue Technology ticket automation rate at Jobber. [Read the story](/customers/jobber-builds-enterprise-wide-ai-support-funnel-with-risotto)

## CRM access that's approved, and admin access that ends on time

Reps ask for Salesforce, HubSpot, Gong or an enrichment tool in Slack or Teams. After the approval your policy sets, Risotto adds them to the Okta, Microsoft Entra ID or Google group that controls it. Make standard and admin access separate rules with their own approvers, so admin access lasts only the hours someone asked for and Risotto removes it on time. The access grants page shows who has what until when. Ironclad reports a 91% autosolve rate on access requests.

[Access requests](/product/access-requests) · [Read Ironclad's story](/customers/ironclad-transforms-90-percent-it-support-with-risotto)

Chris asks for Salesforce admin access for 4 hours. Elena approves it, and at 3:24 PM Risotto removes it and records that on the ticket. Example data.

## Answers from your playbook, so reps stop asking twice

Risotto answers stage, routing and process questions from your Sales Ops docs in Confluence, Notion, Google Drive, SharePoint, OneNote, Guru or Coda, and cites the page it used. Resolved threads become knowledge too, so a question your team answers once gets answered by Risotto the next time.

[Knowledge](/product/knowledge)

Maya asks who owns an inbound lead from an existing customer, and Risotto answers from the lead routing rules with the source cited. Example data.

## Deal desk requests that arrive complete

A rep asks for a discount, and Risotto's runbook shows them a form in the thread: account, deal type, ARR, discount and term. If the discount is over the limit you set, the runbook asks the rep's manager to approve before it goes any further. Then the request lands in Deal Desk's queue, with every answer and the approval on the ticket. Make Deal Desk a sub-department of Sales Ops, with its own tickets, members and escalation contact. Your team still makes the change in Salesforce or your quoting tool.

[Runbooks](/product/runbooks)

Luis fills in the discount request. The discount is over 15%, so his manager approves it before it reaches Deal Desk. Example data.

## Commission questions stay with Sales Comp

Pay is private. Make Sales Comp its own department, and a rep who messages Risotto about their commission reaches Sales Comp's private queue. Only Sales Comp's agents and supervisors see those tickets: not IT, and not the rest of Sales Ops. Every change to who's in the department is logged.

[Ticketing](/product/ticketing)

Marcus asks about his October commission in a DM. Ana answers from Sales Comp's private channel, and her reply reaches him under her name. Example data.

## Built for how revenue teams work

Sales Ops runs on more than the CRM. Risotto covers the rest of the requests, too.

- **Your own queue.** Sales Ops is its own department, with its own permissions, knowledge and agent channel, separate from IT.
- **Deal rooms on request.** Reps ask for a deal channel, and Risotto creates it and adds its first members.
- **Partner and customer channels.** Slack Connect invites are reviewed, with an admin's OK for the ones that need it.
- **Salesforce change requests in Jira.** Requests for a new field or report become tickets that sync both ways with Jira.
- **Comp plan acknowledgments.** Send every rep a DM with a form in Slack, remind the ones who haven't answered, and export the responses.
- **Your other tools.** Connect any tool with an MCP server or an API, and require approval before Risotto acts in it.

[Every team](/solutions) · [Integrations](/integrations)

## Start from the library

Start from one of these and change it to fit. Open one to see every step and tool, or [browse the library](/library).

### Access and channels

The tools and the deal channels your team needs.

- [Okta group access request](/library/runbooks/okta-group-access-request): check your access rules, get the approval, add the person to the group
- [Slack channel request](/library/runbooks/slack-channel-creation): create the channel and add its first members
- [Slack Connect invite review](/library/automations/slack-connect-invite-review): approve partners and deny the rest, with an admin's OK

## Frequently asked questions

### Can Sales Ops keep its requests separate from IT?

Yes. In Risotto, Sales Ops is its own department with its own permissions and private queue, and IT's agents don't see its tickets. [See every team](/solutions)

### Does Risotto work with Salesforce and HubSpot?

Yes. Risotto grants and removes access to them through the Okta, Microsoft Entra ID or Google group that controls each one, and answers questions about how your team uses them from your docs. It doesn't change CRM records by itself. To let Risotto act in a tool, connect the tool's MCP server or API and choose which actions need approval. [Access requests](/product/access-requests)

### Can Risotto handle deal desk and discount requests?

Yes. A runbook collects the details in a form, asks the rep's manager to approve when the request meets the condition you set, and sends it to Deal Desk's queue. Your team makes the change in the CRM. [Runbooks](/product/runbooks)

### Can commission questions stay private?

Yes. Make Sales Comp its own department. Only its agents and supervisors see its tickets, and reps can ask in a direct message to Risotto. [Ticketing](/product/ticketing)

### Does Risotto work in Microsoft Teams?

Yes. Reps ask Risotto in Teams channels or chats, and managers approve access in Teams. Campaigns, such as comp plan acknowledgments, are Slack only. [See Microsoft Teams](/integrations/microsoft-teams)

## Give reps answers and access in the thread where they ask

[Book a demo](/demo)

Source: https://www.tryrisotto.com/solutions/sales-ops
