AI REV Voice for RevOps & Directors

Know what drives
your revenue.

See who is closing business, what is building in the pipeline, and where deals need help. Prism brings the numbers and conversations together.

Track team performance across your CRMs. Ask what changed, decide the next move, and have Operator prepare the work. Your corrections make the next review better.

Try the demoExplore revenue and team performance

Who brings in revenue?
What is behind the result?

Track closed-won revenue, win rate, and the pipeline each rep owns. Compare results across people, teams, or regions, then ask Prism what explains the difference.

Look at activity alongside outcomes: meetings held, opportunities created, deals advanced, and commitments followed through. A busy calendar becomes useful context when you can connect it to what closed and what is moving.

1 operations todo

Revenue review · New business team · Week 39

Show who is bringing in revenue

Closed results, current pipeline, and the next coaching questions, by rep.

Based on

Brian leads closed revenue at $96K. Ruth owns the most open pipeline at $142K, including the $120K Northmoor deal. Owen had eleven meetings and a 33.3% win rate this week. Review the lost-deal reasons and qualification with him before drawing a conclusion from activity alone.

Leadership summary

New business team · Week 39, through Thursday $210K closed won across nine deals. Win rate: 50% (nine wins, nine losses). Current open pipeline: $274K, or $132.4K weighted by probability. Brian leads closed revenue. Ruth owns the largest open opportunity. Review Owen’s lost-deal reasons and qualification, and confirm the next step on Northmoor.

New business · Rep performance

Google Sheets
New business team performance for Week 39. Revenue and pipeline values are in thousands of US dollars.
1RepWon ($K)Win rateOpen ($K)Weighted ($K)
2Brian9666.7%9655.2
3Ruth7250.0%14268.2
4Owen4233.3%369
5Team21050.0%274132.4

Week 39 Through Thursday, September 24

Win rate uses won / (won + lost) deals closed this week. Open pipeline is the current five-deal snapshot below. Weighted pipeline is value × probability.

Based on

Review the rep report and its sources, refine the leadership summary, then share it with the team.

One definition for each KPI.

This report credits closed-won revenue to the owner at close. Win rate uses deals won out of deals won or lost in the period. Current open pipeline and probability-weighted pipeline stay separate from that closed result.

Turn the number into a useful question.

Who is bringing in business? Who is building the next quarter? Where do deals stall? Ask Prism to connect the numbers to shared meetings, objections, and next steps, then prepare coaching or a follow-up.

See the pipeline.
Find where to help.

Move from a rep’s numbers to their actual deals. See stage, owner, value, probability, and recent activity. Switch between new business, renewals, and partnerships, or filter the view to one person.

Ask Prism which deals have gone quiet, which promises are overdue, or where the customer has not agreed a next step. Open the client history to see the emails, notes, and meetings behind the answer.

Sales pipeline

New business

5 deals · $274K open
New revenue

Discovery

1

$22K
Dana Reyes
Discovery 10%Ruth

Qualifying

1

$36K
Lena Osei
Qualifying 25%Owen

Proposal

2

$48K
Carol Susi
Proposal 45%Brian
New note

$48K
Marcus Henderson
Proposal 70%Brian

Negotiation

1

$120K
Priya Nair
Negotiation 55%Ruth

Scroll sideways to explore the stages, or choose List.

The new business board contains the same five open deals used in the rep report. Choose Brian, Ruth, or Owen to inspect their pipeline.

Several CRMs.
One view of the business.

Bring the records behind the numbers into one workspace. Keep HubSpot for one team and Salesforce for another, or use Voice’s built-in CRM. Ask Prism for an update across both and review where each change will go.

HubSpotNew business teamVoiceOne workspaceSalesforceEnterprise team

Across your CRMs

Connected records, together in Voice

Client & dealCRMStageValueNext activity
Oakline Freight40-seat pilotHubSpotProposal$48,000Send revised quote
NorthmoorEnterprise rolloutSalesforceNegotiation$120,000Confirm next steps
Harbor VetSite rolloutHubSpotQualifying$36,000Schedule site visit
You ask Prism
“Move Oakline to Negotiation and add a follow-up for Northmoor on Friday.”

