Skip to content

Request reviews consistently and route feedback to a person

This page sets out how Durward invites reviews after completed appointments inside a scheme your team approves, and how negative or ambiguous feedback reaches a named person. It lists the record behind each invitation and where Durward stops.

A review request workflow turns a completed appointment in your own record into one invitation, and routes whatever comes back. Durward sends inside an approved scheme. Your team approves the scheme before anything is sent, with a named owner, the invitation rule, the channels, the wording, the stop rules and a review point. The same rule applies to every eligible completed appointment, and no customer is chosen, or left out, because of how they are expected to rate. Negative or ambiguous feedback goes to a named person with the case attached. A public reply is a draft that a named person approves and posts. Anything outside the scheme is held for a person.

What the service covers, and what it does not

A review request workflow turns a completed appointment in your own record into one invitation, and routes whatever comes back. Durward sends inside an approved scheme. Your team approves the scheme before anything is sent, with a named owner, the invitation rule, the channels, the wording, the stop rules and a review point. The same rule applies to every eligible completed appointment, and no customer is chosen, or left out, because of how they are expected to rate. Negative or ambiguous feedback goes to a named person with the case attached. A public reply is a draft that a named person approves and posts. Anything outside the scheme is held for a person.

What is included

  • An invitation eligibility table for each appointment type: the completed status, the contact route, the opt-out check, the gap since any earlier invitation and any open matter.
  • Review invitations: one invitation for each eligible completed appointment, sent by Durward inside the approved scheme on the channels agreed in the scope and available on your platform, which can include SMS, WhatsApp and email.
  • Sender and stop: each message names your business as the sender and says how to stop further messages.
  • Consent and opt-outs: the consent wording and where each consent and opt-out is recorded are agreed in the scheme, as for service reminders. A request to stop ends every message from your business to that customer through this workflow, and the stop is recorded. Whether a review invitation is a service message or marketing is for you and a qualified adviser, and the scheme records the answer.
  • Replies to an invitation: a reply is logged. A negative or ambiguous one goes to a named person with the case attached.
  • Human response drafts: where a public review reaches Durward, through your team or a route agreed in the scope, Durward drafts a reply for a named person to edit, approve and post.
  • A pilot on one appointment type, with the measures agreed beforehand.
  • A written scope that names what is set up, which later changes are covered and what is quoted separately. This service is offered alongside another project, and the pricing page shows its fee.

What is not included

  • Choosing who is invited by how the customer is expected to rate, or asking customers privately first and inviting only some of them on the result. Every eligible completed appointment gets the same invitation.
  • A fake review, or a review written by Durward, your staff or anyone else in a customer's name.
  • An incentive. No discount, prize, gift or other benefit is offered for leaving a review, and the invitation does not ask for a particular rating.
  • An automatic public reply. Durward does not post a reply to any review. A named person approves and posts each public reply.
  • A reply to negative or ambiguous feedback that no person has written or approved.
  • A message to a customer whose permission is not recorded, or who has opted out. The case leaves the queue and the reason is kept.
  • Any promise about how quickly a person responds, and any promise about the number of reviews, a rating or revenue.
  • Advice on how a review site ranks, shows or removes reviews.
  • A legal view on contact permission, marketing or review wording. Your team approves the wording and should take qualified advice where the question matters.
  • A connector to a system this page does not describe. If you need one, say so on the fit call and it is assessed there.

Facts, checks and the approved scheme

An invitation goes out only when the record shows a completed appointment and the scheme allows it.

Completed appointment trigger

A case is eligible when your own record shows the appointment as completed, with its date, the customer and the contact route. If completion is not recorded, the first job is to repair the record, not to infer it from a customer's silence. A cancelled, moved or missed appointment is not eligible, and neither is an appointment type your team has left out of the scheme, such as one where an invitation would be unwelcome.

One invitation rule

The scheme holds one rule: the same wording, route and timing for every eligible completed appointment. It is written down before anything is sent and covers the whole record group. It does not predict how a customer will rate, and it offers no incentive. Any exclusion is a fact in the record that the scheme names in advance, such as an open complaint, and it applies to all cases alike.

