Skip to content

Follow up genuine service dates and unresolved work

This page sets out how Durward sends service reminders and follows up open remedial quotations inside a scheme your team approves. It lists the record behind each message, what happens on a reply or an opt-out, and where Durward stops.

A service reminder workflow finds a service date or an unresolved remedial quotation in your own records, checks it against the current booking, the owner and the stop rules, and then sends the message your team has approved. Durward sends inside an approved scheme. Your team approves the record group, the channels, the wording, the frequency and the stop rules before anything is sent, and Durward records consent and opt-outs as the scheme sets out. Anything outside the scheme is held for a named person. The workflow makes no automatic safety decision, sets no examination schedule, makes no remediation claim and does no billing automation.

What the service covers, and what it does not

A service reminder workflow finds a service date or an unresolved remedial quotation in your own records, checks it against the current booking, the owner and the stop rules, and then sends the message your team has approved. Durward sends inside an approved scheme. Your team approves the record group, the channels, the wording, the frequency and the stop rules before anything is sent, and Durward records consent and opt-outs as the scheme sets out. Anything outside the scheme is held for a named person. The workflow makes no automatic safety decision, sets no examination schedule, makes no remediation claim and does no billing automation.

What is included

  • A service-date record for each case: the source document, the current booking, the owner, the permitted contact route and the stop rules.
  • Service reminders: messages about an existing appointment, service or renewal, 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.
  • Marketing and reactivation: where your customers have given the permission the law requires and your team has approved the scheme, marketing messages and reactivation are in scope as a second line. It is set up, approved and stopped separately from service reminders.
  • Consent and opt-outs: Durward receives the consent your customers give and any opt-out, and stores them in the record agreed in the scheme. Your team approves the consent wording. A request to stop ends every message from your business to that customer through this workflow, and the stop is recorded.
  • Sender and stop: each message names your business as the sender and says how to stop further messages.
  • Replies: a reply that asks to book, move or cancel is answered inside the approved wording, or handed to a named person with the case attached.
  • Calendar entries: Durward can create, change or remove an entry in your booking calendar where your platform's API supports it and the scope has been verified.
  • A pilot on one record group, with the measures agreed before it starts.
  • A written scope that names what is set up, which later changes are covered and what is quoted separately. Fees for this service are scoped individually.

What is not included

  • An automatic safety decision. A service date prompts a review and does not show that work is needed or that anything is unsafe.
  • An examination schedule. Which interval applies to an asset is for your qualified people and your own scheme, and this page states none.
  • A remediation claim. A finding or a quotation is a record to follow up, not a statement that work is required.
  • Billing automation. Invoices, credit control and payment chasing are outside this service.
  • Discounts, price changes or negotiation of a remedial quotation. These stay with your team.
  • 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 message arrives, a customer replies or a person responds.
  • Any promise of bookings, renewals or revenue.
  • A legal view on contact permission, marketing or how records are kept. 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

A message goes out only when the record gives a reason to send it and the scheme allows it.

Eligible service facts

A case is eligible when your own record shows a service date, a contract or an open quotation, and the document it came from. If the date or its source is missing, the first job is to repair the record, not to infer a date. A date on file does not show that work is needed or that anything is unsafe.

Current booking checks

Before any message, the workflow looks for a job, visit or booking already against that date, a recent contact and an open dispute. A case with any of these leaves the queue and stays with its owner.

Remedial quotes

An open quotation after an inspection or visit is followed up only from what the record says, such as the date sent and the status. The message asks whether the customer wants to go ahead. The quote owner decides price, scope and any technical question, and the message carries no claim that work is required.

Approved communication

The scheme sets the record group, the wording, the frequency and the channels agreed in the scope and available on your platform, which can include SMS, WhatsApp and email, and nothing is assumed. Service reminders and marketing or reactivation are two separate lines in the scheme, each with its own wording, its own approval and its own stop rule. Which line a message belongs on is decided in the scheme, with qualified advice where the question matters.

Reply to booking or task

A reply that asks to book, move or cancel is handled inside the approved wording. Where your platform's API supports it and the scope has been verified, Durward can create, change or remove the calendar entry. Otherwise it offers your booking link or passes a task to a named person. Where an assistant answers a reply, it says that it is automated.

How a scheme is set up and tested

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

  1. Choose one record group

    You supply a focused export of service dates and open quotations for one defined group, with the source document, the owner and any booking for each case.

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

  2. Write the scheme

    Your team and we write who may be contacted, the channels, the wording, the frequency and the stop rules. Service reminders and marketing or reactivation get separate sections, approved separately.

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

  3. Set up consent and opt-outs

    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.

  4. Agree the reply and calendar rules

    We check what your platform's API supports and which scope has been verified. We agree which calendar changes Durward may make and which go to a named person.

    Buyer receives: A reply rule and a calendar rule, each tested against your platform.

  5. Test before any customer is contacted

    On test records we run a reminder, an opt-out, a reply that asks to book, a clash and a message that must be held. 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 record group. Your team reads the measures agreed beforehand, such as messages sent, bookings and tasks that followed, opt-outs, held cases and corrections, against how the same cases were handled before. 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 service date with no booking against it

