CRM Reports Examples: 8 Reports Every Telecalling Manager Should Read Weekly

These CRM reports examples give a telecalling manager eight reports to read every week: leads by source, cost per qualified lead, stage funnel, conversion lag, telecaller performance, callback adherence, appointments or site visits, and lost reasons. Each report answers one question, has a number that warns you, and leads to one action you can take before next Monday.

The four numbers to look at every morning catch problems you can fix the same day. These weekly reports look for patterns instead: which source, which step, which person.

How to use these CRM reports examples: question, number, action

A report nobody acts on is decoration. For each of the eight, write down:

1. The question it answers, in one sentence a telecaller would understand.
2. The number that worries you, from your own last four weeks, not a slide.
3. The action you will take when that number shows up, and who does it.

Each report below is a spec you can copy. Three rules apply to all eight.

• Compare against your own four-week average. One bad week can be a festival or a paused campaign.
• Be clear about the date you filter on. Funnel and lag reports need older groups of leads, because last week's enquiries have not had time to buy.
• Every number must open into a list of leads. If you cannot click from "14 lost to Budget" to the 14 names, the meeting becomes an argument about the number.

Reports 1 and 2: leads by source, and cost per qualified lead

Report 1: Leads by source

• Rows and columns: one row per source (each Meta form, Google lead form, website form, WhatsApp Bot, IVR, walk-in, referral); columns for new, contacted, qualified, converted and qualified share.
• Filter: leads created last week.
• Question: which sources send people who pick up and fit what we sell?
• Warning sign: volume rising while qualified share falls by half, or a growing row with a blank source.
• Action: read the comments on 20 of that source's disqualified leads before touching the budget, and fix any form or import that leaves the source blank.

Report 2: Cost per qualified lead

Cost per lead, which the ad account shows, and cost per qualified lead can disagree. Here is a hypothetical week for a skin clinic in Pune.

Per lead, Meta looks two and a half times cheaper. Per qualified lead, it costs ₹500 more. That is not a reason to switch Meta off; a qualifying question on the form or a different ad may fix it.

To know what is too high, work back from a sale. Say the average package is ₹45,000, one in five qualified leads buys, and the owner will spend ₹9,000 on marketing per sale. The ceiling is ₹9,000 ÷ 5 = ₹1,800 per qualified lead. Google is under it and Meta is over.

• Rows and filter: each paid source, then each ad; leads created last week and spend for the same dates.
• Question: what does one useful conversation cost from each paid source?
• Warning sign: above your ceiling for two weeks running.
• Action: move budget between ads on this number, never on cost per lead alone.

For Meta leads, atomcrm.ai's Ads Intelligence syncs ad spend and grades each ad by effective cost per qualified lead against a target you set. See how the Meta lead ads sync and ad grading work.

Reports 3 and 4: stage funnel and conversion lag

Report 3: Stage funnel

• Rows and columns: your stages in order (New, Contacted, Interested, Appointment booked, Visited, Converted); columns for leads reaching each stage and the share passing from the stage before, beside its four-week average.
• Filter: leads created in one week, three to four weeks ago, so they have had time to move.
• Question: at which step are we losing people?
• Warning sign: one step passing far fewer leads than usual while the others hold.
• Action: match the fix to the step.

Report 4: Conversion lag

Conversion lag is the number of days from first enquiry to sale. It tells you how long to keep following up before calling a lead lost.

• Rows and columns: weekly groups of leads by date created, for the last 12 weeks; columns for converted within 7 days, 8 to 30, 31 to 60, after 60, and still open.
• Filter: leads created in the last 12 weeks.
• Question: how long do our buyers take, and are we giving up before they decide?
• Warning sign: a steady flow of sales after day 30 while the team marks most leads lost within 10 days.
• Action: stretch the follow-up schedule to match the lag. Read this one monthly.

Say a Hyderabad property developer finds most bookings come 45 to 90 days after the enquiry. A telecaller who closes leads after three unanswered calls in week one throws away next quarter's bookings.

Reports 5 and 6: telecaller performance and callback adherence

Report 5: Telecaller performance

• Rows and columns: one row per telecaller; columns for leads assigned, calls, connect rate, talk time, appointments booked, converted, and converted as a share of assigned.
• Filter: last week, split by source if callers work different sources.
• Question: who needs help this week, and with what?
• Warning sign: a caller's connect rate or conversions well below the team's on the same source for two weeks running.
• Action: one coaching conversation per flagged person, about one pattern.

Report 6: Callback adherence

A callback is a promise: "I'll call you on Thursday at 6." This report counts how many were kept.

• Rows and columns: one row per telecaller; columns for callbacks due, done on the day, done later, still overdue, and adherence (done on the day ÷ due).
• Filter: callbacks that fell due last week.
• Question: are we calling back when we said we would?
• Warning sign: overdue growing week on week, or one caller setting many callbacks 30 or more days out, which parks leads so they never look overdue.
• Action: go through the overdue list with the caller, lead by lead. Then make every "still talking" stage require a next callback date. The callback management system guide covers that stage design.

Reports 7 and 8: appointments or site visits, and why leads were lost