Two clients. Two CRMs. One request.

Review the destinations
HubSpotOakline: Proposal Negotiation
SalesforceNorthmoor: follow-up on Friday

Ready for your review

Changes come back into Voice, too.
Illustrative connected workspace. Try the voice update, then see a change arrive from the CRM.

Your connection setup defines the records, fields, and activities that sync in each direction.

Define how your
company works.

Company DNA gives Prism and Operator your instructions for the business. Define what a useful note contains, how a process should run, which sources to trust, and when the work needs a person’s decision.

The system also learns from the team’s edits and corrections. As a director, you can review those patterns with Prism, keep useful improvements, correct the wrong lessons, and give explicit direction for future work.

Teach it a better handoff, change a qualification rule, or clarify a reporting definition. Your company’s requirements guide the process while individual preferences can shape how people work with their assistant.

Explore Company DNA

Directors define the sources, steps, outputs, and review points for the work.

Notes and qualification.

Set the required questions: decision-maker, success criteria, blockers, and agreed next steps. Prism uses them in voice, chat, and scheduled debrief calls, asking for missing details and keeping uncertainty visible.

Operator procedures.

Define the source documents, order of steps, destination apps, owners, and review points. Specify what can run automatically, what needs approval, and which exceptions should come back to your team.

Reporting and revenue rules.

Define each KPI, who gets revenue credit, the reporting period, targets, and how the report reaches leadership. Correct a misleading comparison once, then direct later reports to use the agreed definition.

Customer answers and handoffs.

Set approved messaging, proposal formats, pricing boundaries, and delivery checklists. Give the system instructions for what can be promised and when it should ask the account owner or another team.

From the source
to the finished work.

Operator can read a meeting, check the account, update a spreadsheet, and prepare a handoff across your connected apps. Inspect the actual result and the sources behind it before deciding what to apply or share.

Review CRM changes across teams, combine regional numbers, or carry the sales agreement into delivery. The work keeps its destination, owner, and context.

HubSpotSalesforceGoogle SheetsGoogle DocsAsanaSlack
Explore more integrations

4 operations todo

Meetings · Account updates · Today 08:00

Approve 3 CRM updates from the meetings

The right changes go back to the right CRM, with the meeting attached.

Based on

Your teams use two CRMs. These updates keep each account in its home system while giving you one place to review the work. Edit a value or leave an item out before applying.

Proposed CRM updates

HubSpot

Acme Corp

Salesforce

Globex Industries

HubSpot

Thompson Insurance

Open a source, edit a proposed value, or review the project and team update before applying them.

A shared definition of the numbers.

Keep open pipeline, weighted pipeline, and closed revenue distinct. In the report, Operator applies a previous correction: separate won revenue from open opportunities and include the source date.

The agreement reaches delivery.

The customer handoff carries the scope, stakeholders, promises, and meeting into an Asana project, a shared brief, and a Slack update. Tasks keep the original conversation as a reference.

Automate the routine.
Keep exceptions visible.

Start by doing the work together. As Operator learns from your edits and corrections, choose the trigger, the tools it can use, and which actions still need review. Recurring reports, follow-ups, and CRM updates can then run within that scope.

A batch still needs attention to each item. Here, Operator handles a bounced address, holds a follow-up with an unsupported meeting reference, and prepares a separate correction from the actual email thread.

1 operations todo

Recordings · Commitments this week · Today 07:30

Send 10 follow-ups from this week’s reviews

One batch, with each promise and next step written for the person.

Based on

Each person gets their own recap and next action. I check every item as it runs and hold anything whose source does not match.

Template

Hi {{first_name}}, Thanks for the time this week. Here is what we agreed: {{commitment_recap}} Next step on our side: {{next_step}}. I will have it with you by {{due_date}}. Alex

Sub-commands

Sub-commands

0/10
Sarah Chen · Acme Corp

[email protected]

David Park · Acme Corp

