Weekly Inquiry Analytics Report: Key Metrics, Trend Comparisons, and Action Items
1. The five metrics to track: it’s not just inquiry volume
A counterintuitive call:Inquiry volume up 40% is bad news, not good news, if the qualified inquiry rate dropped 20% at the same time. A rise in total volume usually means junk traffic, competitors, and bots have mixed in, sales time is diluted, and genuinely good leads don’t get timely follow-up. So the first metric in the report isn’t total volume — it’s the qualified inquiry rate.
The five metrics should form one funnel: visitor arrives, submits form, first response goes out, conversation starts, quote sent, deal won. Each layer has a conversion rate, and the weekly report tracks which layer dropped. Looking only at inquiry volume at the top is like only checking how far the tap is open without checking whether the sink leaks.
| Metrics | Definition | Healthy range | What a drop means |
|---|---|---|---|
| Inquiry volume | Total forms + chats + emails this week | Fluctuates with channel spend | Traffic or form problem |
| Qualified inquiry rate | Share after removing competitors/junk | ≥60% | Traffic quality dropped or form is too loose |
| SLA attainment rate | Share with first response within 5 minutes | ≥90% | Understaffed or gaps in scheduling |
| Quote rate | Share of qualified inquiries that get a quote | 70% or above | Stuck at the needs-confirmation stage |
| Win rate | Share of quotes that close | ≥15% to 25% | Problem with pricing or competitiveness |
These numbers aren’t dogma — calibrate them against your own industry’s historical data. B2B equipment win rates are naturally low, so 10% may be normal; consumables may need 30% to pass. Set the first version of the thresholds by gut feel, then recalibrate once a quarter using the past year’s closed-deal data. For how to set the first-response SLA, see First-response SLA and conversion rate for inquiries.
2. Trend comparisons: break it down three ways — week-over-week, year-over-year, and by channel
A single number means nothing. You got 50 inquiries this week — is that good or bad? No idea. It only means something in comparison: up or down versus last week, up or down versus the same month last year, and broken out by channel, which channels are rising and which are falling. Only after all three layers of comparison do you know whether this week’s numbers are seasonal noise or a real problem.
The channel breakdown matters most. Inquiries from Google Ads and inquiries from organic search can differ twofold in quality. Total volume is up 15%, but break it down and it’s all low-quality leads from a blog download, while inquiries from your high-converting product pages are actually falling. In that case, next week’s job isn’t to celebrate — it’s to find out why that blog page is pulling in junk traffic.
| Comparison dimension | What to check | Judgment criteria | Action |
|---|---|---|---|
| Week over week (WoW) | This week vs. last week | Within ±20% is normal | Flag in yellow and investigate if exceeded |
| Year over year (YoY) | This week vs. same week last year | Still falling after removing seasonality? Watch out | Check market and competitor shifts |
| By channel | Ads / organic / social / chat | Check each channel’s qualified rate separately | Cut low-quality channels, add high-quality ones |
| By source country | English-speaking / German-speaking / other | Spot emerging-market signals | Assign follow-up in the right language |
| By sales rep | Each person’s conversion rate | Unusually low: coach. Unusually high: replicate | One-on-one review |
Data attributed to a specific channel and landing page must be tracked at the moment the form is submitted — sales can’t fill it in after the fact. For the technical side of field sync and deduplication, see Connecting Website Leads to Your CRM. For how to choose an attribution model, see How to calculate lead attribution correctly. Without tracking in place, the channel breakdown in your weekly report is a castle in the air.
3. From metrics to action items: turning anomalies into next week’s work
The biggest waste in a weekly report is reading it and moving on. If a weekly report is nothing but numbers and charts with no action items, it’s decoration for your boss. A genuinely useful weekly report always ends with an action item table: which metric is off, what might be causing it, who owns it, when it will be done next week, and where the results get logged.
Example: this week SLA attainment dropped from 92% to 76%, triggering an alert. Don’t just write “responses got slower, needs improvement” and call it done. Write it like this: Anomaly = SLA attainment 76% (red line 90%); Likely cause = no one on duty during the Wednesday–Thursday peak in US and European inquiries; Owner = sales manager Zhang San; Action = start evening shifts covering US and European working hours next Monday; Deadline = next Wednesday; Follow-up = compare SLA after the new schedule in next week’s report.
| Action item element | Requirements | Bad example (fails) | Good example (passes) |
|---|---|---|---|
| Anomaly description | Include numbers and the red line | “Replies are a bit slow” | “SLA attainment 76%, red line 90%” |
| Possible Cause | List 1–2 hypotheses | “Not enough staff” | “No one on duty during US/Europe peak hours” |
| Department head | Name a person, not a department | “Sales department” | “Sales manager Zhang San” |
| Action | What exactly to do | “Strengthen management” | “Add evening shifts covering 20:00–24:00” |
| Deadline | A specific day next week | “As soon as possible” | “Schedule live by next Wednesday” |
| How results get logged | Where do I see the results? | “Let’s discuss it at the next meeting” | “Compare SLA numbers in next week’s report” |
Action items must be filled in at the top of next week’s report. Did last week’s actions get done, did they work, should we keep going? Once this loop is running, the weekly report stops being a reporting tool and becomes a management tool. For how lead grading works together with prioritization, see Lead Scoring and Prioritization for Inquiries.
4. Five common mistakes in weekly reports
| Mistake | Performance | Consequence | Fix |
|---|---|---|---|
| Reporting only the total | We got 50 inquiries this week | No way to tell good from bad | Report all five metrics together |
| No comparison | Looking at this week’s numbers in isolation | Mistaking fluctuation for a trend | Compare week-over-week, year-over-year, and by channel |
| No red lines | Everything looks normal | Problems surface only at month end | Set alert thresholds for SLA and qualified rate |
| No action items | Read it and done | Same as usual next week | Assign anomalies to a person with a deadline |
| Filling in numbers by hand | Sales patch in the data in their weekly reports | Gaps and delays | Let the CRM generate reports automatically |
The last mistake is the biggest drain: sales manually typing data into a spreadsheet every week. Manual data has a very high error rate, and it forces sales to spend half an hour building a table. The right approach is to build the five metrics into an automatic dashboard in the CRM. The weekly report then only covers anomalies and action items, and the system does the math. For the basics of monitoring and alerts, see Site Monitoring and Alerting Checklist.
FAQ
Which metrics should an inquiry weekly report actually cover?
Why can rising inquiry volume be a bad thing?
What trend comparisons should the weekly report make?
What makes an action item in a weekly report good enough?
What should the alert thresholds be for SLA attainment and qualified inquiry rate?
Can the weekly report data be filled in manually by sales?
Final thoughts
The weekly inquiry report isn’t really about “reporting data” — it’s about “knowing what to do next week.” A report that only says “50 inquiries this week” and one that spells out “SLA dropped to 76%, Zhang San owns it, add evening shifts before next Wednesday” look like the same kind of document, but their management value differs tenfold. The difference is that the latter turns numbers into actions.
Three steps to make it happen: first, build the five metrics into an automated dashboard in the CRM and stop filling in forms by hand; second, lock in two alert lines — SLA below 90% and qualified rate below 60% trigger an investigation; finally, every weekly report must end with an action item table, and the first thing next week is to log back the results of last week’s actions. Run it for three months and you’ll find the reports getting shorter, because problems get handled the same week instead of waiting for month-end.
One line worth remembering: the weekly inquiry report isn’t a numbers report for the boss, it’s the task list for next week’s work — a report with no action items is just a decorative sheet of paper, no matter how nicely written.