Review trends by service and crew (heat map coming soon)
Read what reviews say about each service and each crew.
Read the lesson
Goal: Trace bad reviews to the service and crew behind them. Then make one fix and check it in 30 days.
You need: Any paid plan. Screens: Reviews inbox, the contact Activity tab, and Tag library.
Why this matters
One bad review is a story. Eight bad reviews about the same service is a pattern. Patterns point to a fix. A service may need more time. A crew may need coaching. A step may get skipped.
Owners often guess the cause. They blame the newest tech or the hardest customer. A guess leads to the wrong fix, and the reviews keep coming.
A review heat map by crew is coming soon to ServiceAgent. Until then, use this method. You read the reviews, find the job behind each one, and tag it. After a few weeks, the tags show the pattern.
The idea: trace, then fix one thing
The method has four steps.
- Filter. In
Reviews inbox, filterRatingto 1 to 3 stars for the last 90 days. - Trace. For each review, find the customer's contact. Open the
Activitytab. It lists the appointment and the staff member assigned. - Tag. Add two tags to the contact: the service and the crew, for example
review-neg-drainandcrew-2. - Count. Filter
Contactsby each tag. The biggest count is your pattern.
Then make one fix, note the date, and recheck in 30 days. One fix at a time shows what worked. Three fixes at once show nothing.
How many reviews do you need for a pattern? There is no exact number. A rule of thumb: three or more reviews that name the same service or the same problem within 90 days. Fewer than that, keep watching and keep tagging.
Trace, tag, count, then fix one thing
- Filter 1 to 3 star reviews, last 90 days
- Trace each review to its jobContact, then the Activity tab
- Tag the service and the crew
- Do three or more name the same service or problem?YesPattern: agree one fix with a dateNoKeep watching and keep tagging
- Recheck in 30 days with the same filter
Look beyond the star rating too. A 4-star review that says "great work, but they were late again" belongs in the count. Read the words, not only the stars.
Keep the tags after the fix. They build a history you can use in future reviews.
Be fair with crews. A pattern is a reason to coach, not to blame in public. Talk to the crew lead one to one first.
Build it in ServiceAgent
- Create the tags. In
Settings→Contacts & Pipeline→Tag library, add tags for each service and crew. Keep names short. - Filter the reviews. Open
Reviews inbox→Filters→Ratingfor low scores. - Trace each review. Open the contact, then
Activity. Note the service and the assigned staff. - Tag the contact. Add the service and crew tags.
- Count the tags. In
Contacts, useFilter by Tags. Save each as a view withSave Current View. - Write one fix. Agree it with the owner, with a date.
- Check it works. After 30 days, filter the same way. Compare the count.
Counting a tag in Contacts
Filter Contacts
Worked example: Northside Plumbing
Northside Plumbing has 8 techs and runs on Core. In the last 90 days, drain cleaning has 8 negative reviews, more than any other service. Water heaters have 3, leak repairs have 2 and repipes have 1. Several drain reviews mention a late arrival.
Negative reviews by service, last 90 days
You trace all 8. Six were the first job after lunch, across three techs. The drain service is set to 60 minutes, but the techs say real drain jobs run 75. Each morning drain job runs over, so the tech reaches the first job after lunch late.
When the 8 drain reviews happened
- First job after lunch6
- Other times of day2
Negative drain reviews8
The owner agrees one fix: add a 15-minute Buffer Between Appointments on the booking calendar. You note the date. In 30 days you count again. If late-arrival reviews drop, the fix worked.
The one fix at Northside
- Drain service set to 60 minutes
- Real drain jobs run 75 minutes
- The next job starts late
- 15-minute Buffer Between Appointments
- The next slot starts after the real job
- Late-arrival reviews counted again in 30 days
Tell the owner the result
After 30 days, report the count before and after the fix. Keep it to one line in the monthly report. For example: "Late-arrival drain reviews: 6 in the 90 days before, 1 in the 30 days after."
This is how the Keep stage proves itself. The owner sees a problem, a fix and a result in their own reviews. If the count did not drop, say so and pick the next cause to test.
Common mistakes
- Changing three things at once. Fix: one fix, one date, one recheck.
- Naming a tech in a team meeting. Fix: coach one to one.
- Guessing the cause. Fix: trace each review to its job first.
Do this now
Create service and crew tags for one client. Trace the last 5 low reviews to their jobs. Save one tag view.
Practice the conversation
- Operator Drain cleaning has 8 bad reviews in 90 days. Most mention late arrival.
- Owner That's Luis. They're always late.
- Operator I traced all 8. Six were the first job after lunch, across three techs.
- Owner So it's not Luis?
- Operator It's the schedule. Drain jobs run longer than the calendar allows.
- Owner What do we change?
- Operator One thing: a 15-minute buffer. We check again in 30 days.
Quick check
- Drain cleaning has 8 negative reviews in 90 days. Several mention late arrival. What do you do first?
- Change the service length, windows and roster at once
- Name the late tech at the team meeting
- Read those reviews and the jobs behind them
- Remove drain cleaning from the booking page
- Where do you find which staff member did the job behind a review?
- The contact `Activity` tab
- The review heat map
- `Analytics` → `Calls`
- The review itself
- You made one fix on May 1. When do you check if it worked?
- May 2
- About 30 days later, with the same filter
- At year end
- When the owner asks
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.