The record shows a service due, and no job, visit or booking is recorded for it.

Trigger
The due date reaches the point the scheme names for a reminder.
Systems or sources
Your service or asset record, your booking platform and the consent and opt-out record.
What Durward does
Check again that nothing is booked and that the customer has not opted out. Send the approved reminder on an agreed channel, with a way to book or reply, and log the send.
Human checkpoint
Your team approved the wording and the stop rules. A named person owns every reply that is not a plain booking request.
Exception route
A booking found, an opt-out, a dispute or a missing contact route stops the reminder and leaves the case with a person, with the reason.
Success measure
How many reminders were sent, how many led to a booking or a task and how many were stopped, and why, reviewed by your team.

A remedial quotation with no recorded outcome

A quotation sent after an inspection has no accepted, declined or expired status in your records.

Trigger
The quotation has no outcome by the point the scheme names.
Systems or sources
Your quotation record, the inspection or visit record it came from and the contact record.
What Durward does
Check that the quotation is still open and that nobody is already in touch. Send the approved message that asks whether the customer wants to go ahead, and pass any reply to the quote owner with the quotation attached.
Human checkpoint
The quote owner decides price, scope and any technical question. Durward states only what is on the record.
Exception route
A disputed, withdrawn or superseded quotation, or a live conversation, leaves the queue. The message carries no safety conclusion and no claim that work is needed.
Success measure
Which quotations reached an outcome after the message, which went to the owner and which were excluded, reviewed by your team.

A reply that asks to book or move

A customer answers a reminder and asks to book, move or cancel.

Trigger
A reply arrives on a channel your team has switched on.
Systems or sources
Your booking platform and its calendar, reached through the platform's API where your scope allows.
What Durward does
Where your platform's API supports it and the scope has been verified, create, change or remove the calendar entry and confirm it to the customer. Where it does not, offer your booking link or pass the request to a named person.
Human checkpoint
Your team owns the diary and the rules for what may be changed without a person. An assistant that answers says that it is automated.
Exception route
A request the platform cannot take, a clash or an unclear reply goes to a named person, and the assistant assumes no booking has been made.
Success measure
How many replies became a booking, a change or a task, and how many calendar changes a person corrected, reviewed by your team.

A marketing or reactivation message, where permission exists

A customer who has not booked for some time and has given your business permission to receive marketing.

Trigger
Your team starts a marketing or reactivation scheme, kept separate from the service reminders.
Systems or sources
The consent record, the opt-out record and your customer list.
What Durward does
Check the customer's permission record and opt-out status before each message. Send only the wording your team approved for this line, and record any reply, consent or opt-out.
Human checkpoint
Your team approves the scheme for this line, chooses the audience and takes qualified advice on whether the permission it holds covers the message.
Exception route
A customer with no recorded permission, or with an opt-out, is left out. This page does not say whether a permission is enough. That is for you and a qualified adviser.
Success measure
How many messages were sent, how many opt-outs followed and how many replies reached a person, reviewed by your team.

Human ownership, and who does what

Durward sends inside the scheme your team has approved. Anything the scheme does not cover reaches a named person.

Durward prepares

  • The scheme, with service reminders and marketing or reactivation in separate sections, for your approval.
  • The consent and opt-out record design.
  • The reply rule and the calendar rule, checked against what your platform's API supports.
  • 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 diary, and the decision on which calendar changes need a person.
  • Every technical, safety and pricing decision, and every remedial quotation.
  • You can ask for a copy of your customer lists, consent and opt-out records 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 field-service, booking or CRM platform already sends service and renewal reminders. A feature you already pay for is recommended where it does the job.

This service adds value when

  • Your records hold genuine service dates or open remedial quotations, and a person can say who owns each one.
  • Your platform records the dates but nothing reaches the customer, or replies land with nobody.
  • You can name a person to take replies and exceptions, and your team is content to approve a written scheme.

Use what you already have when

  • Your platform already sends the reminders and someone owns the result. Switch the feature on and stop there.
  • Your records do not show a genuine date or a clear quotation status. Repairing the record comes first.
  • Nobody can be named to take a reply or an exception.
  • The aim is a bulk message to a whole list with no service or quotation fact behind it.

Bring one service date and one open quotation

Tell us which platform holds your service dates, which channels you use and who takes replies. We will say plainly if a feature you already have covers it.