Approved channels

The scheme sets the channels agreed in the scope and available on your platform, which can include SMS, WhatsApp and email, and nothing is assumed. A review invitation is an outbound message, so it follows the same approved-scheme rule as a service reminder. Your team approves the wording, the frequency and the stop rules, consent and opt-outs are recorded as the scheme sets out, and a named owner takes anything outside it. This page gives no legal view. Whether an invitation is a service message or marketing is decided in the scheme, with qualified advice where the question matters.

Duplicate prevention

Before sending, the workflow checks the appointment identifier, the date and the customer against the invitation log. One invitation goes out for each completed appointment. A customer invited for an earlier visit is not invited again within the gap the scheme names, and a visit logged twice, or a booking moved and marked complete again, is counted once. Each send is logged with the appointment, the channel, the wording version and the outcome.

Negative and ambiguous feedback

The scheme names the signals that count as negative or ambiguous, such as a complaint, a concern about care or safety, a dispute about a charge or a reply the workflow cannot place. A request to stop is recorded as an opt-out. Each of these leaves the queue and reaches a named person with the case attached, which holds the appointment, the invitation sent, the customer's own words and any earlier messages. Durward does not reply to it. The person decides whether to contact the customer, and writes or approves any message.

Setting up the scheme, then testing and reporting

Nothing goes to a customer until your team has approved the scheme and each path has been tested.

  1. Choose one appointment type

    You supply a focused export of completed appointments for one appointment type, with the date, the customer, the contact route and any open complaint or dispute.

    Buyer receives: A record group and the list of fields used.

  2. Write the scheme

    Your team and we write the eligibility table, the one invitation rule, the channels, the wording, the timing, the gap between invitations and the stop rules. A named owner takes every exception. The scheme contains no incentive and no selection by expected rating.

    Buyer receives: A written scheme with your team's approval recorded.

  3. Set up consent, opt-outs and the invitation log

    We agree the consent wording, where each consent and each opt-out is recorded. Durward receives them and stores them in that record. How long the records are kept is agreed for your workflow and is not set on this page.

    Buyer receives: A consent and opt-out record design that your team has approved, and the invitation log.

  4. Agree the feedback routing and the drafts

    We agree the signals that count as negative or ambiguous, who receives each type and what the case note holds. We write the format of a draft reply. It is marked as a draft, and only a named person approves and posts it.

    Buyer receives: A routing table, a case note and a draft format, each approved by your team.

  5. Test before any customer is contacted

    On test records we run an eligible appointment, a cancelled one, a duplicate, an opted-out customer, a negative reply, an ambiguous reply and a public review that needs a draft. Each path is checked against the scheme.

    Buyer receives: A test log for each path, kept with the scheme.

  6. Run a pilot and read the measures

    Durward runs the scheme on that appointment type. Your team reads the measures agreed beforehand, such as invitations sent, cases held, duplicates stopped, opt-outs, feedback routed to a person and how each case was resolved, and drafts approved, edited or discarded. The number or rating of reviews is not a measure we promise. We confirm in writing what is set up and what is quoted separately.

    Buyer receives: A pilot read-out and a written scope.

Four cases, and what Durward does with each

These patterns are for scoping and are not client results.

A completed appointment with no invitation yet

Your record shows an appointment as completed, and no invitation has been sent for it.

Trigger
The appointment reaches the point the scheme names for an invitation.
Systems or sources
Your booking record, the invitation log and the consent and opt-out record.
What Durward does
Check the eligibility table again, covering completed status, contact route, no opt-out, no earlier invitation within the gap and no open matter. Send the approved invitation on an agreed channel, with the route to leave a public review and a way to reply, and log the send.
Human checkpoint
Your team approved the wording and the stop rules. A named person owns every reply.
Exception route
An opt-out, an open complaint or dispute, a missing contact route or any doubt stops the invitation and leaves the case with a person, with the reason.
Success measure
How many invitations were sent, how many were held and why, reviewed by your team.

