Lesson 2 of 6 · 8 min

Dashboards and Analytics reports

Read the Dashboard and the Analytics reports the owner cares about.

Read the lesson

Goal: Pull checked numbers from Dashboard, Analytics and Contacts → Reports. Fix bad data before the owner sees it.

You need: Any paid plan. Lesson 1 of this course. A client with at least one full month of data.

Why this matters

A report is only as good as the data under it. Jobs nobody marked as done can make a strong month look weak. One duplicate import can make the customer count look bigger than it is. If the owner finds one wrong number, they doubt all the others. So this lesson has two jobs. First, know where every number lives. Second, check the data before you trust it.

ServiceAgent has no custom report builder today. The Analytics → Reports page says so. There are no scheduled reports and no tiles you can add to Dashboard. That is fine. You build the owner report yourself from 4 places. It takes about 30 minutes a month per client.

The work pays back. A checked report lets you answer any owner question on the call without guessing. It also gives you a clean record. When a client asks in month 9 how month 2 went, you have the same numbers, pulled the same way. Keep each month's export and data check log in one folder per client.

The 4 places your numbers live

PlaceWhat it showsDate control
DashboardTiles: Active Deals, Total Customers, Revenue (30d), Upcoming Appointments. Lists of recent deals and upcoming appointments.None. Always the current view.
AnalyticsTabs: Overview, Calls, Appointments, Tickets, Surveys, Marketing, Widget, Billing, Locations, Tools, Reports.Last 7 Days, Last 30 Days, Last 90 Days
Contacts → ReportsWin Rate and Lead SourcesDate range, This Quarter, Export
Billing → Usage historyCredits used by activityBy period

Use Dashboard as a daily glance. It is not a monthly report, because it has no date filter. Use Analytics for the KPIs. Use Contacts → Reports for sales numbers and exports. Use Usage history for the cost line.

Fig 1

Where the KPIs live in Analytics

Analytics

OverviewConversion Rate
CallsSuccess Rate, and calls split AI vs human
AppointmentsNo Shows, Show Rate, Cancellations, Completion Rate
MarketingReview requests, ad spend, Remaining prepaid
ReportsNo custom report builder yet
Last 30 Days
Every tab uses the same date filter. Analytics screens use 0 credits.

Date windows

Analytics offers rolling windows: the last 7, 30 or 90 days. Owners think in calendar months. So pull the numbers on the same day each month, such as the 1st. On the 1st, Last 30 Days is close to the month just ended. A 31-day month misses one day. Where a screen offers a date range, as Contacts → Reports does, set the exact month. Write the window on the report, for example "Oct 2 to Oct 31." Honest labels prevent arguments. Keep the same window rule for every client, so your own month-end routine stays simple.

Fig 2

Pulling October on November 1

  1. October 1Falls outside Last 30 Days when you pull on November 1
  2. October 2 to 31The window Last 30 Days covers
  3. November 1Pull day: label the report Oct 2 to Oct 31
  4. Any date range screenContacts, Reports: set the exact month
Pull on the same day each month and write the window on the report. Honest labels prevent arguments.

Reading each screen well

Success Rate in Analytics → Calls compares answered calls with total calls. It counts calls to the numbers in the account. Calls to an old number that is not forwarded do not show. So check that every published number forwards to the AI before you trust this KPI.

Conversion Rate in Analytics → Overview and Win Rate in Contacts → Reports are not the same. Use Win Rate for estimate close rate. It reads the deals in the pipeline. It only means something if the team moves each deal to Won or Lost. Deals left in Proposal for months make the number unreliable. Ask the office to close out old deals each month.

Lead Sources shows where contacts came from. It is only as good as the source field. Ad leads do not tag themselves. The team tags them by hand or asks, "How did you hear about us?" If half the contacts have no source, say so on your Operator notes. Fix the intake question.

Usage history in Billing shows credits by activity. Voice is 15 credits a minute. An SMS segment is 2. An email is 0.5. A sudden jump in voice credits often means more calls. It can also mean long calls with a confused caller. Read a few transcripts.

Health Score on each contact sits under Customer Health. It runs from 0 to 100. 80 to 100 is Healthy, 60 to 79 Good, 40 to 59 At Risk and 0 to 39 Critical. It is a health score, not a churn prediction. Use it in your Operator view to pick customers to call.

Fig 3

Health Score bands

Critical0 to 39
At Risk40 to 59
Good60 to 79
Healthy80 to 100
A health score for your Operator view, not a churn prediction. Use it to pick customers to call.

By business size

An owner-operator has thin data. Pull the 6 KPIs and read every job by eye. It takes 10 minutes. A fleet of 8 to 20 techs has enough data for rates to mean something. Run all 5 checks. A multi-location client needs each location pulled on its own, then a total. Expect about 30 minutes per location in the first month and 15 after that.

Build it in ServiceAgent

  1. Open the Organisations page. Pick the client. Check Working in shows the right location.
  2. Open Dashboard. Glance at Upcoming Appointments. If it is empty during a busy season, check that the team books its jobs in ServiceAgent.
  3. Open Analytics → Overview. Set Last 30 Days. Note Conversion Rate.
  4. Open Analytics → Calls. Note Success Rate and the AI vs human split.
  5. Open Analytics → Appointments. Note No Shows, Show Rate, Cancellations and Completion Rate.
  6. Open Analytics → Marketing. Note review requests sent. For ad clients, note ad spend and Remaining prepaid.
  7. Open Contacts → Reports. Set the exact month. Note Win Rate and the top 3 Lead Sources. Use Export to keep a copy.
  8. Open Billing → Usage history. Note credits used and any top-ups.
  9. Run the data checks below. Fix problems before you write the report.
  10. For multi-location clients, switch Working in to each location and repeat steps 3 to 5. Or use Analytics → Locations where it shows what you need.

