Glake
Get in touch
Development · Insurance

AI quality control for sales calls

The system pulls call recordings from the phone system, transcribes each conversation, scores reps on four criteria, and exports the results to a Google Sheet every day

Intellekt Razvitie
Intellekt Razvitie · deployed in an insurance company’s sales department
Discuss a similar projectAll case studies
AI quality control for sales calls
5–15% → 100%
call review coverage
4
scoring criteria for every call
1
daily report, ready in Google Sheets
450
calls a day, processed without human input
01 · The challenge

What the client needed

Intellekt Razvitie is a systems integrator that rolls out automation and AI for its clients. For one of them — an insurance company with a telesales team — it hired us to build a system that checks call quality.

In phone sales, everything hinges on the conversation: how the rep uncovers the customer’s needs, handles objections, and secures the next step. To stay on top of those conversations, a supervisor listens to recordings and scores every rep.

Listening took three to five hours a day, and coverage stayed low: only 5–15% of calls were reviewed manually. Scores were subjective — different reviewers judged the same situation differently. There was no single spreadsheet with each rep’s history, and reps got feedback only a few days later.

By the time a call came up for review, the rep had already repeated the mistake, and as the team grew, manual QA could no longer keep up with call volume.

Off-the-shelf tools didn’t fit: they didn’t integrate with the company’s phone system, Beeline’s cloud PBX, and couldn’t be tailored to the client’s sales methodology. The client needed a system that collects recordings, scores conversations against the company’s own rules, and hands the supervisor a ready-made report.

What stood in the way
Manual listening
Supervisors spent three to five hours a day on it and still checked only 5–15% of calls.
Subjective scores
Different reviewers scored the same situations differently, and there was no running history for each rep.
Delayed feedback
Reps heard about their mistakes days later, and as the team grew, the analyst couldn’t keep up with call volume.
02 · The solution

What we built

01

No listening required

The supervisor no longer downloads recordings or listens to calls: every call that qualifies for scoring gets checked, not just a sample.

02

Consistent scoring

The criteria follow the company’s sales methodology, so every rep is scored by the same rules, not by an individual reviewer’s opinion.

03

Full history in one sheet

Scores for every call from every rep live in one Google Sheet, and the “Summary” tab shows each rep’s average score.

04

No more delayed feedback

A new report comes out every day, so the supervisor can see right away who needs coaching and on what.

03 · Demo

How one call gets scored

Here’s how a single call moves through the system, from the recording to a row in the report.

Step 1

Fetching the recording

On a set schedule, the system queries the Beeline cloud PBX API, pulls the list of newly completed calls, and downloads the recordings. Calls below a minimum length and calls with no speech are filtered out right away — there’s nothing to score.

Step 2

Transcription

The recording is transcribed and split into the rep’s lines and the customer’s lines. Speakers are identified by what they say, so the system tells them apart in calls from both the direct and agent sales channels. Thanks to that split, only the rep’s words get scored: their questions, objection handling, and what they agreed on.

Call scores by criterion, with short explanations
Call scores by criterion, with short explanations
Step 3

Scoring

A language model checks the conversation against the criteria: whether the rep uncovered the need, how they handled objections, whether they secured a next step, and how actively they drove the call. It scores each item with a short explanation, and the system calculates the total score and issues a verdict. On top of the four core criteria, each product — OSAGO (mandatory auto liability insurance), CASCO (comprehensive auto insurance), and mortgage insurance — has its own checklist based on the company’s methodology.

Total score, verdict, comment, and recommendations for a call
Total score, verdict, comment, and recommendations for a call
Step 4

A row in the report

Results go to a Google Sheet, one row per call: rep, date, scores by criterion, total score, and comment.

More screenshots

The “Summary” tab: verdict breakdown and scores by channel and by rep
The “Summary” tab: verdict breakdown and scores by channel and by rep
04 · Tech stack

Stack and approach

Python + FastAPI
The backbone of the system: runs every step, from fetching the recording to the final report
Beeline cloud PBX API
The source of call recordings
Speech recognition
A model that transcribes speech into text
LLM
A language model that scores each call against the criteria and writes a comment
Google Sheets
The spreadsheet where the finished report lands every day

Also used: PostgreSQL — call and score storage · APScheduler — job scheduling · Docker — server deployment

How it works

Collection · scheduled via FastAPI + APScheduler
Beeline cloud PBX API
newly completed calls
Filtering
short and silent calls
Transcription
Speech recognition
split into rep and customer lines
Scoring
LLM
4 criteria and a product checklist
Total score
verdict and comment
PostgreSQL
calls and scores
Report · daily
Google Sheets
one row per call
“Summary” tab
average score per rep
05 · Results

What the client got

The supervisor no longer listens to calls by hand: the system scores every conversation automatically, and results for every rep live in one spreadsheet.

100%
of calls scored, up from 5–15%
4
criteria, the same for every rep
450
calls a day, processed without human input
One consistent standard instead of each reviewer’s subjective opinion
Each rep’s full history in one spreadsheet
A fresh report every day, not days after the fact
Delivered to the client with source code and documentation
06 · For your business

Who else this works for

A similar system fits any business where customer conversations drive revenue directly and there are simply too many to review by hand.

Sales teams and call centers
Scoring every call against the script, reports by rep, training material, and next-day feedback
Clinics and service centers
Monitoring front-desk calls — the greeting, appointment booking, and offers of additional services
Restaurants, bars, and hotels
Checking reservation calls — whether the host confirmed the details, explained the booking terms, and offered an alternative
Banks and insurers
Monitoring adherence to scripts and call requirements, and flagging calls that need a manual review

We build solutions like this around your needs: turnkey AI products, AI agents and automation, integrations, and data.

Our services
Get in touch

Want results like these?

Tell us about your project — we’ll talk it through and show you how to make this work for your business

We’ll set up a short call
We’ll scope your task and estimate it within 1 business day
You’ll get a clear implementation plan and transparent pricing
Alexander Yarygin
Founder, Glake
Replies personally
What can we help with?
Select one or more
or
Chat on LinkedIn

More case studies

Technical audit of an AI auto-reply system
AuditE-commerce

Technical audit of an AI auto-reply system

Independent audit of AI review replies on Wildberries: quality, why drafts get edited, and a fix plan

KEO
AI operations monitoring agent
DevelopmentMarketplaces

AI operations monitoring agent

Pulls Wildberries metrics, computes KPIs, and flags sales and ad anomalies

MPstats
AI sales automation for new-build apartments
DevelopmentReal estate

AI sales automation for new-build apartments

Application intake, document scanning, and reservations — no manual data entry

Tera
All case studies