A reply that is negative or ambiguous

A customer answers the invitation with a complaint, a concern or words the workflow cannot place.

Trigger
A reply arrives on a channel your team has switched on.
Systems or sources
The invitation log, your booking record and the case note.
What Durward does
Read the reply against the signals in the scheme. Stop any further message to that customer, attach the appointment, the invitation and the customer's own words, and pass the case to the named person.
Human checkpoint
The named person decides whether and how to contact the customer, and writes or approves any message. This page makes no promise about how quickly a person responds.
Exception route
A request to stop is recorded as an opt-out. A concern about care or safety, or a dispute about a charge, goes to the person who owns it. Nothing is posted publicly.
Success measure
How many replies were routed, to whom and how each case was resolved, reviewed by your team.

Human response drafts for a public review

A public review has been posted about your business, and your team wants to consider a reply.

Trigger
A review reaches Durward, through your team or a route agreed in the scope.
Systems or sources
The text of the review, your approved reply guidance and, where your team links it, the appointment record.
What Durward does
Write a draft reply in your agreed voice, mark it as a draft and pass it to the named person. Durward posts nothing.
Human checkpoint
A named person edits or rewrites the draft, approves it and posts it, or decides not to reply.
Exception route
A review that mentions health, care, safety, an allegation or a dispute goes to the person with no draft, and the person decides how to answer.
Success measure
How many drafts were approved, edited, discarded or not used, reviewed by your team.

An appointment that is not eligible, or already invited

A cancelled appointment, a visit logged twice, or a customer invited for a recent visit.

Trigger
The record reaches the invitation point and the eligibility check does not pass.
Systems or sources
Your booking record and the invitation log.
What Durward does
Leave the case out of the queue, record the reason and send nothing. Where the same visit appears twice, count it once.
Human checkpoint
Your team names the gap between invitations and any appointment type that is left out. The rule is the same for all cases.
Exception route
A case where the record is unclear, such as a completed status with no date, goes to the named owner to repair the record.
Success measure
How many cases were left out and for which reason, reviewed by your team.

Human ownership, and who does what

Durward sends inside the scheme your team has approved, with a named owner, a review point and exceptions held for a person. Anything the scheme does not cover reaches a named person.

Durward prepares

  • The scheme, with the eligibility table, the one invitation rule, the channels, the wording and the stop rules, for your approval.
  • The consent and opt-out record design.
  • The routing table and the case note for negative and ambiguous feedback.
  • Human response drafts, marked as drafts, for a named person to approve and post.
  • A test log for each path, and a pilot read-out.

Your team keeps

  • Approval of the scheme, the channels, the wording and the frequency before anything is sent.
  • The named owner, and every decision about contacting a customer who has given negative or ambiguous feedback.
  • Each public reply. A named person approves and posts it.
  • Checking the invitation wording against the current terms of the review site you use, with qualified advice where the question matters.
  • You can ask for a copy of your customer lists, consent and opt-out records, invitation log and message templates, and the written scope sets out how a copy reaches you if you leave.

When this is the right size of tool

Check first whether your booking or customer platform already sends review requests. A feature you already pay for is recommended where it does the job.

This service adds value when

  • Your records show completed appointments, and a person can say who owns feedback.
  • Customers are asked for reviews by hand, unevenly or not at all.
  • You can name a person to take negative feedback and to approve public replies, and your team is content to approve a written scheme.

Use what you already have when

  • Your platform already sends a review request for each eligible appointment and someone owns the result. Switch the feature on and stop there.
  • Your records do not show which appointments were completed. Repairing the record comes first.
  • Nobody can be named to take negative feedback or to approve a reply.
  • The aim is to raise a rating, or to invite only the customers likely to be pleased. This service does neither.

Bring one appointment type and one question about reviews

Tell us which record shows completed appointments, which channels you use and who would take negative feedback. We will say plainly if a feature you already have covers it.