PerfCopilot
A performance review draft for a contact-center team with each claim connected by citation lines to RingCentral call and message activity, queue, and disposition icons.

Turn RingCentral call activity into fair, cited reviews for your support and sales teams

PerfCopilot reads each rep's RingCentral activity — call and message volume across your queues and outbound lines, talk time, direction, and how interactions were dispositioned — then drafts a performance review where every claim links back to the activity that backs it, bias-checked before you ever hit send. By default it reads metadata only; call transcripts are pulled in only when an org admin opts in.

Connect RingCentral — free up to 5 seats → · metadata read-only, no credit card

✓ Call/comms metadata by default · ✓ Transcripts only with org-admin opt-in · ✓ Bias-checked

What PerfCopilot reads from RingCentral (two clearly separated tiers)

RingCentral is your whole communications backbone — inbound support queues, outbound sales lines, and team messaging in one place. PerfCopilot is deliberate about which part of that it touches, and we put it in writing:

Tier 1 — DEFAULT (metadata only, the moment you connect):

No call audio. No transcript text. No message bodies. Metadata is enough to write an honest, outcome-aware draft for most contact-center and sales reviews — and every line of it is cited back to the activity record that supports the claim.

Tier 2 — OPT-IN ONLY (call transcripts, behind explicit consent):

If your organization wants reviews to reference what was actually said on a call — coaching moments, objection handling, de-escalation — an org admin can turn on transcript access. It is off by default, scoped to the sales and success roles you designate, logged, and revocable. Nothing reads transcript content until that switch is flipped on purpose.

This is the centerpiece. We do not blur the two tiers, and we do not let a marketing line imply we read your calls by default. The honest version is also the version your security and compliance reviewers can sign off on — see /security. Want the full source list? See all integrations.

Built for contact centers and multi-channel teams

Most "AI review" tools were built for one engineer and one repo. RingCentral teams are a different shape, and PerfCopilot is built for that shape:

Why metadata + a bias check beats a raw call dashboard

RingCentral's own analytics and most contact-center dashboards are built to show you more numbers: calls per hour, average handle time, longest hold, occupancy. Those are operations metrics. Dropped into a performance review unfiltered, they quietly reward the wrong things — the rep who rushes callers off the line to shrink handle time, or the one whose dial count is high because their calls go nowhere.

PerfCopilot does the opposite. It reads the same metadata, then:

A dashboard tells you a rep made a lot of calls. A cited, bias-checked review tells you what those calls did — and shows the activity behind the claim.

RingCentral analytics vs. a cited, bias-checked draft

RingCentral / contact-center analytics dashboardsPerfCopilot
Reads call & comms activity
Cites the activity behind each claim✗ (charts, not citations)✓ (transcript-level detail only when opted in)
Bias & fairness check on the draft
Writes the review — not just a dashboard✗ (metrics only)
Combines RingCentral with CRM + email evidence✓ (18 integrations)
No migration — exports into Lattice/15Five/BambooHR
Costbundled into your comms/CC seatFree up to 5 seats · Pro $4.99/seat/mo annually

PerfCopilot drafts a full-cycle review from a rep's RingCentral activity (metadata by default) in under 5 minutes — versus an evening cross-referencing queue reports and call logs by hand.

Why "cited to the call activity" matters

When a contact-center or sales rating gets challenged — in a calibration session, a PIP discussion, or a promotion case — "they're a strong performer" is not enough. A cited review shows the queue coverage, the outbound effort, the resolution pattern that backs the rating, linked to the underlying RingCentral activity. With transcript access opted in, it can point to the specific coaching-worthy or objection-handling moment too. Defensible reviews start from evidence the rep can see, not a manager's recollection of a busy quarter.

Run the performance review generator across RingCentral and your CRM at once, then see pricing — free up to 5 seats.

Connect RingCentral — free up to 5 seats → · metadata read-only, no credit card

FAQ

Does PerfCopilot transcribe or read my team's RingCentral calls? Not by default. By default PerfCopilot reads metadata only — call and message counts, durations, direction, queue and disposition data, and timestamps. Call transcripts are opt-in only: an org admin must explicitly turn them on, scoped to the sales or success roles you choose. It is off until someone enables it on purpose, and it can be turned back off.

What does it read by default, the moment I connect? Call and message activity metadata: how many calls and messages, how long, inbound vs. outbound, which queues, how interactions were dispositioned, and when. No call audio, no transcript text, no message bodies — unless transcripts are explicitly opted in.

Does it just rank reps by call volume or handle time? No. Volume and average handle time are inputs, not the verdict — and over-indexing on them is exactly what the built-in bias and fairness check guards against. PerfCopilot writes an outcome-aware draft that weighs how work resolved across your queues and lines, not a leaderboard of who dialed the most.

Is this OK with our privacy and compliance team? That's why the model is two-tier and written down. Metadata-by-default plus opt-in, role-scoped, logged transcript access is built to pass a security review — see /security for the data-handling detail. PerfCopilot is read-only and never writes anything back into RingCentral.

Do I have to move off Lattice, 15Five, or BambooHR? No. PerfCopilot drafts from RingCentral activity and exports the finished review into the HR platform you already run. It's a writing layer — nothing to migrate, no new system of record.