Review Request Timing Template for Service Teams

Review Request Timing Template: Rules, Scripts, and Metrics to Track

A review request should be timed like a service handoff, not blasted like a campaign. The client has just finished an appointment, visit, repair, session, or stay. If the experience went well, the ask should be quick and respectful. If there is unresolved friction, the request should pause.

This template gives you a practical timing rule, message scripts, cooldowns, stop rules, and metrics. For the broader workflow explanation, read review request timing for service businesses.

The Timing Rule

Start here:

Situation	Action
Service completed normally	Send after 1-3 hours
Service completed late at night	Send next business morning
Multi-day project completed	Send after final handoff or next business day
Complaint logged	Pause
Refund or dispute open	Pause
No-show or cancellation	Do not send
Client got a request recently	Skip or delay

The rule should be simple enough that staff can explain it without opening a settings page.

Why A Written Template Beats An Ad Hoc Judgment Call

The value of writing this rule down isn't really about the specific hours chosen, it's about removing the moment of improvisation where a staff member has to decide, on the fly, whether a particular client's visit was "good enough" to warrant a review request. That improvised moment is exactly where inconsistency creeps in: one staff member might send a request after almost any visit out of habit, while another skips it entirely for anything less than perfect, and the business ends up with review-request behavior that varies by whoever happened to close out that appointment.

A written template removes that variability by giving every staff member the same trigger and the same stop-rule checklist to run through, regardless of how confident they feel making that judgment call in the moment. This matters most for newer staff, who are the least equipped to develop the kind of intuitive judgment a tenured team member has built up over years of handling client interactions.

SMS Script

Hi [Name], thanks for choosing [Business]. If you have a minute, we would appreciate your honest feedback: [review link]

Keep SMS short. Do not ask only for five-star reviews, do not offer incentives unless the review platform allows it, and do not send the same client repeated asks in a short period.

Email Script

Subject: How was your experience with [Business]?

Hi [Name],

Thank you for choosing [Business].

If you have a minute, we would appreciate your honest feedback here:

[review link]

Your review helps us understand what went well and where we can improve.

Thanks, [Business]

Email is better when the service needs a little more context or when SMS consent is unclear.

Adapting Scripts Without Losing Their Purpose

The scripts above are a starting structure, not a rigid text to copy verbatim regardless of the business's actual voice and client relationships. A business with a more formal, professional clientele can adjust wording to sound more polished; a business with a casual, personal-relationship-driven client base can soften the language considerably while keeping the same underlying shape: a brief thank-you, an honest ask, and a clear link.

What shouldn't change regardless of tone adjustments is the restraint built into the core structure, no pressure language, no implied obligation, no repeated asking. Losing that restraint while customizing the tone defeats the purpose of using a tested template in the first place, since the restraint is exactly what keeps the request feeling like a genuine ask rather than a sales tactic.

Stop Rules

Do not send a review request when:

• The appointment was cancelled.
• The client was marked as a no-show.
• A complaint is open.
• A refund is pending.
• The invoice is disputed.
• Staff flagged the record for manager review.
• The client recently received a request.

These stop rules matter more than the wording. The fastest way to make review automation feel careless is to ask for a review after a bad or unresolved experience.

Why A Middling Review Deserves A Distinct Follow-Up Path

A three-star review sits in an awkward middle ground that most templates never explicitly address: the client had an experience worth commenting on publicly, and it wasn't fully positive, but it also wasn't bad enough to trigger a formal complaint through normal channels. Treating this the same as no response at all wastes a rare, direct piece of feedback a business would otherwise never see, since a moderately dissatisfied client often doesn't bother raising a complaint separately.

Building a distinct, low-pressure follow-up specifically triggered by a middling rating, not to contest the review or ask for a higher score, but to open a private conversation about what could have gone better, treats a three-star review as useful operational signal instead of either an ignored data point or a threat to manage defensively. This is meaningfully different from both the standard thank-you sent after a five-star review and the formal escalation triggered by an actual complaint.

Cooldown Rule

For repeat clients, choose a cooldown:

• Weekly service: ask no more than once every 60-90 days.
• Monthly service: ask after a meaningful successful visit, not every time.
• Project service: ask after the project is complete.
• First-time client: ask only if the service completed successfully.

Bulk requests should skip clients with recent non-expired requests.

Workflow Fit To Test

Tregovia can be evaluated for appointment-linked review requests, SMS or email channels, configurable timing, public review forms, moderation, responses, rating stats, and cooldown-aware bulk requests.

Keep the product claim narrower than the operating policy. Staff still need to decide which situations should pause a request: complaints, disputed invoices, refunds, cancellations, sensitive appointments, or unresolved service issues. Do not describe review automation as guaranteeing positive reviews or controlling third-party review platform outcomes.

Use the Reputation FAQ, review request timing for service businesses, CRM alternatives, and Tregovia pricing if review requests are only one part of a broader CRM comparison.

Metrics To Track

Track weekly:

• Requests sent
• Completion rate
• Average rating
• Low-rating count
• Duplicate requests blocked
• Staff-paused requests
• Response time to reviews
• Reviews by service type

If completion rate is low, change timing before changing copy. If low ratings increase, look at service quality and timing first.

Timing Questions

What is a good review request timing template?

Use a completed-service trigger, a short delay, one primary channel, a cooldown for repeat clients, and stop rules for complaints, refunds, cancellations, no-shows, or sensitive cases.

How long should the delay be?

For appointment-based services, 1-3 hours after completion is a useful starting point. Late-night or complex services may work better the next business day.

Should review requests be sent by SMS or email?

Use SMS for short transactional asks where consent exists. Use email when the request needs more context or the relationship is less immediate.

Where does Tregovia fit?

Tregovia can be evaluated for appointment-linked review requests, SMS or email channels, configurable timing, public review forms, moderation, responses, rating stats, and cooldown-aware bulk requests.

What should be measured?

Track requests sent, completion rate, average rating, low-rating count, duplicate requests, response time, and requests paused by staff.

Reviewing The Template Every Few Months

A timing template written once and never revisited can drift out of alignment with how the business actually operates a year later. Service mix changes, staff turnover means the people originally trained on the stop rules may no longer be the ones handling client interactions, and completion rates that looked healthy at launch may have quietly declined. Reviewing the template periodically, checking whether the stated delays and stop rules still reflect reality, keeps it a living operational tool rather than a document nobody actually consults anymore.

Timing Rule

A good review request timing template is mostly restraint. Ask after successful work, wait long enough to avoid feeling instant, skip the wrong moments, and measure completion before sending more requests.