AI speech analytics for calls

We put speech analytics into your contact center: recognize 100% of calls, score each one against the QA scorecard, collect sales insights, and flag compliance issues. The base covers 1,000 hours per month, with a 150k RUB/month retainer and a 300k RUB setup.

We score every call: recognize speech, check the QA scorecard, surface objections, and flag script violations.

Pricing

from ₽150,000

per month

This is the lower bound of a project. We scope the exact quote after a brief: it depends on volume and the number of integrations.

What's included

Capabilities

Scoring every call

We recognize 100% of recordings and score every conversation: an agent sees the score, the scorecard items, and the excerpts that lowered it.

A scorecard from your script

The scorecard comes from your script: greeting, needs discovery, next step, and forbidden phrases become weighted items with a threshold.

Sales insights

We collect objections, reasons for refusal, and the next step named across all calls: a manager sees topic frequency, customer wording, and example dialogs.

Compliance flags

We mark script violations and forbidden phrases: each flag carries a timecode, a quote, and a link to the recording, so review runs on evidence.

How we work

From request to result

  1. 1

    Recording and telephony audit

    We listen to 3-5 hours of recordings, check the codec, channels, and archive, and compare your script and scorecard with real conversations.

  2. 2

    Scorecard and taxonomy

    We build the scorecard items, weights, and thresholds, then set objection topics and the list of forbidden phrases with the QA lead.

  3. 3

    ASR and scoring pipeline

    We connect recognition and diarization, set scoring rules, check accuracy on a labeled sample, and fix disputed items.

  4. 4

    Pilot and retainer

    We launch a pilot on your stream, compare scores with a manual QA sample, ship the dashboard, and move to a monthly retainer.

Who it fits

Check if it fits you

Good fit

  • From 500 recorded hours per month

    At that volume the sample covers every channel and shift, so we tune the scorecard and thresholds on enough statistics.

  • A scorecard and an owner

    A QA lead owns the items and weights, accepts disputed scores, and reviews thresholds with the team once a month.

Not a fit

  • Poor recordings

    Noise, cut-offs, and narrow bandwidth lower recognition accuracy, so a clean channel and a normal codec come first.

  • Legal and HR work without a policy

    Disciplinary review and employee scoring need an agreed policy for recording, access, and storage, signed by legal and HR.

Track record

What you get

1,000 h/mo

Hours in the base

The base covers 1,000 hours of recordings per month: recognition, diarization, and scoring run in one stream.

150k RUB/mo

Retainer in the base

The monthly retainer in the base setup is 150k RUB/mo. It includes processing 1,000 hours, scorecard support, and scoring rule updates.

100%

Every call scored

Scoring covers 100% of recordings. A manual QA sample is used for disputed items and threshold calibration.

Scope of work

What the delivery includes

QA scorecard

Scorecard items with weights, thresholds, and phrase examples. The card covers greeting, needs discovery, argumentation, next step, and forbidden wording.

Scoring pipeline

Recognition, diarization, and scoring rules in one pipeline. It takes recordings from telephony, computes the score, and writes the result to the database.

Quality dashboard

A dashboard with scores by agent, topic, and shift, a flag list, and links to recordings. The QA lead sees monthly movement and reviews disputed calls.

How it works

How the system is built

  1. Recognition and diarization

    A call recording goes into recognition, diarization separates the agent from the customer, and the model adds timecodes. Text arrives with role labels, so scoring sees who said each phrase.

  2. Scoring against the scorecard

    Scoring rules match turns against scorecard items, award points, and keep a quote with a timecode. Every call gets a score, and disputed items go to the QA lead for manual review.

  3. Insights and compliance

    Analytics groups objections, topics, and next steps across all calls, while compliance rules mark forbidden phrases. A manager sees topic frequency and specific dialogs, and legal gets flags with quotes.

Limitations and cost

Where the solution pushes back

  • 01

    Recording quality

    Recording quality sets the scoring ceiling. Wideband audio and a clean microphone give the model more words to work with, so the audit starts with a codec check and a channel improvement plan.

  • 02

    Language and domain

    Language and domain set the glossary and scoring rules. Russian and English run at the start, and industry terms join the glossary during the audit, so the model hears professional vocabulary with more precision.

  • 03

    Recording policy

    Recording policy sets retention, access scope, and pseudonymization. Legal and HR sign the document before launch, so the team works to clear rules every day.

Stack

Technologies

The technologies we use in our work and their role in a project.

Recognition and storage

We recognize call recordings through Whisper and Yandex SpeechKit, pass scoring events through Kafka, store scores and scorecards in PostgreSQL, and compute hourly and topic aggregates in ClickHouse.

A speech recognition model: it transcribes recordings in batches, runs on your server, and we switch to it on difficult recordings.A cloud service for Russian speech recognition: it returns text and timecodes and helps on phone channels with narrow bandwidth and noise.The event bus: it carries call start, the finished transcript, and the scoring result into a queue while keeping message order per call.Stores transcripts, scorecards, scores, and compliance flags: we build reports from this data and review disputed calls with the QA lead.Computes aggregates by hour, agent, and topic: average score, flag share, and objection frequency across millions of rows in seconds.
Budget estimate

Cost calculator

This is an indicative range, not a quote. We scope the exact estimate after a brief: it depends on volume and the number of integrations.

Call hours per month

1000

QA depth

CRM integration

Add-ons

Support

Year one: updates and monitoring, a reply within 2 business days.

Service

AI speech analytics for calls

The estimate covers our team's work. Hardware, third-party service licences and travel are added on request.

Estimated cost

₽2.1M

Timeline

3 wk

Questions

Frequently asked questions

Which languages and domains does analytics cover?

Russian and English at the start, with more languages added through a dictionary. The domain sets the term glossary and topic set: banking, telecom, delivery, and product support each run with their own dictionaries.

How do you connect to telephony?

Through a recording export from your PBX or a stream from SIP recording. We set the file pickup schedule, formats, and reprocessing, while the number and routing stay yours.

Where do recordings and transcripts live?

Inside your perimeter: audio and text sit in PostgreSQL and object storage, with role-based access. Your policy sets retention and pseudonymization, and we connect external services on your decision.

How long does setup take and how does the work run?

Setup takes three weeks: audit, scorecard, pipeline, and a pilot on your stream. After that the work runs on a monthly retainer at 150k RUB, and setup costs 300k RUB.

What teams add to this service

Ready to discuss your task?

Leave a request – we'll get back with a proposal and a preliminary estimate.

Contact us