How to Send Manual Google Review Requests at the Right Time

Manual Google review requests work best when they are sent soon after a customer has had a real chance to assess their experience. They are especially useful for in-person visits, phone customers, or completed interactions that did not generate an email suitable for an automated follow-up. The goal is simple: send one brief, honest invitation with a direct review link, without asking for a particular rating or turning the request into a sales message.

At Revilope, manual requests are designed to supplement a regular review-request routine. You can paste one or more customer email addresses into the dashboard, then choose whether to send the request as soon as possible or apply your business’s saved delay.

When should you send a manual Google review request?

The right time is not when you first collect an email address. It is when the customer can give informed feedback about what they received. A request sent too early can feel confusing, while one sent long after the interaction may arrive after the details have faded.

Manual sending is a practical option when there is no qualifying completion email to trigger a follow-up. Common examples include:

An in-person customer whose email was collected after a completed visit.
A phone customer who has received the product, service, or answer they needed.
A customer handled through a separate system that is not part of your usual email workflow.
A recently completed interaction where a team member did not send the usual completion email.

Use the same test you would use for any review request: could this customer fairly describe their experience if the invitation arrived now? If they still need to receive a delivery, test a repair, use a product, or confirm that a support solution works, wait until that evaluation period has passed.

How to send manual Google review requests without making them feel random

A manual request should still follow a repeatable process. That protects the customer experience and makes it less likely that requests are sent inconsistently or at the wrong stage.

Identify a completed, reviewable interaction. Choose customers who have received the value they are being asked to review. A completed appointment, final handoff, delivered order, or resolved support issue is generally more appropriate than an inquiry, booking, or payment reminder.
Check that the timing makes sense. A same-day completed experience may suit a short delay. Products and outcomes that need setup, use, or inspection often deserve more time.
Use the correct customer email address. Confirm the address before sending. A review request should go to the person who had the experience, not a shared or unrelated contact.
Send one clear invitation. Keep the wording short, include a direct Google review link, and leave the choice entirely with the customer.
Review the request activity. Check whether the request was scheduled, sent, cancelled, skipped as a duplicate, rejected, or failed instead of assuming it went out.

This approach is more useful than waiting until the end of a busy month and sending a broad batch to customers whose interactions happened long ago. A smaller set of timely requests is easier for customers to connect with a specific experience.

Choosing between sending now and using a delay

Manual does not have to mean immediate. A short delay separates the review invitation from the original interaction and gives the customer room to reflect. Revilope lets you send a manual request as soon as possible or use the saved delay for that business.

Customer situation	Useful timing approach	Reason
A clearly completed same-day service or appointment	Send soon or use a short delay	The experience is fresh, but the customer is not being asked at the exact moment of completion.
A completed service or straightforward purchase	Consider a 12 to 24 hour delay	The customer has breathing room while still remembering the details.
A product, repair, installation, or outcome that needs brief use	Use a longer delay	The customer needs enough time to form a meaningful opinion.
An interaction completed months ago	Usually do not treat it like a routine manual send	The request may feel disconnected from the experience and the customer may no longer recall useful details.

For many completed interactions, 24 hours is a sensible starting point. It is not a universal default. The best delay depends on when customers can honestly evaluate the experience, not on a fixed calendar rule. Our guide on choosing a Google review request delay explains how to match timing to different customer journeys.

What a manual review request should say

A strong request is brief, recognizable, and easy to act on. It thanks the customer, invites honest feedback, and directs them to the correct Google review page. It does not need a long explanation of why reviews matter to your business.

Use this structure:

A simple thank-you.
An invitation to share their experience or honest feedback.
One direct link to the correct Google review page.
A clear reply path if the customer would prefer to contact your business directly.

For example:

Thank you for choosing us. We would appreciate hearing about your experience. If you would like to share feedback on Google, you can use the link below.

The language is courteous because it gives the customer a choice. Avoid asking for a five-star rating, offering something in exchange for a review, or writing repeated reminders that make the customer feel chased. Ask for feedback, not a predetermined outcome.

Why manual requests need the same standards as automated ones

It is easy to treat a manual request as an exception and skip the safeguards that make a regular workflow more customer-friendly. In practice, the same standards matter whether a request is typed into a dashboard or triggered from an email.

Use a consistent template: A custom template keeps the message recognizable and avoids rushed, improvised wording.
Use the right review link: Test that the link opens the correct Google Business Profile before sending requests to customers.
Respect opt-outs: Customers should have a straightforward way to decline future review requests.
Avoid duplicates: One appropriate invitation is better than several prompts about the same interaction.
Keep business details separate: If you manage multiple businesses, each should use its own review link, template, reply-to address, delay, and customer records.

Every live Revilope review request includes an unsubscribe option. If a recipient unsubscribes, we prevent future review requests from that business and cancel any requests that are still waiting to be sent. Our duplicate detection also helps show when a request was skipped because the customer was already contacted.

Using manual requests in Revilope

Manual requests are available from the Revilope dashboard. Add one or more customer email addresses, then choose to send the requests as soon as possible or use the delay already saved for that business. Each customer receives an individual email, and manual requests use the same plan allowance as BCC-triggered requests.

That makes manual sending useful for the gaps that email-triggered automation cannot cover. For the customer emails that do mark a completed experience, our BCC workflow can reduce repetitive work: add your private Revilope address in BCC on the qualifying email, and we schedule a separate branded follow-up after your chosen delay. Read more about using Revilope to see how manual and BCC-triggered requests can sit within one workflow.

Check activity after sending

Manual sending should not be a black box. Request activity shows whether a request is scheduled, sending, sent, failed, cancelled, skipped as a duplicate, or rejected. These statuses help you distinguish between a customer who simply has not responded and a workflow issue that needs attention.

For example, a rejected request can point to an email address that has not been verified as an authorized sender. A skipped request can indicate that the customer has already received a request. We retry temporary sending failures up to three times. If a request permanently fails before it is sent, the reserved request is returned to your plan allowance.

Frequently asked questions about manual review requests

Should I send a manual request to every customer?

Use a consistent standard based on a completed, reviewable experience rather than trying to predict who will leave a positive review. Not every interaction needs a request, but eligible customers should not be selected only by the rating you expect them to give.

Can I send manual requests to more than one customer at once?

Yes. In Revilope, you can paste one or more customer email addresses into the dashboard. Each recipient receives an individual request rather than seeing other customers’ email addresses.

Are manual requests a replacement for review-request automation?

They are best used alongside automation. Manual requests cover in-person, phone, and other interactions without a suitable trigger email. BCC-triggered requests are useful when your normal customer email reliably marks the point at which an experience is complete.

What is the most common manual review request mistake?

Sending at the wrong time. A request sent before the customer has received the full value of the product, service, or support outcome is unlikely to feel natural or produce useful feedback.

Manual review requests are most effective when they are timely, brief, and respectful of customer choice. If you want one place to handle both manual sends and email-triggered follow-ups, start sending free with Revilope.