Prerequisites: a RevOps workspace with a channel and an agent. Seat provisioning needs access provisioning set up.
What good looks like
1
Separate the four shapes at intake
These look similar in a channel and are completely different work. Make the distinction a form field, not a judgment call for the person triaging:
Route each shape differently. Configuration changes in particular should not sit in the same working list as data fixes, because they will always lose.
Learn more about choosing between channels, views, and categories
2
Give the answers to the agent
The “where is” and “how do I” questions are the highest-volume shape and the least valuable use of an ops person’s time. Index the things people ask about:
- Where each standard report and dashboard lives
- What each pipeline stage means, and the exit criteria for each
- Required fields at each stage, and why
- How to log an activity, an opportunity, a multi-product deal
- Which tools reps have by default and how to request the rest
Learn more in structuring knowledge for AI
3
Hand seats to access provisioning
New-hire tooling is the request shape that automates most cleanly, and RevOps usually has no idea it is available.Put the go-to-market stack in the application catalog: the CRM, the engagement tool, the call recorder, the enablement platform, the data provider, the CPQ tool. Tier them the same way IT tiers everything else, with the sales manager as the first approving round.Then the request is a form, the approval is a round, and the grant is automatic. It also means the seats are visible as entitlements, which is what lets you reclaim them when someone leaves.
Learn more in setting up access provisioning
4
Fold new hires into onboarding
Better still, do not wait for the request. The onboarding task template can include the go-to-market bundle for a sales role, so the seats are requested before the start date rather than on day two.
Learn more in employee onboarding
5
Treat configuration changes as change management
A CRM accumulates fields the way a garage accumulates boxes. The desk is where you stop that.Require three things on any configuration change request: what problem it solves, who else is affected, and what happens to the existing data. Then attach an approval, one round, the RevOps lead. The approval is not bureaucracy, it is the only thing preventing a fourth field that means “renewal risk”.Use a task template so the change has visible stages:
- Confirm the requirement and the reporting impact
- Check whether an existing field already covers it
- Build in the sandbox
- Migrate or backfill existing data
- Update the field documentation in knowledge
- Announce the change to the sales team
Learn more in task templates
6
Split the working lists by shape
Four views, matching the four shapes. The important one is Configuration changes, not resolved, oldest first, reviewed on a fixed slot each week. Without a dedicated slot, project work never beats a same-day data fix.
Learn more about views
7
Use the volume as a roadmap
Once requests are categorized, the pattern is readable. Twelve requests a month to fix the same field means the field needs a validation rule. Forty questions about one report means the report needs renaming or the answer needs documenting.The knowledge gaps report does the same thing for the questions the agent could not answer, ranked by frequency. That is a better prioritized backlog than a planning session produces.
Learn more in closing knowledge gaps
Where teams get this wrong
One undifferentiated list
One undifferentiated list
Configuration work never wins against a same-day data fix, so it never happens.
Seats by DM to the CRM admin
Seats by DM to the CRM admin
It is invisible, it is unauditable, and the seat is never reclaimed.
Adding a field on request
Adding a field on request
Ask what problem it solves and whether a field already covers it.
Not updating documentation after a change
Not updating documentation after a change
The agent then confidently describes a CRM that no longer exists.
Next
Deal desk
The approval half of the desk.
Reporting and briefs
Turn request volume into a roadmap.