Reporting Glossary

Use this glossary when operators, managers, and analysts need a shared definition for the most common call-log and reporting terms in Callaro. Consistent language is one of the fastest ways to reduce reporting confusion, improve handoffs, and make dashboard reviews more useful.

Prerequisites

Your team uses Callaro call logs or exports to make operational decisions.
Managers and frontline reviewers agree to use one shared set of definitions.

Recommended owner

Operations Manager or RevOps: owns the definitions used in reporting.
QA lead: keeps examples aligned with review guidance.
Team leads: reinforce the terms during training and reporting reviews.

How to use this page

Start with the term that caused confusion in a report, export, or call review.
Confirm how the term is defined here before changing dashboards or workflows.
If your team uses a custom internal term, document the relationship between that term and the Callaro term.
Revisit this page whenever you update outcome definitions or export logic.

Common terms

Call outcome

The business result assigned to a call. Outcomes should be actionable, consistently defined, and tied to a next step or reporting meaning.

Summary

A short explanation of what happened on the call. The summary gives quick context, while the outcome gives the structured business result.

Transcript

The text version of the conversation. Use it for fast review and pattern analysis when you do not need to hear tone or pacing.

Recording

The audio playback or audio record of the conversation. Use it for coaching, escalations, compliance-sensitive review, or when transcript accuracy is in doubt.

Logged field

A value captured from the call and stored in Callaro or sent to another system. Logged fields often drive reporting, routing, or CRM updates.

CRM activity

The note, task, timeline event, or field update written into a connected CRM after the call. This is what reps and managers often see first after a conversation ends.

Export

A point-in-time file containing selected reporting data from Callaro. Exports are useful for BI, finance, and leadership reviews, but they must be interpreted with the right filters and definitions.

Date range

The reporting window used to include or exclude calls in a view or export. Many reporting mismatches come from different date ranges, not different underlying call data.

Filter

A condition used to narrow a reporting view or export, such as campaign, time period, or outcome. Filters change the meaning of totals, so they should always be checked first.

QA sample

A small set of reviewed calls used to verify whether classifications, transcripts, recordings, or script behavior are trustworthy. QA samples help teams validate trends before making larger decisions.

Common errors and failure handling

Different teams use the same term differently

Document the official definition and make it part of reporting reviews. Shared language is an operational control, not just a documentation preference.

Export numbers do not match dashboard numbers

Check filters, date range, and metric definitions before assuming the data is wrong. The definition mismatch is often the real issue.

Reviewers disagree on whether a call fits an outcome

Use a QA sample, compare transcript and recording, and refine the definition so it leads to a consistent next step.

Acceptance checklist

Managers and operators can explain key reporting terms the same way.
Outcome, summary, transcript, and recording are used for the right purposes.
Export and dashboard reviews start with shared definitions.
Reporting disputes are easier to resolve because the language is clear.