The 5 data checks

Run these every month, before you write a single sentence.

  1. Job status. Check that finished jobs are marked Completed. Analytics → Appointments counts what the team marks. Jobs left as Scheduled make a strong month look weak.
  2. Jobs vs analytics. Count jobs in Jobs → List for the month. Compare with Analytics → Appointments. A big gap means a filter or location is wrong.
  3. Duplicates. Look at new contacts. Two records for one phone number inflate Total Customers. Fix duplicates at the next import with Smart Merge.
  4. Calendar sync. Each team member connects Google Calendar on their own. The sync sends jobs out to Google and blocks busy times. A stopped sync does not change the counts here, but a tech may miss new jobs. Reconnect it the same day.
  5. Workflow failures. Open each key workflow → History → View run history. Failed runs mean texts did not go out.

If a check fails, fix the cause first. Then recheck the number against the calendar. Only then send the report.

Fig 4

Can you trust this month's numbers?

  1. Pull the month's numbers
  2. Are all finished jobs marked Completed?YesGo to the next checkNoMark them, then recount in Jobs, List
  3. Does the Jobs count match Analytics, Appointments?YesGo to the next checkNoFix the filter or the location
  4. Any duplicates, stopped calendar syncs or failed runs?YesFix the cause firstNoWrite the report
  5. Recheck the number, then send
Fix the cause, then recheck against the calendar. Only then write a sentence.

Worked example: Green Acre Lawn and Landscape

Green Acre runs 5 crews on Growth. On November 1 you pull its numbers. Analytics → Appointments shows 214 completed jobs for the last 30 days. That looks low for the end of leaf season. You run check 1. Crew 4 got a new lead on October 20, and nobody showed them how to mark jobs Completed. That crew's jobs from October 20 to 31 still show as Scheduled, so they are missing from the count.

You show the crew lead how to mark a job Completed, and the office updates the old ones. Then you recount in Jobs → List. Crew 4 had 4 jobs a day for 9 working days. That is 4 × 9 = 36 jobs. The corrected total is 214 + 36 = 250 jobs.

Fig 5Example numbers

Green Acre's missing jobs

Completed jobs shown in Analytics214
+Crew 4: 4 jobs a day × 9 days36
Corrected total250
Jobs left as Scheduled hid 36 ÷ 250 = 14.4% of the month's jobs.

Without the check, the report would show 36 fewer jobs. That is about 14% fewer: 36 ÷ 250 = 0.144. The owner would have asked why business fell. You would have spent the call defending a wrong number.

Fig 6Example numbers

The owner call, without and with the check

No data check
  • Report shows 214 jobs
  • Owner asks why business fell
  • The call defends a wrong number
Check 1 run
  • Statuses fixed, recount shows 250 jobs
  • The number matches the calendar
  • The call plans next month
A checked number turns the call from defense to next steps.

Common mistakes

  • Mistake: Using Dashboard tiles as monthly numbers. Fix: Dashboard has no date filter. Use Analytics and Contacts → Reports.
  • Mistake: Pulling numbers on random days. Fix: Pull on the same day each month and label the window.
  • Mistake: Trusting a low number without checks. Fix: Run the 5 data checks first.
  • Mistake: Reporting one location as the whole business. Fix: Check Working in and report each location.
  • Mistake: Promising a custom dashboard to the owner. Fix: Say the report is a one-page summary you build each month.

Do this now

Pick one client or your practice account. Run the 5 data checks for the last 30 days. Write one line per check: pass, or what you found and fixed. Deliverable: a 5-line data check log you keep with the report. Time: 25 minutes.

Practice the conversation

  1. Owner Can I get a dashboard I can open myself?
  2. Operator You can open Dashboard any time. It shows deals, customers, revenue and upcoming jobs.
  3. Owner Why do I need your report, then?
  4. Operator The dashboard is today. My report is the whole month, checked.
  5. Owner Checked how?
  6. Operator I check the job records, look for duplicates and check every automation ran.
  7. Owner Did you ever find a problem?
  8. Operator Last month one crew's jobs were not marked done. I fixed it before your report went out.
  9. Owner So the numbers I see are right.
  10. Operator Yes. If I am not sure of a number, I say so on the page.

Quick check

  1. The day before the monthly report, you see one crew's jobs from last week are still marked Scheduled. Completed jobs look low. What do you do first?
    • Send the report now with a note that one number may be low.
    • Mark the finished jobs Completed, then recheck the count against `Jobs`.
    • Remove completed jobs from this month's report.
    • Ask the owner to count the jobs from their notes.
  2. Why is `Dashboard` a poor source for the monthly report?
    • It costs credits each time you open it.
    • It has no date filter, so it always shows the current view.
    • Only the owner can see it.
    • It shows only ad data.
  3. A crew of 3 people left 6 working days of finished jobs marked Scheduled, at 5 jobs a day. The report shows 300 completed jobs. What is the corrected total?
    • 306
    • 315
    • 330
    • 390

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community