Check the records before starting a follow-up sequence
Before anyone is contacted, each record should show where it came from, what is still open, who owns it, whether it is duplicated, which recorded event gives a reason to ask and which contact route your team has approved. This guide sets out those checks and a downloadable input schema. It is not a CRM migration, a clean-up of your whole database or legal advice, and it promises no result.
Record provenance
Start with where the records came from. A follow-up built on records nobody can trace is hard to stop and hard to explain.
- 01
Take one export for one purpose
Write the purpose in a sentence, such as unresolved quotes in one product range, and export only the fields that purpose needs. A whole-database export is harder to check and reaches further than the task requires.
- 02
Record the source system and the export date
Say which system each field came from and when the export was taken. Where two systems hold the same fact, say which one wins.
- 03
Keep a stable identifier on every row
Use the identifier from the source system, not a name. Without it a record cannot be traced back, corrected or excluded reliably.
- 04
Correct errors in the source, not in the copy
Treat the export as a copy and fix mistakes in your own system. Then the corrected data stays in your accounts, whichever tool or supplier you use next.
- 05
Decide what counts as current
Your team sets how recent an export must be for this batch. This guide gives no age limit. If an export is stale, take it again.
Current opportunity and owner
A record is a candidate only when the thing it describes is still open and a person answers for it.
- 01
Read the status from the source's own list
Open means no order, refusal, withdrawal or newer record is logged against it. Resolved and superseded records leave the batch, with the reason kept.
- 02
Look for a live conversation
Compare the latest logged call, email, visit or note with an activity limit your team chooses. Anything inside the limit belongs to its owner and is not put into a sequence.
- 03
Name an owner who can take a reply
Use a named person or role who is still in post and still holds the account. A team name or a colleague who has left is not an owner.
- 04
Let each owner look at their own rows
Ask owners to mark any record they would rather handle themselves. It is a quick check and can surface relationships the system does not show.
- 05
Hold records that have no owner
A record with no owner waits until someone is assigned. The first job is to repair the record, not to contact it.
Duplicates and missing fields
Duplicates and blanks lead to avoidable mistakes, such as two messages to one contact or a message to someone already excluded.
- 01
Choose a match key before you search
Use fields your records hold reliably, such as an account identifier with a normalised email address. Exact matches are straightforward. Near matches, such as similar names, need a person to decide.
- 02
Look beyond the export
A contact can appear once in the batch and again in a record outside it, such as an open enquiry or a live quote. Check the live records as well.
- 03
Contact one record and exclude the rest
Give related records a shared group identifier. The owner chooses which record is contacted, and the others are excluded with the reason duplicate.
- 04
Apply an exclusion to every copy
If one record is suppressed or has objected, the same person or organisation under another record is covered by that exclusion too.
- 05
Count blanks for each required column
Required here means the name, the contact route, the event date and the owner. If a missing value can be recovered from the source, repair it. If not, exclude the record as incomplete and do not fill the gap with a guess.
- 06
Mark duplicates, do not merge them in the check
The check flags duplicates. Merging or deleting is a separate change to your CRM, made by your team and checked on its own.
Factual trigger
A record needs a recorded reason to be contacted. The age of a record is not a reason.
- 01
Name the recorded event
A quote was sent, a stated expiry date has passed, a service date is recorded or a hire has ended. Each is a fact in the source system.
- 02
Take the date from the source
Do not estimate or infer a date. If the date is missing, repair the record from the source or exclude it as incomplete.
- 03
Do not treat inactivity as a trigger
A record being old or quiet says little about whether someone wants to hear from you, and nothing about whether you may contact them. A record whose only trigger is its age is excluded, with the reason kept.
- 04
Refer to the event in the message
A message that refers to the quote or the date is clearer than a general reminder. Your team approves the wording before anything is sent.
- 05
Keep a pointer to the evidence
Store a reference to the source record so a reviewer can open it and see the event for themselves.
Contact route and suppression
Having a phone number or an email address on file does not show that you may use it for this message. A person approves the route, group by group.
- 01
Approve the route for each record group
Your team names the group, the channel, the wording, the timing and the frequency. Nothing is inferred from the fact that a contact detail exists.
- 02
Write down the basis your team relies on
The rules can differ by channel and by who the recipient is, for example an individual, a sole trader or a company. Your team records its basis for each group and takes qualified advice where the answer matters. This guide does not decide it for you.
- 03
Check suppression and objection everywhere they are kept
That means the CRM, the email platform, any phone list and objections noted by an owner in free text. If a source cannot be reached, treat the batch as stopped until it can.
- 04
Check again just before sending
Suppressions can change between the export and the send. Check again immediately before any message goes out and keep the date of the check.
- 05
Make stopping easy to record
Anyone who objects or asks to stop is recorded where every system can see it, and the sequence stops for that record.
Proceed, repair or stop
Each record, and then the batch, gets one of three outcomes with a reason written down.
- 01
Proceed
The record passes every check above. It joins the approved record group and, if its owner agrees, the pilot.
- 02
Repair
There is a fixable gap, such as a missing date, an unassigned owner or an unresolved near-duplicate. The record goes to a named person, is corrected in the source and is tested again.
- 03
Stop for the record
The record is excluded with one reason: resolved, live conversation, owner request, duplicate, suppressed, no trigger, no owner, no approved route or incomplete. The reason stays on file.
- 04
Stop for the batch
If nobody can name the source, if a suppression source cannot be reached or if the same check fails across much of the batch, do not start. A batch that is mostly repairs is a data task first.
- 05
Use your existing system if it already does the job
If your CRM already produces a queue that an owner works, you may not need anything new. The records still deserve these checks before a sequence runs.
Pilot baseline
Before the first message, count what the batch looks like now, so you can tell afterwards what changed.
- 01
Count the export
Record how many records went in, how many were excluded under each reason, how many were repaired and how many proceed. Keep the counts with the dates.
- 02
Record how these records are handled today
Note who chases them now, how often and how quickly, taken from records and not from memory. The gaps are part of the baseline.
- 03
Start with a small group
Run the first sequence on a small group from the proceed list, agreed beforehand with the owners.
- 04
Set the stop rules before you start
A reply, an order, a refusal, a change of owner, a suppression flag or any doubt stops the sequence for that record and passes it to its owner.
- 05
Compare like with like
Compare replies, reopened quotes and how quickly an owner receives a reply against the baseline, counted the same way. A reply is not a sale, so count orders at the last step. The measurement guide covers the method.
Eight checks before the first message
Answer these in writing for the batch. The downloadable schema has a field and a test for most of them.
- 1.Is the purpose of the export written in one sentence, with only the fields it needs?
- 2.Can every record be traced to a source system and an export date?
- 3.Is each record still open, with no live conversation and a current named owner?
- 4.Have duplicates been grouped, with one record chosen for contact?
- 5.Does every record have a recorded event and an event date taken from the source?
- 6.Has your team approved the contact route for each group and recorded its own basis?
- 7.Have all suppression and objection sources been checked, with a second check planned just before sending?
- 8.Does every record have a proceed, repair or stop outcome with a reason, and has the baseline been counted?
Download the record-check schema (CSV) A plain spreadsheet file with a header and one line for each field, giving the group, whether it is required, the test, what to do if it fails and a de-identified example. Edit it freely; it opens in any spreadsheet program.
Continue with the next step
These pages cover what follows once the records have been checked.
Bring one export, gaps included
Send the field list from your CRM or quote system for one batch of records. We will say plainly whether the records look ready, what needs repairing first and whether a feature you already have covers the follow-up.