Lesson 5 of 7 · 6 min

The monthly service rhythm: tune, report, review

Run the monthly rhythm: tune, report, review.

Read the lesson

Goal: Run every client on the same monthly rhythm. Tune weekly, report results monthly and hold a short review call.

You need: At least one live client. The Prove: Reporting course helps.

Why this matters

The retainer pays for a result every month, not for a setup that happened once. If the owner hears from you only when the invoice arrives, they start to wonder what they pay for. A steady rhythm answers that question before they ask it.

Tuning also keeps results from slipping. Customers ask new questions. Prices change. A tech leaves. Each change opens a small gap in the agent or a workflow. Weekly tuning closes those gaps while they are small.

A fixed rhythm protects your time too. When every client gets the same weekly and monthly tasks, you can plan your weeks. You can also see when your book is full.

The three loops

Weekly: tune (about 30 minutes per client).

  1. Read 10 call transcripts. Start with calls that ended in a transfer or had no booking.
  2. Check the answer rate in Analytics → Calls → Success Rate.
  3. Open each workflow's History → View run history. Look for failed runs. Each run retries up to 3 times, so a final failure needs your fix.
  4. Check Conversations for threads with no reply.
  5. Glance at Billing → Usage history for credit spikes.
  6. Fix one or two things. Write down what you changed and the date.

Monthly: report (about 1 hour per client). One page, in this order:

  1. The package KPIs: this month, last month and the baseline.
  2. What you changed this month, with dates.
  3. What you learned, in one or two lines.
  4. The next fix you plan.
  5. The cost line: your fee, the plan and any Safe Pack top-ups.

Report results, not activity. Owners do not care that 1,400 texts went out. They care whether more customers showed up and paid. Activity counts belong in your own working notes.

ServiceAgent has no scheduled reports and no custom report builder. You build the page yourself from Analytics, Contacts → Reports and your notes. The Prove course shows how.

Monthly: review call (about 30 minutes). Walk through the one page. Ask what the owner noticed. Agree on the next fix. End on time.

KPIs by package

PackageKPIs on the report
Never Miss a JobAnswer rate, jobs booked by the AI
Business on AutopilotThe above, plus no-show rate, estimate close rate, days from job done to paid
Growth EngineAll of the above, plus reviews per month, average rating, active members, cost per booked job

SAU recommends 6 KPIs for every client report, covered in Prove lesson 1. You may adjust them to the owner's real needs, but never to hide a bad month.

By size. An owner-operator wants the page and five minutes on the phone. A fleet's office manager often reads the report first, so send it to both. A multi-location group wants the same KPIs for each location side by side, so the weakest site stands out.

When a KPI drops

Every client has a bad month sooner or later. How you handle it decides whether they stay.

  1. Check the data first. A calendar that stopped syncing or a forwarding change can make a number look wrong. Fix the data, then look again.
  2. Find the cause. Read the transcripts and run history for the weeks the number fell. Look for one change that lines up with the drop.
  3. Fix one thing and note the date. Watch the same KPI for two weeks after the fix.
  4. Tell the owner before they ask. Put the drop on the report with the cause and the fix. Never drop a bad KPI from the page.
Fig 1

When a KPI drops

  1. A KPI drops on the monthly pull
  2. Is the data wrong, such as a broken sync?YesFix the data, then look againNoFind the cause in transcripts and run history
  3. Fix one thing and note the date
  4. Watch the same KPI for two weeks
  5. Put the drop, the cause and the fix on the report
Owners forgive a bad month that you explain. Never drop a bad KPI from the page.

Owners forgive a bad month that you explain. They do not forgive a number that quietly disappeared.

Planning your month across clients

Put the rhythm on one calendar for your whole book. With 10 clients, give each a fixed weekly tuning slot, such as five on Monday and five on Tuesday. Pull all KPIs on the first two working days of the month. Send reports by day 5. Book review calls in the second week.

Fig 2

The monthly rhythm

  1. Week 1Tune; pull KPIs on days 1 and 2; send reports by day 5
  2. Week 2Tune; hold the 30-minute review call
  3. Week 3Tune: 10 transcripts, run history, one or two fixes
  4. Week 4Tune; note every change with its date
Tuning every week, a report and a call every month.

When the calendar has no room for a new client's slot, your book is full. That is your signal to raise prices, drop the weakest fit or hire help.

