Skip to content

Bolna call analytics

Score every Bolna call against rules you approved, and group the calls that failed by the reason they failed rather than by status code.

Bolna reports a call funnel: dialled, connected, a person on the line, a two-way conversation, and a qualified conversation at thirty seconds or more.

That last step is the closest thing to a quality signal, and it is a stopwatch. A thirty-second call where the agent said the wrong thing qualifies.

What Bolna does read

Extractions pull structured answers out of a transcript against questions you write, and return a confidence score and the reasoning behind each one.

That is genuinely more transparency than most platforms offer. It still answers your question about the call rather than checking the call against a standard.

What we add

BolnaDid the call connect, last, and produce the fields you asked for.
EvidovaDid the agent do the job, against rules you approved and can change.
BothVolume and outcome on one side, quality and cause on the other.

Failures are grouped by cause, not by status. A list of eighty failed calls is work. Four reasons ranked by how many calls each cost is a decision.

Two things about Bolna specifically

Bolna times a whole call to the second, with one timestamp for all of it, so turn order inside a call is reconstructed rather than read.

It also sends the transcript as one block of text. A line that begins with neither speaker prefix is left out rather than attributed to the wrong party.

Bolna does not sign its deliveries, so the token in the webhook path is what protects the URL. Anyone holding it can post to your workspace.

Read next

This page as markdown