Define what completed service means
A review request should follow a real customer experience, but teams may disagree about when the work is complete. Write a practical trigger for the request, such as vehicle pickup, final walkthrough, or confirmed delivery. Include situations that need staff attention before any request is sent.
Verify the location and customer record
Check that the request points to the correct business location and that the customer contact details belong to the completed job. Shared systems and similar branch names can create simple mistakes. Use only the contact permissions and process approved by your business.
Choose one clear request path
Decide whether staff will offer an NFC card or plate, send an approved message, or use another established method. The wording should identify the business and explain the action without suggesting what rating the customer should give. Keep a direct support option available for unresolved service questions.
Make exceptions easy to record
If a customer is waiting for a correction, part, refund decision, or follow up call, record the next owner and pause the ordinary request process as appropriate. The checklist should help staff coordinate the service response, not hide a concern or pressure the customer into a public conversation.
Audit a small sample regularly
Review a few completed cases from different locations. Confirm the request timing, destination, location identity, and any follow up. Look for patterns the team can fix, such as a branch link that was copied incorrectly or a request that reaches customers before their service is actually finished.