[email protected]

Marcus Henderson · Globex Industries

[email protected]

Anna Kowalski · Silo & Co.

[email protected]

Julie Thompson · Thompson Insurance

[email protected]

Priya Rao · NovaTech

[email protected]

Robin Lee · NovaTech

[email protected]

Mike Torres · DataDrive

[email protected]

Piotr Nowak · Globex Industries

[email protected]

Ava Thompson · Thompson Insurance

[email protected]

Run the follow-ups, inspect the held item, then move it into its own operation to review the corrected draft.

The activity history keeps the sources, actions, and outcome with the operation. A new situation can come back to your team with the context needed to decide.

The context, ready
for your next decision.

Ask Prism what changed before the leadership review, or call while travelling between offices. It brings together shared account history, meetings, emails, files, and messages from connected apps.

When a deadline depends on someone else, Prism can message or call that teammate to ask. It supports most languages, so another region’s conversation can still inform your brief.

Its guidance draws on your Company DNA, previous corrections, and what worked for similar clients, alongside AI REV’s ten years of practical experience. Ask why, check the source, and decide the next move together.

Meet the model behind the work

The weekly sheet and account changes support the brief. Open pipeline stays separate from won revenue.

Start with a workflow.
Build on what you teach it.

Connect the work you want to improve.

Start with a team’s follow-ups, reporting, or customer handoff. Connect the relevant mail, calendars, CRM, files, and task apps, and define the result you need.

Share with the people involved.

Pipeline and client membership control shared context. Private notes and meeting transcripts stay private and out of CRM sync. Comments follow access to the item being discussed.

Review, correct, then expand.

Improve the result in Operator or explain the change to Prism. Its learning model carries those corrections into later runs. Choose which routines to automate as the work becomes reliable for your team.

A few practical details.

Can directors guide what the system learns?

Yes. Company DNA holds your instructions for notes, Operator procedures, reporting, customer communication, and handoffs. Review patterns learned from user corrections with Prism, clarify the intended behavior, and give new directions when a process or requirement changes. The resulting work remains something you can inspect and improve.

What should we define before automating a process?

Define the trigger, trusted sources, steps, output, destination apps, and responsible owner. Specify which actions need review and what should happen when information is missing. For notes, define the questions and required details; for reports, define the metrics, attribution, period, and audience.

Can I see sales performance by person?

Yes. Ask Prism to compare revenue, wins, conversion, activity, and open pipeline by rep, team, or region using your connected records. Operator can prepare the report with the period, metric definitions, attribution, and sources so you can inspect the result before sharing.

Can I check which deals need attention?

Use the pipeline’s owner and board views to inspect the actual opportunities, then ask Prism about quiet accounts, missing next steps, overdue commitments, or customer objections. Shared meetings, notes, and emails provide the context behind each deal.

Can different teams keep different CRMs?

Yes. Voice can connect multiple CRMs and keep linked records in their home systems. Each update has a destination, and changes can sync both ways according to your connection setup. You can also use Voice’s own pipeline without another CRM.

How do we get consistent notes without more admin?

Define the information that matters in your Company DNA. Prism uses the meeting and account context to ask useful follow-up questions when someone debriefs by voice, chat, or phone. Scheduled calls and the calendar’s missing-note view help the team catch up.

Can directors inspect what is behind a report?

Operator shows the sources, proposed changes, and activity for the work it prepares. Open the connected sheet or account context, edit a value, and check the reporting date before sharing. Open pipeline remains distinct from closed revenue.

What happens when an automated item needs a decision?

Operator can hold the item and explain what is missing. Review it separately, provide the correction, or move it into its own operation while keeping the rest of the work and its outcome visible.

Do shared pipelines expose private notes?

No. Sharing a pipeline or client gives access to its shared work. Private notes and recordings stay private to their owner and are excluded from CRM sync. Comments and references do not grant access to unrelated material.

Bring your process
to Prism.

Explore a CRM update, a handoff, or a leadership report. See how your team can prepare, review, and improve the work together.

Try the demo