Automation should start when service is genuinely completed, not when an appointment is created. Review the trigger and cases where a request is inappropriate.
What may be happening
If a customer receives two requests for one job, several systems may be triggering messages. Identify the responsible tool and the record preventing repeats.
What to change first
- Define a completed-service event and job identifier to check whether the request was already sent.
- Request honest feedback without incentives or filtering for positive reviews only.
- Test cancellation, rescheduling, and repeated events. Confirm they do not create unintended messages.
An example to adapt
Example: one visit may be updated several times in the CRM. The system should recognize the job and retain the request date instead of resending on every status change.
How to check progress
Review unique requests per completed service and duplicate-message complaints. Audit links and wording in each language.
Questions about this problem
Should I screen for satisfaction before sending the review link?
Do not use it to select only positive feedback. Issue support should exist without manipulating who can review.
Your review checklist
Check what you have reviewed. This list is kept only while this page stays open.
Sources for further reading
Google: tips for getting reviewsHow we can help
At Community Noguer, we connect pages, content, and follow-up around what your team needs.
View the related service Use the self-assessment