Asking for a Review

Goal

Ask at a natural moment, get the customer’s permission to send a link, and use FSRevs to deliver the correct Review Flow without making the interaction feel scripted or pressured.

Before You Ask

Confirm that:

The customer has completed the relevant experience.
The Review Flow is enabled and available at the correct location.
Its review destinations open the intended business listings.
You have permission to contact the customer by email or text.
The sender has Send requests for that location.

Use a Short Spoken Prompt

Choose language that sounds natural for your team:

“Would it be okay if I text or email you a quick link to share feedback about your visit?”

Or, when the customer has already volunteered positive feedback:

“Thank you—that means a lot. Would you mind if I send you a link where you can share that feedback?”

The question asks for permission to send the request. It does not require a positive review or tell the customer what rating to leave.

Send the Request

After the customer agrees:

Open Launch or Quick Actions.
Select Send Review Request.
Choose the location and Review Flow when asked.
Type the customer’s name. Select Find customer to reuse an existing record; the finder carries the typed name into the search.
Confirm the customer’s email or phone number.
Check Recipient request history if there is any chance the same request was already sent.
Review optional sender or employee attribution only when it accurately describes the experience.
Choose FSRevs email/SMS delivery or Send from Your Device.
Read the final details and send.

Choose the Delivery Method

Use FSRevs email or SMS when you want FSRevs to perform and track delivery.
Use Send from Your Device when the customer expects the message from your own phone or email app. FSRevs prepares the tracked request, but cannot confirm whether you complete the send in the other app.
Use a Smart Link or QR code when the customer should open the experience themselves without you sending to their contact details.

After Sending

Do not send the same request again simply because the customer has not responded immediately.
Use request history and Message History to distinguish prepared, sent, delivered, failed, and customer activity states.
Let configured follow-up reminders handle later contact when appropriate.
Use the Review Flow’s Reports page to evaluate the overall experience, not one customer in isolation.

What to Say If the Customer Declines

Thank them and continue the normal interaction. Do not add their contact information just to send the request anyway.