# Call History Overview

Track status, transcripts, and call-level context for diagnostics and coaching. Read the Call History guide in Hello Alex documentation.

Canonical HTML: https://docs.helloalex.ai/article/call-history-overview

Path: [Documentation](/) / [Call History](/call-history)

## Overview

Call History is where operational truth lives after launch, because every completed attempt is recorded with status and context.

## How it works

- Rows show direction, outcome, and duration so teams can spot delivery patterns quickly.
- Detailed views add transcript and summary context, turning outcomes into actionable quality and support insights.
- The list is paged twenty-five calls at a time, and the count beside it reports how many calls the current filters match -- the answer to the filter, not the size of the page.

## Use cases

- Post-campaign QA review
- Support ticket evidence collection

## Tips

- Good to know: filtering before deep review shortens investigation time when campaign volume is high.
- Good to know: filters apply to the whole history rather than to the page on screen, so page one already holds the best matches. Narrowing is faster than scrolling.

## Call List

List scanning helps identify performance drift before it impacts larger outreach programs.

Open representative calls from each major outcome category for deeper review.

- Outcome and duration fields reveal high-level patterns across inbound and outbound traffic.
- Opening selected rows provides fast transition into transcript-level diagnosis.
- **Outcome:** Completed, no-answer, failed, etc.
- Good to know: campaign-name filtering is especially useful right after major launch waves.
- Launch health spot-check
- Outcome distribution review

## Call Detail

Call detail links qualitative conversation behavior to quantitative outcome data.

Capture key IDs and conversation snippets for coaching notes or support escalation.

- Transcript and AI summary expose where dialogue succeeded, failed, or required human escalation.
- Identifiers from detail view can be shared in tickets, enabling precise support reproduction.
- **Summary:** AI-generated call recap.
- Good to know: attaching the call ID with transcript context usually speeds support triage.
- Root-cause analysis
- Agent coaching feedback loops

## Filters, search and export

Narrow the history to the calls you are asking about, then take those calls out as a CSV.

Filter to one campaign and one outcome, then export that date range for reporting.

- Search matches a phone number, a contact name, or a conversation ID, so one call can be found from a support ticket.
- Filters combine: a date range with an outcome and a pathway answers "what failed on this campaign last week" in a single pass.
- Changing a filter returns you to page one, because page forty of the previous result means nothing under a new one.
- Export takes what the filters have selected -- a date range, the rows you ticked, or only the page on screen.
- **Date range:** Today, yesterday, the last 7, 30 or 90 days, or two dates you choose.
- **Status:** Completed, no answer, busy or failed -- the outcome the carrier reported.
- **Pathway:** One pathway, any pathway, or calls that ran without one.
- **Call type:** Single calls, campaign calls, or both together.
- **Duration:** Under a minute, one to three minutes, or over three.
- **Sentiment:** Positive, neutral or negative, where the call was analysed.
- **Recording and transcript:** Only calls that have one, or only calls that do not.
- **Export scope:** A date range, the rows you ticked, or the current page. The file carries date, direction, phone, name, duration, pathway, status, sentiment and cost.
- Good to know: a short duration together with a failed status is the quickest way to find a number that is not connecting at all.
- Good to know: a wide date range on a long history makes a large file. Filter first, export second.
- Post-campaign failure review
- Finding one call from a support ticket
- Monthly reporting

## Next step

Filter recent launches by campaign or date and investigate low-quality or failed outcomes first.

## Related documentation

- [More Call History guides](/call-history)