Turn Zoom meeting activity into fair, cited reviews for customer-facing teams

Your CSMs, solutions engineers, and onboarding specialists do their best work on camera — in demos, QBRs, kickoffs, and client check-ins. PerfCopilot reads each person's Zoom meeting metadata by default — how many meetings, how long, with whom, in what role — and drafts a performance review where every claim is cited back to the meeting activity that backs it, bias-checked before you send. Transcripts stay off unless an org admin explicitly turns them on.

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

✓ Meeting metadata by default · ✓ Transcripts only with org-admin opt-in · ✓ Bias-checked

What PerfCopilot reads from Zoom (two tiers, you choose the second)

This is the whole point. Zoom is where customer-facing teams live, so the data boundary has to be unmistakable. PerfCopilot uses two tiers, and the second is off until you deliberately turn it on.

Tier 1 — DEFAULT (meeting metadata, read-only):

• Meeting counts — how many scheduled sessions a person hosted or attended over the cycle, the basic measure of customer coverage
• Durations — total and per-meeting time on camera, so a QBR isn't weighed the same as a two-minute sync
• Timestamps — when meetings happened, the basis for cadence (steady client contact vs. quarter-end cramming)
• Participant counts — how many people were in the room, a proxy for the scope of a session
• Host / attendee role — whether the person ran the meeting or supported it, which separates "owned the QBR" from "sat in"

Every one of these becomes a cited line in the draft — "hosted 14 customer QBRs across the half, averaging 47 minutes" — pointing to the meeting activity behind the claim. No recording, no transcript, no words said in the room.

Tier 2 — OPT-IN ONLY (transcripts & recordings):

• Off by default. Reading meeting content requires explicit org-admin consent and is scoped to the sales/success roles where call review is already part of the job.
• When enabled, transcript detail lets a draft cite what happened in a meeting — a discovery question that unblocked a deal, a renewal save — not just that the meeting occurred.
• Even then it is read-only, role-scoped, and revocable. PerfCopilot never flips this on for you.

The honest default: out of the box, a Zoom line describes a pattern of meeting activity, never a quote. Content citation is a deliberate, admin-gated upgrade — not the starting state. Want the full source list? See all integrations.

Built for customer-facing teams who live in meetings

Zoom isn't a side channel for these roles — it's the job. A CSM's quarter is a calendar of renewals and QBRs; a solutions engineer's is back-to-back demos; an onboarding specialist's is a pipeline of kickoff sessions. That makes meeting activity a genuinely useful work-coverage signal that code- and ticket-based sources can't see:

• Customer coverage, not keystrokes. Meeting counts and participant scope show how much of the book of business a CSM actually touched — the accounts carried, the renewals worked, the kickoffs run.
• Cadence tells a story. Steady client contact across the cycle reads very differently from a flurry of meetings the week before reviews. Timestamps make that visible, fairly.
• Role separates owners from observers. Hosting a QBR is not the same as being a fifth attendee. The host/attendee split keeps the review honest about who carried the session.
• It's the half of the job GitHub and Jira miss. For client-facing people, the deliverable is the meeting. PerfCopilot makes that work countable and citable instead of invisible at review time.

Pair it with email and CRM activity and you get a review that reflects the whole customer-facing cadence — meetings, follow-through, and account ownership — not a single dashboard number.

Why meeting metadata + a bias check beats a meeting-hours leaderboard

A raw "hours in Zoom" leaderboard rewards the wrong thing: calendar-stuffing. The person who books the most back-to-back meetings looks like the top performer, while the CSM who resolves an escalation in one focused 30-minute call looks idle. That's exactly the trap PerfCopilot is built to avoid:

• Volume is not value. More meetings, longer meetings, and bigger rooms are not automatically better outcomes. A leaderboard can't tell a saved renewal from a meeting that should have been an email.
• The bias check guards against rewarding busyness. PerfCopilot's built-in bias check flags drafts that lean too hard on raw meeting volume or duration — the visibility bias that punishes efficient, outcome-focused operators — so the metadata informs the review without distorting it.
• Outcome-aware by design. Meeting activity is framed as coverage and cadence, then weighed against the outcomes that show up in CRM, email, and (if opted in) what actually happened on the call. The question is "did they cover and move their accounts?" — not "who logged the most hours?"

The honest framing: Zoom metadata answers "how much customer-facing work did they carry, and how steadily?" CRM and email answer "did it move the account?" You need both, weighted fairly — which is why a leaderboard never becomes the rating.

Zoom dashboards / meeting analytics vs. a fair, cited review draft

PerfCopilot turns a review cycle of Zoom meeting activity (metadata by default) into a cited, bias-checked draft in under 5 minutes — versus exporting and pivoting meeting reports by hand.

Why "metadata by default, transcripts opt-in" matters

Most meeting-analytics tools either ignore content entirely (just charts) or quietly parse every recording to score "talk ratio" and "sentiment." PerfCopilot refuses both extremes. By default it reads only meeting metadata — counts, durations, participants, role — so you get real customer-coverage signal without anyone's words leaving the meeting. Reading transcripts or recordings is a separate, deliberate choice that only an org admin can make, scoped to the sales and success roles where call review is already standard practice. That two-tier boundary is the difference between a fair work signal and surveillance. Plainly: we read meeting metadata by default; we read meeting content only when you explicitly turn it on.

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

Connect Zoom — free up to 5 seats → · metadata by default

FAQ

Does PerfCopilot read or record my Zoom meetings? Not by default. Out of the box PerfCopilot reads only meeting metadata — meeting counts, durations, timestamps, participant counts, and host/attendee role. Reading transcripts or recordings is opt-in only: it requires explicit org-admin consent and is scoped to sales and success roles. PerfCopilot never enables meeting-content access on its own.

Then what does it actually read from Zoom by default? Read-only meeting metadata: how many meetings a person hosted or attended, how long they ran, when they happened, how many people were in the room, and whether the person was host or attendee. That becomes a labeled meeting-activity signal — "hosted 14 QBRs averaging 47 minutes" — never a quote from inside the call.

Does it just count meeting hours? No. A raw hours-in-Zoom count rewards calendar-stuffing and penalizes efficient operators. PerfCopilot frames meeting activity as customer coverage and cadence, then weighs it against outcomes in CRM and email. Its built-in bias check flags drafts that over-weight raw meeting volume or duration, so busyness never becomes the rating.

Is the Zoom connection private and compliant? Yes. The default connection is read-only and scoped to meeting metadata, so meeting content is never exposed. Transcript and recording access is a separate, admin-gated, role-scoped, revocable opt-in. This is documented on our security page and matches our two-tier boundary for meeting-content sources.

Do I have to leave Lattice or 15Five to use this? No. PerfCopilot is a writing layer. It drafts from your Zoom meeting activity (combined with CRM, email, and other sources) and exports the finished review into the HR platform you already run. Nothing to migrate.