- Was the caller audio clear and noise free? This is a useful filter to have for downstream analytics tasks.
- What was the outcome of the call? If it was a sales call, that is very important information to gather.
Tazo Large answers one
choice question per request, so each question is its own call on the
same recording. The two calls run in parallel.
Setup
calls/ folder.
Define the questions
Each question has a short context that tells Tazo what kind of recording it is hearing, the question, and acriteria map from option ID to description. Descriptions are what Tazo
reads, so write them in plain language.
Ask Tazo
Turn the quality answer into a verdict
Flagging a call as low quality drops it from downstream analytics, so the quality verdict needs a high bar: at least 80% confidence and a 20-point lead over the runner-up. If Tazo is not sure, the call for simplicity sake is reported as clear.Analyze the calls
Build on it
- More checks. Add a question with its own context and options, and ask it in the same
gather. For example, whether the customer was satisfied at the end of the call. - Follow-up questions. Ask a second question only when the first finds something. For example, ask how many times a distracting sound happens only after a distracting sound was heard.
- Batch review. Run
analyze_callover a folder and send low-quality and uncertain calls to a person.
Limitations
- The thresholds are not calibrated quality guarantees.