Inquiry Dashboard: Track First Response Time, Follow-Ups, and Conversion Rate
1. Why the Dashboard Keeps Only Three Core Metrics
Many teams build inquiry dashboards with 20 metrics: page views, unique visitors, bounce rate, time on page, form completion rate, first response, second response, follow-up touches, quotes sent, win rate, average deal size… They open it once a day, look it over, and still don’t know what to do. A dashboard isn’t meant to display data, it’s meant to drive action.
Counterintuitive take: the more metrics you have, the less your team does. Every metric is shouting “look at me,” so nobody knows which inquiry to rescue first today. A dashboard that actually works has no more than 3 core metrics, and each one maps to a specific action.
| Core Metrics | Cost Item | Healthy Threshold | Action |
|---|---|---|---|
| Median first-response time | Median first response time across all new inquiries that day | ≤15 minutes | Auto-assign overdue inquiries from the no-reply list |
| Follow-Up Distribution | Cumulative touches per active inquiry | 3 to 5 for hot inquiries | Remind on inquiries stalled over 3 days |
| Stage Conversion Rate | Four stages: new inquiry → qualified conversation → quote → won | ≥30% at each stage | Optimize the stage with the biggest drop-off |
These three metrics map to the three stages of the inquiry lifecycle: just arrived (first response), in progress (follow-up), and closing (conversion). Other metrics like page views and unique visitors belong to traffic, so put them on the marketing dashboard, not the sales dashboard. Keeping traffic and sales dashboards separate is Inquiry Source Channel Analysis the prerequisite for making this work.
2. First Response Time: the Median Is More Honest Than the Average
The most common mistake with first response time is looking at the average. One inquiry gets a reply in 2 minutes, another in 2 hours, and the average is 61 minutes, which looks fine, but that 2-hour inquiry has most likely already churned. Averages get buried by outliers; the median reflects how your team actually responds.
| Measurement | Example | What It Reveals | How to Use It |
|---|---|---|---|
| Average | 2 minutes and 120 minutes average out to 61 minutes | Hides long-tail delays | Watch the trend, not the absolute number |
| Median | Half of inquiries answered in ≤15 minutes | Reflects actual response level | Use as the daily report’s main metric |
| P90 | 90% of inquiries answered in ≤45 minutes | Shows the worst cases | Use for scheduling and escalation |
| SLA attainment rate | Share replied to within 15 minutes | Shows process discipline | Tied to sales performance |
In your daily report, first response time should always be read as two numbers: the median and the SLA attainment rate. The median tells you how fast the team is overall; the SLA attainment rate tells you whether the process is actually being followed. You need both. Looking at only one will mislead you. For how to set SLA tiers, see First-response SLA and conversion rate for inquiries.
3. Follow-up count: 3 to 5 touches is the sweet spot for hot inquiries
More follow-ups is not better. B2B inquiry data shows that a hot inquiry contacted 3 to 5 times within 14 days has the highest chance of closing; fewer than 2 and the buyer thinks you are not eager enough; more than 8 and the buyer gets annoyed or even blocks you. The follow-up count dashboard should answer “which inquiries should have been followed up but weren’t,” not “who followed up the most.”
| Follow-up count range | Inquiry status | Buyer mindset | Dashboard action |
|---|---|---|---|
| 0 to 1 | Just came in or forgotten | They still don’t know who you are | Must reach out once today |
| 2 to 3 | Normal follow-up in progress | Comparing suppliers | Watch, don’t intervene |
| 3 to 5 | Sweet spot | Interested but hesitant | Send one differentiated message |
| 6 to 8 | Near saturation | Starting to get impatient | Downgrade to monthly nurturing |
| >8 with no reply | Effectively lost | Chose someone else or not interested | Archive, stop proactive follow-up |
The stalled list is the most useful part of the follow-up dashboard: if an inquiry has had no new activity for more than 3 days, it automatically goes on the “stalled list,” and you review it at every morning meeting. Stalled does not mean lost. Often the salesperson just forgot, but on the buyer’s side it reads as “this company isn’t eager.” For how to design your follow-up cadence, see Inquiry follow-up count and conversion rate.
4. Stage conversion rates: a four-stage funnel to find where you’re losing deals
You can’t judge conversion by one overall number. A figure like “8% from inquiry to closed deal” gives you nothing to act on. Break the funnel into four stages and see which one leaks the most. That’s what you optimize next month. The four stages are usually: new inquiry → qualified conversation → quote → win.
| Funnel stage | Definition | Healthy range | If it’s below the range |
|---|---|---|---|
| New inquiry → qualified conversation | The buyer replied to your first response | 50% to 70% | Improve your first-response script and speed |
| Qualified conversation → quote | Moved into a real needs discussion and sent a quote | 40% to 60% | Strengthen your needs-discovery skills |
| Quote → win | Contract signed or deposit paid after the quote | 20% to 35% | Review your quoting strategy and competitor comparison |
| New inquiry → win, overall | All stages multiplied together | 3% to 8% | Find the weakest stage and focus on breaking through |
Take an example: you get 100 new inquiries, 60 qualified conversations, 30 quotes, 6 wins. The overall 6% looks fine, but qualified conversation → quote is only 50%, below the healthy range. The problem isn’t traffic, and it isn’t first response. It’s that your salespeople don’t know how to dig into needs once they get a conversation. The dashboard tells you: next month you practice needs-discovery scripts, not add ad budget. For a systematic way to diagnose funnel bottlenecks, see Inquiry conversion funnel bottleneck analysis.
5. Daily report template: four quadrants plus red-flagged exceptions
A daily report doesn’t need to be long. One screen is ideal. Keep the structure fixed: four quadrants plus one row of red-flagged exceptions. The system generates it automatically at 9:00 every morning, and the sales team reviews it in 10 minutes at the daily standup. The value of a daily report isn’t in reading it. It’s that after reading it, everyone knows what they need to do that day.
| Daily report module | Field | Rows shown | Exception rules |
|---|---|---|---|
| New inquiries yesterday | Count, source, median first response time, SLA compliance rate | Totals are enough | Flag in red if up or down 30% vs. yesterday |
| Overdue, no reply | Inquiry ID, buyer, source, time waited | Up to 10 | Auto-flag in red if >30 minutes |
| No activity for over 3 days | Inquiry ID, last follow-up, owner | Up to 10 | Flag in red if no action for >3 days |
| Expected to close today | Inquiry ID, amount, stage, next step | Up to 5 | Highlight if amount > threshold |
Example: At 9:00 on a Monday, the sales manager opens the daily report. Three inquiries from Germany have been waiting 2 hours with no reply, two quotes from last week have had no follow-up, and one deal is expected to close with a contract signed this Friday. He doesn’t need to dig through the CRM. In 10 minutes he knows to reply to the three German inquiries first this morning, chase the two stalled quotes this afternoon, and prepare the paperwork for Friday’s signing. That’s what a daily report should do.
Daily report data must sync automatically. It can’t depend on sales reps filling it in by hand. Manually entered data has a very high loss rate, and people tend to make it look better than it is. For how to sync automatically from forms to your CRM, see Connecting Website Leads to the CRM. For how reliable the forms themselves are, see Inquiry Form Reliability.
FAQ
How many metrics should an inquiry dashboard show?
For first response time, should I look at the average or the median?
How many follow-ups is the right amount?
How do you break down stage conversion rates?
How do you keep the daily report from becoming a formality?
What gets flagged red automatically?
Final thoughts
With an inquiry dashboard, the easiest mistake isn’t having too little data, it’s having too much. Many teams pile on everything they can collect, PV, UV, bounce rate, time on page, and it looks professional, but when sales open it in the morning they have no idea what to do that day. A dashboard’s value isn’t in displaying, it’s in driving action.
Three steps to make it work: first, cut everything except the core metrics, keeping only median first response time, number of follow-ups, and stage conversion; second, fix the daily report to four quadrants plus red-flagged exceptions, generated automatically at 9:00 every day; third, every red flag must map to a specific salesperson and a specific action, not just tagged “team.” Once these three steps are done, the dashboard turns from decoration into a tool.
One line worth remembering: a good inquiry dashboard doesn’t tell you “how well we’re doing,” it points at the screen every morning at 9 and says, these three, save them today.
