Use case · Revenue operations
A monitor spots slipping coverage, a Relay finds why, the dashboard shows the deals, and the CRM updates after a manager approves.
An illustrative revenue operations use case for Agent Serve, the AI workspace where teams build, deploy, and manage AI agents: Monitors, a Revenue Analyst Relay, Dashboards, Chat and Workflows combine to prepare a weekly pipeline review.
At a glance
The problem it removes
Each week someone exports the pipeline, checks coverage by hand and chases reps for updates before the forecast call. Deals that are slipping are found late, and the review deck is out of date by the time it is shown.
Step by step
The pipeline monitor flags EMEA coverage below 3× on Monday morning.
The Revenue Analyst reads the deals, finds the slipped ones and drafts the review.
The CRM update and the email to sales leads go out only after approval.
How it fits together
A monitor on pipeline coverage raises an alert when a region drops below 3×.
The Revenue Analyst Relay picks up the alert, reads the deals and drafts a briefing.
The pipeline dashboard drills from the region to the slipping opportunities.
Managers ask Chat which deals moved stage and why, with sources.
A workflow writes next steps back to the CRM after a manager approves.
How it runs
The whole review runs in Agent Serve, and nothing leaves for the CRM or an inbox until a manager says yes.
A Metric threshold monitor checks pipeline coverage every hour and raises a Warning when a region falls below target.
The Revenue Analyst Relay starts on When a monitor alerts and reads the pipeline table and dashboard it was given.
It lists the deals that slipped a stage or a close date, with the reason it found for each.
The briefing email and the CRM update wait as approvals showing the exact message and fields.
What to measure
Example figures for a mid-size sales team, to show what is worth tracking.
−70%
Review prep time
From about 6 hours to under 2 each week.
+18
Deals flagged early
At-risk deals surfaced before the forecast call.
+4 pts
Forecast accuracy
Committed versus closed, quarter on quarter.
0
Unapproved CRM writes
Every update waits for a manager.
Illustrative example. Figures show how the workflow is measured; they are not customer results.
In depth
Agent Serve puts the dashboard, the scenario, the approval and the follow-up question in one workspace.
The Agent Serve pipeline dashboard drills from region to stage to the opportunities, with breadcrumbs back up.
Agent Serve dashboard scenarios recalculate outcomes as a manager changes discount, term or deal size, kept apart from recorded results.
An Agent Serve Relay always asks before it sends email. The manager sees the exact message, then approves or declines.
Managers attach the pipeline table in Agent Serve Chat and ask which deals moved and why, then get a chart back.
Examples
The same pattern, adapted by three revenue teams in banking, insurance and payments on Agent Serve.
An Agent Serve monitor watches committed lending pipeline by region, and a Relay drafts the Monday note for relationship managers.
An Agent Serve dashboard tracks renewals due in 90 days, and a Relay lists the brokers whose books are slipping.
An Agent Serve workflow updates merchant deal stages in the CRM after a sales manager approves each change.
Examples show what teams can build in Agent Serve. They describe patterns, not named customer deployments.
Before and after
| Work | Before | With Agent Serve |
|---|---|---|
| Spotting risk | BeforeSomeone notices thin coverage during the forecast call. | With Agent ServeA monitor raises an alert as soon as coverage crosses the line. |
| Preparing the review | BeforeAn analyst exports the CRM and builds slides every Monday. | With Agent ServeA Relay drafts the review from the same pipeline data the dashboard uses. |
| Updating the CRM | BeforeNext steps typed in by hand after the meeting, if at all. | With Agent ServeA workflow writes them back once a manager approves. |
| Who sees what | BeforeOne export emailed to everyone, every region included. | With Agent ServeRow-level security shows each manager their own territory. |
Governance
Agent Serve keeps revenue data scoped by territory, and every outbound action waits for a named person.
Security and governanceAgent Serve caps how many tasks a Relay runs at once and per day, so a burst of alerts never floods the team.
The Agent Serve Human block pauses the CRM update until a manager responds.
Relays never send email or book meetings without an approval, under any autonomy setting. An approval covers the exact payload the reviewer saw and expires if nobody decides.
Proposals, approvals, declines and executed actions are written to the workspace audit log, which admins can export.
Row-level policies narrow what each person sees in tables, dashboards, exports and scheduled reports.
Workflows run from a deployed version, so a change is reviewed before it reaches production runs.
Admin, write and read roles per workspace, plus permission groups that limit which models, blocks and integrations a team can use.
Further reading
Disputes that fail reconciliation tend to sit in a side queue until the chargeback window has closed. Here is an end-to-end setup that finds them early, ranks them by deadline and drafts the pack, with an analyst signing every filing.
Cards and payments operations · 12 min readPeriodic reviews pile up because every file starts from scratch, even when nothing has changed. Here is a setup that refreshes the data, drafts the file and routes it by risk, so analysts spend their time on the reviews that need judgement.
Retail and business banking · 12 min readSampled call reviews find a missing risk warning weeks after the client acted on the advice. Here is a setup that checks every recorded advice call within a day and puts the quote in front of a compliance reviewer.
Wealth and advice · 12 min readQuestions
Agent Serve Monitors, Relays, Dashboards, Chat and Workflows, plus a connection to your CRM. The pipeline data sits in an Agent Serve table the monitor and dashboard read.
Only if you allow it. In this use case the Agent Serve workflow pauses at a Human step, so every CRM update waits for a manager to approve it.
You choose. Agent Serve monitors run from every 5 minutes to every 7 days, and a workspace can hold up to 200 monitors.
No. The figures are illustrative examples of what a revenue team might measure with Agent Serve, not customer results.
Last updated
Enterprise access
Agent Serve is available to teams by invitation. Tell us what you want to build and we will set up your workspace with you.