Report 7: Appointments or site visits

• Rows and columns: one row per telecaller who booked, plus branch or project; columns for booked, confirmed, attended, no-show, cancelled and show-up rate (attended ÷ booked).
• Filter: by appointment date, not booking date.
• Question: are bookings turning into people at the clinic, showroom or site?
• Warning sign: a falling show-up rate, or one caller booking far more than others while few of their visitors arrive, which usually means booking to hit a target.
• Action: a confirmation call the day before plus a WhatsApp reminder, and treat unconfirmed bookings as soft.

For a property developer, this is the site-visit report.

Report 8: Why leads were lost

• Rows and columns: one row per reason from a fixed list (Not interested, Budget, Bought elsewhere, Location too far, Wrong number or junk, Never answered); columns for count, share of lost leads, and the split by source.
• Filter: leads closed as lost last week.
• Question: are we losing on the ad, the price, the speed or the call?
• Warning sign: "Not interested" swallowing most of the list, or junk bunched in one source.
• Action: junk goes back to whoever runs that campaign. "Bought elsewhere" usually points to slow first response. "Budget" or "Location too far" from one campaign points to targeting, not the telecaller.

Make callers pick the reason from a list. Free text can be read but not counted.

A one-page sales CRM dashboard layout (template)

A dashboard is for spotting which report to open. A CRM software dashboard that leads with total lead count says nothing about quality or follow-up. This layout fits one screen and works as a lead management dashboard for 5 to 30 callers.

For a real estate CRM dashboard, call the appointment block site visits and add a project column. For a clinic group, put branch as a filter at the top.

A 20-minute Monday reading order

1. Tiles: is anything more than a quarter off its four-week average?
2. Cost: is any paid source above your ceiling?
3. Funnel: which step leaked more than usual?
4. Telecallers: pick at most two people and one pattern each.
5. Callbacks: agree the overdue list is cleared by Tuesday evening.
6. Lost reasons: send one note about junk or budget to whoever runs the ads.
7. Write three actions with a name against each, and check them first next Monday.

Building these reports in atomcrm.ai

• Standard reports (leads by source, stage and owner, telecaller performance, callbacks, appointments, conversion funnel) are the starting point for reports 1, 3, 5, 6 and 7. The conversion lag and cohorts view answers the question behind report 4: how many days leads take to convert, grouped by when they arrived.
• The report builder takes up to 8 measures and 4 groupings, as a table or chart, and drills down from any number to the leads behind it. Use it for lost reasons by source.
• Ads Intelligence covers report 2 for Meta, grading each ad as winner, scalable, watch, learning or loser. The sales funnel view adds revenue and CAC.
• The team performance leaderboard shows calls, connect rate, talk time, follow-up adherence and conversions. The Call Pro Android app logs each call's outcome and duration on the lead.
• Lost reasons work best as sub-stages under the Disqualified group, because stages drive reports. The separate Status label, for why an open lead is stuck, does not change reports.
• Custom drag-and-drop dashboards are where you arrange your own version of the one-page layout (read cost per qualified lead in Ads Intelligence). A report you save in the report builder can be emailed daily, weekly or monthly to up to 20 addresses.

The reports and dashboards guide covers the standard reports, the builder and scheduled emails, and understanding your analytics explains how the numbers are calculated.

Frequently asked questions

What is the difference between a CRM report and a CRM dashboard?

A report answers one question in detail, with rows, columns, a date filter and the leads behind every number. A dashboard puts the headline figure from several reports on one screen so you know which report to open. Define the reports first, or "qualified" will mean different things to different callers.

How often should a sales manager review CRM reports?

Daily for the few numbers that need action the same day, such as unassigned leads and overdue callbacks. Weekly for the eight reports here, because a week gives enough leads to show a pattern without waiting too long to act. Monthly for slow-moving views like conversion lag and cost per sale.

How do you measure telecaller performance in a CRM?

Look at the chain, not one number: leads assigned, calls, connect rate, talk time, callbacks done on the day, appointments and conversions. Each link points to a different fix. Compare callers only on the same lead source and week, since fresh ad leads and old lists behave differently. Use the numbers to decide what to coach, not to rank people publicly.

What should a real estate CRM dashboard show?

Enquiries and qualified leads by project and source, cost per qualified lead for paid campaigns, site visits booked against visits done, callback adherence per telecaller, and lost reasons such as budget or location. Give site visits the most space, since they sit closest to a booking, and keep conversion lag nearby for slow buyers.

Can I build these reports in Excel instead?

Reports 1 and 2, yes, if every lead has a clean source column and someone pastes in ad spend weekly. The rest are hard. Callback adherence, funnel steps and conversion lag need the date of every stage change and callback, and a shared sheet rarely keeps that history once people overwrite cells. That is usually when a team moves its leads into a CRM.

Schedule the weekly email and read it on Monday

Pick the three reports that match your biggest problem, save them in the report builder, schedule them as a weekly email to you and your team leads, and add the rest over the next month. For the wider picture, see CRM software for sales teams. To see these reports on your own sources and stages, book a 20-minute demo, or start the 14-day trial for ₹5 and set up the email yourself.