Jacksonville, FL · Enterprise and growing businesseshello@rsoftware.net  ·  (904) 456-8806
R SoftwareTalk to us
Does It Actually Pay Off? · Part 2 of 8

Your Two-Week Baseline: Measuring With the Tools You Already Have

Phil Roberts
Founder, R Software & Consulting
· 5 min read

In the first article in this series, we made the case for writing down how things work today before you add AI or automation. Without a "before," you can't tell whether the "after" is any better.

This article is for the person who will actually pull those numbers. In a lot of offices that's the office manager. You don't need new software. Your phone system, your scheduling software, your inbox, and a plain spreadsheet can give you a fair picture in about two weeks.

Before you start: set up one simple spreadsheet

Make one spreadsheet with a tab for each source: Calls, Replies, Appointments, and Task Tally. Add a Notes tab for anything unusual, like a staff member out sick, a storm, or a holiday.

Pick two normal weeks. If an unusual week can't be avoided, measure anyway and note why. Imperfect numbers you understand beat no numbers.

One rule from day one: this file holds counts and times, not people. No names, phone numbers, email addresses, or details about anyone's situation. More on that below.

Source 1: Your phone system

Many business phone services have a call log or reporting screen, often called "call history" or "reports." If you can't find yours, ask your phone provider.

What to pull, for each day of the two weeks:

  • Inbound call volume by hour. How many calls came in during each hour of the day.
  • Missed and abandoned calls by hour. Calls nobody answered, and calls where the person hung up while waiting or ringing. Some systems show these separately; some lump them together. Either is fine, as long as you note which.
  • Voicemails left. How many missed calls turned into a voicemail, and how many didn't.

Breaking it out by hour matters. A daily total can hide a pile-up of missed calls at lunch or right after you close.

If your system only lets you export the raw call list, that's fine. Copy just the date, time, and outcome (answered, missed, voicemail) into your spreadsheet, and leave the caller's number behind.

Source 2: Your inbox and web forms

Here you want time to first reply: how long someone waits between sending a message and getting a real answer from a person (not an automatic "we got your message").

You don't need to measure every email. A sample works:

  • Each day, pick the first five or so new inquiries that came in by email or web form.
  • Note the date and time each one arrived and the date and time of your first real reply.
  • Write the gap in hours, and mark whether it arrived during business hours or after.

If your forms send to a shared inbox, the timestamps are already there. A CRM, if you have one, may show when a lead came in and when it was first contacted.

Source 3: Your scheduling or practice-management software

Most scheduling and practice-management tools keep a record of appointment changes. Look for:

  • No-shows: appointments where the person didn't arrive and didn't call.
  • Reschedules: appointments moved to a different time.
  • Cancellations, if your software tracks them separately from reschedules.

Many systems have a built-in report for these. If yours doesn't, a daily look at the schedule and a tally mark works fine. Keep only the weekly counts.

Source 4: A short task tally sheet

Some important numbers, like staff time on repetitive work, don't live in any system. For those, ask the people doing the work to jot it down.

Keep the sheet short so people will actually use it. Three or four columns are plenty:

Date Task Minutes Had to fix something? (Y/N)

Choose a few tasks tied to the workflow you're considering: reminder calls, typing intake forms into your software, returning voicemails, chasing missing paperwork. Rough minutes are fine. The goal is "about 15 minutes," not a stopwatch.

Hypothetical example: Picture a small property management office where two people share the phones. For two weeks, the office manager exports the call log each Friday and copies the hourly counts into the Calls tab. Each morning, she logs reply times for the first few web inquiries from the day before. Both staff keep a tally sheet by their keyboards for maintenance-request calls and follow-ups. At the end, she has missed calls by hour, average time to first reply, and weekly minutes spent on follow-ups. Nothing new was purchased.

A word on the tally sheet: make it clear to your team that it measures the task, not the person. If people feel graded, the numbers get less honest.

Keeping the baseline private and secure

Every source above touches customer, client, or patient information. The baseline doesn't need any of it. A few habits keep it that way:

  • Record counts and times, not personal details. "3 missed calls between 12 and 1" is enough. You don't need to know who called.
  • Leave raw exports where they came from. If you download a full call list or report, copy out only the counts you need, then delete the download rather than leaving it in your Downloads folder or email.
  • Store the spreadsheet with limited access. Keep it in a shared drive or folder that only the people working on the baseline can open, not on a public link or a personal device.
  • Don't paste records into outside tools. Avoid copying call lists, emails, or schedules into a free online tool or chatbot to "help analyze" them. Customer information shouldn't leave the systems you've approved for it.
  • Follow your industry's rules. If you're in dental, therapy, law, or accounting, treat anything pulled from your systems with the same care as your other protected records, and check with whoever handles your compliance if you're unsure.

At the end of two weeks

Put a short summary at the top of your spreadsheet:

  • Average inbound calls per day, and the busiest hours
  • Missed or abandoned calls, during business hours and after hours
  • Voicemails left
  • Average time to first reply on emails and web forms
  • No-shows and reschedules per week
  • Weekly minutes on each tallied task, and how often something had to be fixed

That's your baseline. Save a copy and don't edit it, so you'll have a fixed "before" to compare against later.

When we run an assessment with a business, building this baseline together is one of the first steps, before anything gets built, so we can both see later whether it made a difference.

Your two-week baseline checklist

  • Pick two normal weeks and note anything unusual.
  • Set up one spreadsheet with tabs for Calls, Replies, Appointments, Task Tally, and Notes.
  • From your phone system: inbound calls and missed/abandoned calls by hour, plus voicemails left.
  • From your inbox and web forms: time to first real reply on a daily sample.
  • From your scheduling software: weekly no-shows and reschedules.
  • Keep a short task tally sheet for minutes spent and fixes needed.
  • Record counts and times only, delete raw exports, and limit who can open the file.
  • Summarize the results and save an unedited copy as your "before."

Written with help from our AI assistant.

Phil Roberts is the founder of R Software & Consulting, a CTO-level engineer who builds and runs production platforms.
Free savings snapshot

Want a rough estimate of what automation could save each year?

A 30-minute call, at no cost.

Get my free savings snapshot →

Follow R Software & Consulting on LinkedIn for practical, secure AI ideas for local small businesses. Follow us on LinkedIn (opens in a new tab)

← All insights

Start here

See what AI can accelerate for you.