Weekly noise, monthly truth

Monthly Call Trends: The Report That Smooths the Noise

Daily call reports spike and dip for reasons that mean nothing; monthly trends surface the movements that mean everything — seasonality, campaign lift, staffing drift. Here is what the monthly view contains and the decisions it feeds.

Prefer to talk? Call 1300 858 751
  • Calls per number, per month
  • Answered rates over time
  • Seasonality made visible

Monthly trends questions

What does a monthly trends report show?

The same call detail as any report — calls per number, durations, answered against missed — grouped by month instead of day. Patterns invisible in the daily noise become obvious: seasonal peaks, campaign lift, slow erosion in answered rates.

What decisions is the monthly view for?

Staffing plans for the season ahead, campaign lift measurement (this month against last), cost forecasting (call charges scale with the trends), and spotting structural drift — a number quietly losing calls month over month.

Can we get the trend data into our own tools?

Yes — the CDR area of our API returns the per-call records, so monthly aggregation can be built in your BI stack exactly as your fiscal calendar needs. Records appear within a couple of minutes of each call.

Daily reports tell you what happened today; monthly trends tell you what is happening to you. The difference is noise: daily volumes spike for weather, news and luck, while monthly movements reveal seasonality, campaign lift and slow structural drift — the patterns that justify staffing and budget decisions. This page covers what the monthly view contains and the four decisions it feeds.

What the monthly view contains

The same call detail as every report — calls per number, durations, answered against missed — grouped by month and compared against prior months. Three dimensions matter most in monthly aggregation:

  • Volume per number, per month — the seasonality and lift view: which lines are growing, which are fading.
  • Answered rates, per month — the drift view: answering performance that erodes a point a month is invisible weekly and undeniable quarterly.
  • Durations, per month — the mix view: shorter calls signal changed customer intent before any other metric shows it.

The underlying records are per-call and exact — per-second billing reconciles against them — so the monthly view inherits the accuracy. The reporting framework is in call detail reporting.

The four decisions the monthly view feeds

  1. Seasonal staffing. Last year'"'"'s monthly curve is this year'"'"'s roster plan.
  2. Campaign lift. This month against last, per tracking number — the honest before-and-after.
  3. Cost forecasting. Call charges scale with the trends; monthly volume is the input the budget needs, checked against per-second actuals.
  4. Structural drift. A number losing calls month over month is a campaign or market signal worth investigating early.

The data layer for custom views

Teams building monthly trends in their own BI tools read the raw records through the CDR area of the API — records within roughly one to two minutes of each call completing, JSON over REST with bearer-token authentication. The integration patterns are in call analytics through the API.

The takeaway

Monthly trends turn a call log into a management instrument — and they need months of data to do it, which argues for starting early: numbers from $10 a month, searchable on available numbers, logging from the first call. The product behind the trends is on 1300 numbers.

Reports that compound

Get the numbers the trends need

1300 and 1800 numbers from $10 a month — every call logged, monthly trends from month one.