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. Each entry below ties the idea to the label you see in the app (April 2026).
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, usually surfaced per session as Campaign outcome in Call logs and as Disposition (plus Task status, Sentiment, Failure) under Call details → Call Insights → Details → Outcome when a campaign task exists. Call result in Call details is a separate telephony/summary line when the backend provides it. 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. In Call details, it appears only when present, under Call Insights → Details → Summary.
Transcript
The text of the conversation. In Call details, it appears in the left column below the AudioPlayer, either as a merged transcript plus Tool marker timeline or as Transcript (plain text). Use it for fast review; use search to match text, speaker labels, or tool names.
Recording
The audio for the session. In Call details, use the left-column player (Play / Pause, scrubber, Mute, open in new tab). In Call logs, the Recording column indicates availability at a glance. Use audio for tone, timing, and disputes.
Logged field
A value captured from the call. In the UI, structured extractions most often show under Call details → Call Insights → Details → Extracted data (one row per key, humanized). Webhook and CRM delivery are described in other articles.
CRM activity
The note, task, timeline event, or field update written into a connected CRM after the call. The call detail page does not always mirror CRM; see integration guides and Webhooks / Post-call webhook in Call Insights for raw delivery views when enabled.
Export
A point-in-time file of call-log data. In Call logs, start an export with Export CSV (current filters and search apply). Track jobs under Call log exports (open Export history from the call logs page header) and download from Download CSV when the file is ready.
Date range
The reporting window used to include or exclude calls. On Call logs, the active filter set (including time-related attributes) is what Export CSV and list counts use. Mismatches with other views usually come from different filters or page scope.
Filter
A structured condition from the Filters side panel on Call logs, or a Debug preset (platform staff) that applies a predefined set. Clear filters resets the table scope.
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.