Build it in ServiceAgent

  1. In your own account, build a workflow with a weekly Scheduled Trigger. Add a Create CRM Task step for each client's tuning. Set an Owner, a due date and Priority.
  2. Each week, work through the six tuning steps above. Note changes on the client's deal.
  3. In the first week of the month, pull the KPIs. Answer rate is in Analytics → Calls. No-shows are in Analytics → Appointments (No Shows, Show Rate). Close rate is in Contacts → Reports → Win Rate.
  4. Build the one-page report and send it as a PDF to the inbox the owner actually reads.
  5. Book the review call in the second week.
  6. Check it works. Every number on the page should match the screen you took it from. Recheck any number that moved a lot.

Worked example: Green Acre Lawn and Landscape

Green Acre has 5 crews on Growth. It runs Business on Autopilot. Here is one month's report, with example numbers.

KPIBaselineLast monthThis month
Answer rate81%94%96%
Jobs booked by the AI a week089
No-show rate6%4%3%
Estimate close rate30%33%35%
Days from job done to paid954
Fig 3Example numbers

Green Acre against its baseline

81% to 96%Answer rate
6% to 3%No-show rate
9 to 4Days from job done to paid
Results against the baseline, not activity counts.

What changed. On the 4th, you added a quick answer about one-time mowing. Transcripts showed the agent stalled on that question. On the 18th, you moved the payment link text to 1 hour after the job closes.

Next fix. Estimates over $2,000 close slowest. Next month, you test a day 3 phone task for those.

Cost line. $997 retainer, $95 Growth billed yearly and one $20 Safe Pack. Total: $997 + $95 + $20 = $1,112.

Fig 4Example numbers

Green Acre's cost line this month

  • Your retainer$997
  • Growth plan, billed yearly$95
  • One Safe Pack$20

Total$1,112

Show every dollar, including the Safe Pack top-up.

Your time. Weekly tuning: 4.4 weeks × 0.5 hours = 2.2 hours. Report: 1 hour. Call: 0.5 hours. Total: about 3.7 hours, plus a small buffer for fixes.

Fig 5Example numbers

Hours per client per month

Tuning: 4.4 weeks × 0.5 hours2.2 hours
+Monthly report1 hour
+Review call0.5 hours
Total, before a buffer for fixesabout 3.7 hours
Know your hours per client before you set your book size.

Common mistakes

  • Reporting activity. Fix: show package KPIs and what you changed.
  • Changing five things at once. You cannot tell which one worked. Fix: one or two changes a week, with dates.
  • Hiding top-ups. Fix: put every Safe Pack on the cost line.
  • Skipping the call when the month was good. Good months build trust too. Fix: keep the call short, but keep it.
  • Sending the report to an inbox nobody reads. Fix: ask the owner where they read email.

Do this now

Set recurring weekly tuning tasks for each live client. Draft a one-page report template with the five sections. Time: 20 minutes.

Practice the conversation

  1. Operator This month, 96% of calls were answered. Last month was 94%.
  2. Owner And jobs?
  3. Operator The AI booked about 9 a week. No-shows dropped to 3%.
  4. Owner What did you change?
  5. Operator I added an answer for one-time mowing. Customers kept asking.
  6. Owner What's this $20?
  7. Operator One credit top-up in your busy week. It's on the cost line.
  8. Owner What's next?
  9. Operator Big estimates close slowest. I'll test a day 3 call task for those.
  10. Owner Fine. Same time next month?
  11. Operator Same time. I'll send the page two days before.

Quick check

  1. A Business on Autopilot report lists 1,400 texts sent and 220 workflow runs. The owner asks what they pay for. What should the report show instead?
    • More activity counts, such as emails and AI steps
    • A full list of every message sent
    • Package KPIs like estimate close rate, plus what you changed
    • Ad return and review counts
  2. A workflow's run history shows a final failed run after 3 attempts. What do you do?
    • Nothing; the system retries forever
    • Find and fix the cause, then check the next run
    • Delete the workflow
    • Wait for the monthly report
  3. You tune each client for 45 minutes a week, with 4.4 weeks a month. A report takes 1 hour and the call 0.5 hours. How many hours per client per month?
    • 3.7
    • 4.3
    • 4.8
    • 5.5

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

Learn

Get certified

Community