Skip to content
NewPazau Agent 3 is here: Procedures that test themselves before they go live
Pazau Insights

Stop sampling. Score every conversation.

Pazau Insights QA-scores 100% of conversations, AI and human, against scorecards you write. It finds what's driving contacts, predicts CSAT where nobody answered the survey, and flags compliance misses the same day.

100% QA coverageScored within 4 minutes91% agreement with expert reviewersWorks with any helpdesk
Insights · Last 90 days
AI resolution rate
71.4%+6.2 pts
Cost per contact
$1.84−38%
QA score (100% coverage)
94.1+3.8
Resolution rate, weekly
Top contact drivers
  • Where is my order31%−12%
  • Returns & exchanges22%+4%
  • Damaged on arrival9%+41%
  • Promo codes7%−3%
100%
of conversations scored, up from the 1–3% a manual QA team samples
4 min
from conversation close to QA score, at p95
91%
agreement between Insights judges and expert human reviewers
r = 0.87
correlation between predicted and surveyed CSAT
Auto-QA · Custom scorecards

Your rubric, applied to every conversation, with evidence.

Write criteria in plain language, weight them, and mark some as compliance gates that fail a conversation outright. Insights scores each one with a quote from the conversation and a line from the Trace, so agents and QA leads can see exactly why.

  • Plain-language criteria. “Set accurate expectations on the delivery date” is a valid rule. No keyword lists.
  • Versioned rubrics. Re-score up to 90 days of conversations against a draft before you publish it, and keep trend lines intact.
  • Calibration built in. Your QA team grades a sample; Insights reports agreement per criterion and flags drift.
  • Coaching in the workflow. Scorecards appear in Inbox with comments, and agents acknowledge them there.
Lumen & Oak · QA · Conversation #2,190,441
Rubric: Delivery CX v7
89
Passed · 89 / 100
Agent: Priya N. (human) · scored 2m 51s after close
  • Verified identity before account changesCompliance · gatePass
  • Followed Procedure: Delivery exception v12Process · 20%18 / 20
  • Offered the correct remedy for the SLA breachAccuracy · 20%20 / 20
  • Set accurate expectations on new delivery dateAccuracy · 15%9 / 15
  • Empathy and toneSoft skills · 15%14 / 15
  • Resolved without unnecessary transferEfficiency · 15%15 / 15
  • Clear, correct wrap-up and dispositionProcess · 15%13 / 15
Evidence
Message 7 · Agent

“Your sofa will definitely arrive Thursday.”

Carrier ETA from get_shipment was a window, Thu–Sat. Procedure step 4 says never promise a single date.

Coaching note

Quote the carrier window and offer the delivery-tracking link instead of a date.

Shared with agent in InboxAcknowledged
Contact drivers

Know why customers are contacting you before the queue tells you.

Insights clusters every conversation into drivers automatically, across languages and channels. When a driver spikes more than 3σ above its 28-day baseline, you get an alert in Slack, Teams, or email with example conversations attached.

Auto-clustering

No taxonomy to maintain. Drivers merge across English, Spanish, and 40 other languages.

Spike alerts

Hourly detection, routed to the team that owns the fix, not just support.

Cluster to Procedure

Turn a driver into a draft Procedure in one click, then simulate it.

Why it escalated

Every handoff is summarized and grouped by root cause.

Insights · Contact drivers · auto-clustered
  • Where is my order18,420−12%
  • Delivery window changes9,310+6%
  • Assembly service booking4,870+2%
  • Damaged on arrival · Harlow sofa1,260+214%
  • Promo code errors980−31%
Spike: 4.1σ above 28-day baseline. 82% mention a split rear seam. Alert sent to #cx-ops and the merchandising team.

Lumen & Oak spotted a seam defect on one sofa model from a driver spike three days before returns data would have shown it, and automated delivery-exception handling on the way to a 38% lower cost per contact.

Customer stories
CSAT prediction · Compliance monitoring

Hear from the 89% who never answer the survey. Catch the miss before a regulator does.

Insights · Predicted CSAT · all conversations
4.47predicted on 100% · surveyed on 11%
3%
1★
5%
2★
9%
3★
27%
4★
56%
5★
Correlation with surveys
r = 0.87
Low-CSAT alerts today
38

CSAT prediction on every conversation

A model trained on your own survey history predicts a 1–5 score for every conversation, with a confidence band. Low predicted scores open a follow-up task in Inbox while the customer can still be won back.

