Operations
Part of Review automation workflow: what to automate first
Review automation workflow: what to automate first
A UK review automation workflow: make consent and suppression checks gates, then prioritise review requests, one reminder and negative-reply routing before NPS.
What to take away
- Automate the consent record before the request itself. The lawful basis, channel and timestamp are what a platform dispute or a data request asks for first.
- The fastest wins are one trigger after order completion, one reminder, and a routing rule that assigns each negative reply to a named owner.
- Hold NPS automation until someone owns detractor follow-up within a set time. A score nobody calls is a newsletter with a number in it.
- Every automated request needs a working opt-out route, plus a suppression list the next send reads before the queue builds.
Consent comes before cadence
A review request to a named customer uses personal data, so record the lawful basis for that processing rather than assuming consent is always required. The ICO's guidance on lawful bases is in its Guide to the UK GDPR, under “Lawful basis for processing”; its individual rights guidance explains how objections apply.
Consent to send decision
- Capture consent at checkout
- Store what, when, channel
- Workflow reads consent record
- Objection flag reaches all tools
- Suppress before next send
Consent captured at checkout is usually too narrow to cover a request sent four months later. Store what the customer agreed to, when, and through which channel, then let the workflow read that record instead of a policy page.
An objection has to travel with the contact record. If a customer asks you to stop, that flag must reach the CRM, the review platform and the email tool before the next send. The ICO's individual rights guidance covers what a customer can ask you to do, including the right to object to direct marketing.
Where an objection concerns a review that names the customer, routing a disputed review through data protection is a separate track with its own clock.
The first automations to switch on
Rank candidates by what they return per hour of setup, not by how clever they look in a demo. Most UK teams should switch on these four first.
- Record the lawful basis, permitted channel and any objection or opt-out. Make the pre-send suppression check a hard gate.
- Trigger one review request after delivery or job completion, once the gate passes.
- Send one reminder after a delay you set in the workflow, unless a review or objection has already been recorded.
- Route a negative reply to a named owner. Treat NPS follow-up as a separate, conditional alert, not as a fourth automation to enable first.
First four automations
- Request trigger after delivery confirmed
- One reminder if no review appears
- Route replies at three stars or below
- Pre-send suppression check on objections
Everything else, including NPS detractor follow-up, sentiment tagging and reply templates, waits until those three automations run quietly and someone reads the output each morning. Add NPS only when an owner and a first-contact target are agreed.
Where each trigger sits
Treat every candidate as a job with an input, a consent check and an owner. Anything without an owner waits until someone is named.
| Automation | Trigger | Consent check | Verdict |
|---|---|---|---|
| Request after purchase | Delivery or job completion | Basis recorded at the point of sale | Switch on first |
| Single reminder | No review after a set delay | Same basis, object flag read | Switch on first |
| Negative-reply routing | Reply at three stars or below | Internal only | Switch on first |
| NPS detractor follow-up | Score at six or below | Internal feedback, not marketing | Only with a named owner |
| Review platform sync | New review published | Public data | Switch on second |
| Win-back request | Renewal or repeat purchase | Fresh basis or new consent | Decide case by case |
Incentives need care. The Digital Markets, Competition and Consumers Act 2024 gives the CMA powers over unfair commercial practices, which covers fake and undisclosed incentivised reviews.
Where NPS automation fits
NPS automation answers a different question from a review request, and it follows a different rule. A detractor score is internal feedback, so keep it out of the public review funnel and out of any marketing list built from review contacts.
The usual failure is a closed loop with nobody closing it. Agree a first-contact service-level target that the named owner and rota can meet, including weekends if the workflow runs then. Automate the alert, then measure elapsed time to first contact rather than the score itself.
Channel preference and contact windows
Preferred channel is a data field, not an assumption. A customer who buys on a work email may not want a text to a personal number, and a wrong number is a data problem as well as a wasted send.
Email suits most UK ecommerce, while SMS suits trades and appointments where the job is still fresh. Examples to assess include Trustpilot or Reviews.io for review collection, Google Business Profile as a review destination, HubSpot or Salesforce for customer records, and Mailchimp for email delivery. Do not assume they connect: check that the chosen products and plans can pass the trigger, consent and suppression fields, and route replies as required. Selecting review-response software is largely a question of who holds the queue when a send misfires.
Set the request and reminder windows in the customer's local time, and choose the actual hours to fit your audience and service. Set the reminder delay in the workflow after fulfilment, and suppress it if a review or objection arrives first; document the settings so the team can test them.
Common questions
Which automation saves the most time first?
The request trigger and its reminder are the first candidates to remove repeated manual steps. There is no reliable time-saved figure without a baseline, so compare staff time spent on those tasks before and after automation.
Do I need consent for every automated review request?
No. Consent is one lawful basis, and legitimate interests can cover a request to an existing customer. You must still offer a clear way to object and honour it.
Can I automate review requests by SMS?
Yes, if the number was given for that purpose. SMS marketing also falls under PECR, so include an opt-out and keep sends inside reasonable hours.
Should NPS automation feed the review workflow?
Only for promoters, and only where the customer agreed to be contacted for that purpose. Detractor scores should stay internal.
