August 18, 2026
The Weekly Call Report: Five Minutes That Show Who's Missing Calls
Signal emails a weekly call report to your account's users every Monday, covering the previous week: total call volume, a daily breakdown, missed calls by extension, and any calls flagged as bad experiences. It takes about five minutes to read. The reason it arrives by email is that reports you have to go and fetch do not get read.
Why the delivery method is the feature
Every phone system built in the last fifteen years has reporting. Almost none of it gets looked at.
The reason is mundane. A dashboard requires you to remember it exists, decide today is the day, find your password, and pick a date range — four small frictions in front of a task nobody assigned you. A report in your inbox on Monday requires you to not delete it.
We built the weekly report as an email first because that is the only version that survives contact with a busy office. The same data lives in the portal, and the report is also stored there permanently. But the email is what makes it a habit, and a habit is the entire value. A phone report read once a week for a year beats an excellent dashboard opened twice.
What is in a weekly call report?
Four sections, all covering one Monday-to-Sunday week.
- Call volume. Total inbound and outbound calls for the week, so you have a baseline to compare against.
- Daily breakdown. The same counts split by day, which is where seasonality and Monday spikes become visible.
- Missed calls by extension. Which extensions had calls ring and go unanswered, and how many.
- That week's red flags. Calls where a caller had a bad experience, if you have call recording and AI features enabled. Most accounts do not — those features are off by default and require a consent announcement. Finding the call that went wrong covers what that section is for.
The report is a snapshot. Signal generates it once, on Monday, from that week's call detail records, and stores the result. Opening the report in March does not re-run the query.
What to look at first: missed calls by extension
Start here, because it is the only section that names a specific fixable thing.
A missed-call count next to an extension is not an accusation. It is a routing diagnosis, and the pattern tells you which one.
One extension with most of the misses usually means your main number points at a single phone. That person takes lunch, walks to the back office, and is already on a call for a good part of the day, and while they are unavailable nobody else's handset makes a sound. The fix is a ring group so several phones ring together. Call groups covers the member list and — more importantly — the no-answer destination.
Misses spread evenly across several extensions means everyone is busy at once. That is a capacity problem, not an availability one, and a ring group will not touch it. A call queue holds the caller, plays hold treatment, and hands them to whoever frees up first. Call queue setup covers the two settings that decide whether a queue helps: a wait ceiling and a failover destination.
Misses on an extension that should never receive direct calls means a phone number or an auto attendant key is pointed somewhere stale. Worth ten minutes with routes to find out where.
The daily shape of your volume
The daily breakdown answers a different question: when do you need people on phones?
Most small offices carry a distribution they have never actually looked at. Early-week days often run well ahead of late-week ones. Volume tends to peak in the first stretch after opening and again right after lunch. The last hour before close is frequently quiet enough that a single person covers it comfortably. Your own report will tell you which of those hold for you and by how much — that is the point of reading it rather than assuming.
Once you can see that shape, staffing stops being a guess. The office that puts three people on the front desk all day and still misses the 8:15 rush is a common and expensive arrangement, and it is invisible until somebody plots the week.
Watch the shape across several weeks rather than reacting to one. A single bad Tuesday is noise. A pattern of bad Tuesdays is a schedule.
Report section | The question it answers | Where the fix usually lives |
|---|---|---|
Call volume | Is this week normal? | Nowhere — it is your baseline |
Daily breakdown | When do calls actually arrive? | Staffing and business-hours routing |
Missed by extension | Who is not getting to the phone? | Ring groups, queues, routing |
Red flags | Which calls went badly? | Callbacks and menu design |
What the report will not tell you
It will not tell you why a caller hung up. Call detail records show that a call ended, not what the person wanted. If you need the content of calls, that requires call recording — which requires a consent announcement, and is off until you enable it.
It will not tell you about calls to a mobile number your staff hand out personally. Anything that does not traverse your phone system does not appear in your phone system's reporting, which is one of the quieter arguments for not giving out personal cell numbers.
It will not change retroactively. This one is a deliberate product decision. A weekly report is a record of what a week looked like when it ended, and a report that quietly re-computes when you reopen it is worthless for comparison. If you want a live view, use call history and CDR search — that is what they are for. Call reporting basics covers the searches worth saving.
And it will not tell you what a missed call cost. That number depends on your business, not on your phone system — an office where a new customer is worth four figures should read a miss count of twelve very differently from one where it is worth twenty dollars.
Who gets it, and what to do with it
The report goes to the users on your account, which is worth deciding deliberately. The owner should see it, and so should whoever manages the front desk — they are the person who can act on a missed-call pattern by Tuesday.
A reasonable habit: read the missed-by-extension section, check whether the number moved, and change exactly one thing. Add a member to the ring group. Extend a queue timeout. Move lunch coverage. Then read next Monday's report to find out whether it worked.
That loop — one change per week, measured against a report you did not have to run — is worth more than any single feature in a phone system.
Frequently asked questions
What is in a weekly call report? Total inbound and outbound call volume for the week, a daily breakdown of those counts, missed calls broken down by extension, and that week's red-flagged calls if you have call recording and AI features enabled. Signal generates it every Monday for the previous Monday-to-Sunday week and emails it to your account's users.
How do I find out who is missing calls? Read the missed-by-extension section of the weekly report. One extension carrying most of the misses points at a main number ringing a single phone, which a ring group fixes. Misses spread across several extensions point at capacity, which a call queue fixes. The pattern matters more than the total.
Why does my call report never change after the fact? Because Signal generates each weekly report once and stores the result rather than re-querying when you open it. A report that shifts retroactively cannot be compared to last week's, which defeats the purpose. For a live view of calls, use call history and CDR search in the portal instead.
Do I need to log in to see my call reports? No. The report arrives by email every Monday, which is the whole point of building it that way. Every report is also stored in the portal if you want to compare several weeks, and live call history is always available there for questions the weekly snapshot does not answer.
If you are currently guessing at how many calls your office misses, a few weeks of reports will settle it. We are glad to walk through your first one and point at which of the numbers is worth acting on.