Your Call History Is a Business Report You're Not Reading

Call detail reporting turns a log your phone system already keeps into three answers: what hours your callers actually dial, which published numbers produce calls, and what share of calls nobody picked up. There is nothing to install and no survey to run. The data exists the moment your first call connects.

Most offices never look. The log sits in the portal, one row per call, while the decisions that depend on it get made from memory.

What is in a call detail record?

A call detail record (CDR) is one row per call. It carries the date and time, the direction, the calling number, the number or extension dialed, the duration, and how the call ended — answered, no answer, or busy.

That is a small set of fields, and it is enough to answer questions people normally guess at. Signal keeps a CDR for every call and exposes it as searchable call history in the portal, filterable by date range, direction, extension, and number. Call reporting basics covers the search itself.

When do people actually call you?

Pull one month of inbound calls and group them by hour of day and by weekday. Almost every small office finds its volume concentrated in windows narrower than its posted hours.

The typical shape: a hard spike in the first ninety minutes after opening, a trough over lunch, a smaller rise late afternoon, and Monday outrunning every other day. None of that is universal, which is why you should look at yours.

Three things to check specifically.

Calls that arrive before you open. If your published hours start at 8:00 and a meaningful block of calls lands between 7:15 and 8:00, your after-hours greeting is doing more work than you think. Go listen to it. A message that only says "we are closed" spends real call volume on nothing.

The lunch hour. If volume barely dips at noon but coverage does, that is a schedule problem with a routing fix — a lunch time condition that sends calls to a queue rather than to a ringing empty desk. Building a business-hours route covers the open, closed, and lunch pattern.

The first ninety minutes. If most of your day's calls arrive before 9:30 and one person covers the front desk, you have found your bottleneck.

Which of your numbers produce calls?

Filter inbound call history by the number dialed. Every number you own reports its own volume separately — the main line, the number you kept after a move, the number printed on a truck, the one in an old directory listing.

Two findings are common, and they point in opposite directions.

A number with zero inbound calls in ninety days is a maintenance line item with no return. Before releasing it, confirm nobody has it printed on something durable — releasing a number is not reversible.

A number with real volume routing to the wrong destination is the more expensive finding. An old location's number pointed at a voicemail box nobody checks will not announce itself. It shows up as a number with steady inbound and no answered calls. Pointing a phone number at a destination is the fix, and it takes about a minute.

What share of your calls go unanswered?

Count inbound calls with a no-answer disposition, divide by total inbound calls, and you have a missed call rate. Most offices have never computed this number, and computing it changes behavior faster than any other single figure in the log.

Read it carefully, because "unanswered" covers three different failures:

1. Rang out. The call reached a phone or a ring group and nobody picked up. This is a coverage problem — usually one phone on one desk. Ring groups and the front-desk gap covers the ten-minute version of the fix.
2. Abandoned in a queue. The caller waited and hung up. This is a capacity problem, and queue reporting breaks out wait times and abandons separately. See queue reports.
3. Went to voicemail. Not necessarily a failure, unless nobody works the mailbox. A voicemail nobody returns is a missed call that produced paperwork.

Split by extension and the picture sharpens. Signal's weekly call report emails a missed-by-extension breakdown, so a pattern that would take a query to find arrives without anybody running one.

Watch for the single-extension outlier. When one extension misses calls at several times the rate of its peers, the cause is almost never effort. It is usually do-not-disturb left on, a forward pointed somewhere stale, or a phone that stopped registering days ago.

What call history will not tell you

It will not tell you why. Two answered forty-second calls look identical whether one booked an appointment and the other ended in an argument.

Signal offers a layer above the CDR: AI call summaries with action items and sentiment, plus red-flag detection that surfaces calls where the caller had a bad experience. Two honest caveats belong with that.

These features send call audio and text to third-party AI providers. Signal has no BAA with those providers, so they are off by default per client, and a practice handling protected health information should leave them off pending a BAA. They also depend on call recording, and recording on Signal requires a consent announcement played to the caller — in two-party-consent states that announcement is legally load-bearing, not a courtesy.

The CDR carries none of that exposure. It is metadata about calls, not their content, which is part of why it is the right place to start.

A five-minute weekly habit

You do not need a reporting practice. You need a short, repeatable look.

1. Open the weekly call report Signal emails and read three lines: total inbound, missed, and the missed-by-extension list.
2. If missed moved by more than a few points against the prior week, open call history and filter that week by disposition.
3. Once a quarter, filter by number dialed across ninety days and decide what to keep.

The value is not sophistication; it is that the numbers exist before the argument about whether last week was busy. The weekly call report covers what to do with each line of it.

Frequently asked questions

What is a call detail record (CDR)? A CDR is one row per call recording the date and time, direction, calling number, number or extension dialed, duration, and disposition — answered, no answer, or busy. Signal writes one for every call and makes them searchable in the portal by date range, direction, extension, and number.

How do I find out when my business gets the most calls? Filter one month of inbound call history and group the results by hour of day and weekday. Look specifically at calls arriving before you open, volume across the lunch hour, and the first ninety minutes after opening — the three windows where coverage most often fails to match demand.

How do I tell which phone number is bringing in calls? Filter inbound call history by the number dialed. Each number you own reports separately, so a tracking number, an old location's number, and the main line each show their own volume. Numbers with zero inbound calls over ninety days are candidates for release; numbers with volume and no answers are misrouted.

How do I calculate my missed call rate? Divide inbound calls with a no-answer disposition by total inbound calls for the same period. Then split the misses into rang-out, abandoned in queue, and sent to voicemail, because each has a different fix. Signal's weekly report includes a missed-by-extension breakdown automatically.

What can't call history tell me? Whether the call went well. The CDR records that a call happened and how it ended, not what was said or whether the caller got what they needed. Call summaries and red-flag detection address that, but they rely on recording with a consent announcement and are off by default.

If you have never looked at your own call log, an hour with it usually produces one or two changes worth making. We are glad to walk through what your history shows and what it implies about your routing.