Build a lead-routing SLA dashboard the revenue team actually reviews
A compact dashboard that shows whether inbound leads reach a named owner inside the promised window.

Decide which decisions the dashboard supports
A dashboard earns a weekly meeting only when it answers a decision the team can act on. For lead routing, that decision is who must fix a missed handoff this week. Start by listing the three choices the revenue team makes from the data, such as adding coverage, changing a routing rule, or coaching a seller. If a panel does not change one of those choices, it does not belong on the first screen.
Write the decision and the owner above each panel before you build it. The owner should be a role, not a person, so the dashboard survives staff changes. A panel that says a number is low without naming who acts will be ignored within a month. Review the list of decisions with the sales leader and remove anything that is only interesting.
Define the SLA in buyer terms
An SLA should describe what the buyer experiences, not what the team intends. Write it as a window from submission to a real attempt to contact the buyer, such as a call or a personal email. An automated acknowledgment does not count as contact because it does not answer the buyer's question. Put the exact wording on the dashboard so nobody redefines it in a meeting.
Set the window by segment so the promise matches coverage. A small team may promise a faster response during business hours and a next-morning response after hours. That is honest and easier to keep than a single aggressive target. Buyers remember the promise that was shown to them, not the one in an internal slide.
Choose the few fields the dashboard needs
Most CRM exports contain far more fields than a routing dashboard needs. The minimum set is the submission time, the assignment time, the first contact time, the source, the segment, and the owner. Each field should come from a system that captures it automatically. A field maintained by memory will turn the dashboard into a guess.
Check a sample of records to confirm the timestamps mean what the labels say. An assignment field may update when a manager opens the record rather than when the seller receives it. If the field is wrong, fix the field before adding charts. A precise dashboard built on a loose field damages trust faster than no dashboard at all.
Show the distribution, not just the average
An average hides the small number of buyers who waited far too long. Show the median, the share inside the window, and the slowest tenth of requests. The slowest group is where the promise breaks and where the next fix lives. A median that looks healthy can sit beside a slow tail that loses deals.
Use the same time buckets every week so the team can compare periods honestly. Label the buckets in plain language, such as under one hour and over one day. Avoid a chart that requires a legend to understand. The person reviewing the dashboard should see the shape of the problem in a few seconds.
Split queue time from seller time
Routing delay and seller delay need different owners, so report them separately. Queue time runs from submission to a named owner, while seller time runs from ownership to first contact. A single total number lets each group blame the other. Two measures plus a combined view keep the conversation on the fix.
Review the split with both sales and marketing present. Marketing often sees incomplete forms while sales sees slow follow-up, and both observations can be true. The split shows which problem is larger this week. It also prevents a fast seller from being blamed for a slow routing rule.
Add an exception list with named owners
The dashboard should end with a short list of requests that missed the window and still need action. Each row needs a buyer, an owner, an age, and the next step. Keep the list to the current week so it stays readable. An exception list that grows without limit becomes another backlog nobody trusts.
Assign a single coordinator to keep the list current and to close rows when the buyer has been contacted. The coordinator does not need to fix every case, but they must know who does. A daily glance at the list is usually enough. The goal is to catch a missed buyer while the conversation can still be saved.
Set a weekly review rhythm
Put the review on the calendar at the same time each week and keep it to thirty minutes. Start with the exception list, then look at the trend, then choose one change. A meeting that only reads numbers will lose attendance. A meeting that ends with an owner and a date will earn it.
Record the change and the expected effect in a short log beside the dashboard. Next week, check whether the change moved the measure before adding another. One tested change at a time is easier to understand than a redesign every month. The log also shows new team members why the current rules exist.
Retire panels nobody uses
Every quarter, ask which panels changed a decision in the last three months. Remove the ones that did not, even if they took effort to build. A crowded dashboard hides the two numbers that matter. The team should be able to explain each remaining panel in one sentence.
Keep a small archive of removed panels in case a question returns. Note why each was removed so the team does not rebuild it by accident. A dashboard is a tool for decisions, not a museum of data. The best version is usually the smallest one the team still opens.
Sources
- Occupational Outlook Handbook: Sales managers, U.S. Bureau of Labor Statistics. Describes sales manager responsibilities and the operating context for revenue teams.
- Market research and competitive analysis, U.S. Small Business Administration. Outlines a practical process for understanding customer demand before sales investment.
- Business Trends and Outlook Survey, U.S. Census Bureau. Provides business conditions context for demand and coverage planning.