Insights · Compliance monitor · Today
  • Call-recording notice (two-party states)Clean
  • Reg E disclosure on card disputes3 flagged
  • No guarantee of claim outcome1 flagged
  • Mini-Miranda on collections callsClean
  • Cancellation offered within 2 turns (FTC click-to-cancel)Clean
3 flagged → routed to compliance queue · evidence and trace attached · export for regulator

Compliance monitoring, not compliance sampling

Required disclosures, prohibited promises, and consent rules are checked on every conversation and call. Flags route to your compliance queue with evidence, and exports are ready for examiners. Meridian Mutual scores 100% of claims calls against state claims-handling rules.

AI vs human benchmarking

One scorecard for AI and people. Same bar, same evidence.

Because Pazau Agent and your human team are scored on the same rubric, you can see where the AI is ready to take more volume and where people still do better. Split any metric by driver, channel, language, or Procedure version.

  • Decide which drivers to hand to Pazau Agent next, with the numbers to back it.
  • Compare resolution rate before and after every Procedure publish.
  • Spot where handoffs happen too late, or too early, by root cause.
  • Report cost per resolution for AI and human side by side to finance.
Insights · AI vs human · Returns & exchanges · 30 days
Metric Pazau Agent Human team
  • QA score93.888.4
  • Policy adherence99.2%96.1%
  • Predicted CSAT4.524.61
  • Median handle time1m 52s9m 40s
  • Reopened within 7 days3.1%4.4%
  • Cost per resolution$0.75$6.90
Humans score higher on CSAT for “damaged item” returns. Consider a handoff after the photo step.
Everything in Insights

Built for the people who run support, not just watch it.

Calibration sessions

Run blind calibration with your QA team and see agreement per reviewer and per criterion.

Rubric diffs

Compare two rubric versions side by side, broken down by criterion, before you roll one out.

Agent and team views

Scores, trends, and coaching notes per agent, with team leads seeing only their teams.

Fairness checks

Score distributions by language and channel, so no customer group is served worse.

Warehouse export

Scores, drivers, and Traces sync to Snowflake, BigQuery, Databricks, or S3 every 15 minutes.

Custom dashboards

Build views by any field, compare custom date ranges, and schedule reports in the owner's time zone.

Works on conversations that never touched Pazau Agent.

Insights reads from Pazau Inbox and Voice natively, and from Zendesk, Salesforce Service Cloud, Genesys, and Amazon Connect through our connectors. Many teams start here, then add Pazau Agent once they can see which drivers are ready.

See integrations
Coverage
100% of chat, email, messaging, and voice
Time to score
Under 4 minutes after close (p95)
Judge agreement
91% with expert reviewers
Languages
45+ for text, 30+ for voice
Retention
Configurable, 30 days to 7 years
Training
Never trains foundation models on your data
FAQ

Insights questions.

How accurate is automatic QA compared with our human QA team?+
On our internal benchmark, Insights judges agree with expert human reviewers 91% of the time. During onboarding we calibrate on a sample your team grades, and we report agreement per criterion so you can see where to tighten wording.
Can we use our existing QA scorecard?+
Yes. Paste it in. Each line becomes a criterion you can weight, and any criterion can be marked as a compliance gate that fails the conversation regardless of total score. Rubrics are versioned, and you can re-score 90 days of history against a draft.
Do we need Pazau Agent or Pazau Inbox to use Insights?+
No. Insights connects to Zendesk, Salesforce Service Cloud, Genesys Cloud, Amazon Connect, and others. Conversations in Pazau Inbox and Voice are scored natively with full Trace detail.
How does CSAT prediction work?+
Insights trains a per-customer model on your own survey history and conversation outcomes. It predicts a 1–5 score with a confidence band for every conversation. It never trains foundation models, and your data isn't used for any other customer.
What does “compliance monitoring” cover?+
Any rule you can describe: required disclosures (recording notices, Reg E, Mini-Miranda), prohibited statements (guaranteed claim outcomes, medical advice), and process rules (identity verification before account changes). Flags route to a queue with evidence and export for regulators.
How is Insights priced?+
Insights is part of every Pazau plan, with scorecards, compliance monitoring, and warehouse export on Business and Enterprise. Scoring conversations from a third-party helpdesk is quoted per conversation volume. The pricing page has the full comparison.

See what your team could resolve.

Bring 1,000 of your real conversations. We'll show you, in a 30-minute call, how many Pazau Agent resolves end-to-end.