The reason to get back in touch is already in your records
Your CRM, ERP and quoting tools hold quotes that were never followed up, accounts whose buying has changed and service dates that are coming round again. Each of those is a factual reason to speak to a customer. They tend to sit there because no one owns them and nothing says what to do next.
A general mailing to old contacts does not solve that. It cannot tell a real quote or service date from an old record with no usable background, which is why we do not treat a newsletter as recovery. We start from the event on the record and build the follow-up around it.
We look before anything is sent
The first job is to find out what your records can support. For each one we look at where it came from, who owns the relationship today, what has happened recently and how best to reach the customer. A quote, an order, a hire, a service date, an enquiry or a renewal counts as a reason to write. The age of a record on its own does not.
The records that pass are ranked by value, by how recent they are and by the relationship, without guessing at what the customer intends. Current opportunities and existing ownership of relationships are left intact. You then approve which records go forward and which are left out.
Only then does the agent send the message you approved. It follows up within the frequency you set and stops when someone asks, when it is unsure or when a person needs to take over.
One old quote, worked through
Take a quote like this. Q-18462 was sent on 03 August for £8,450. No activity was recorded after 08 August, and the quote expires on 02 September. The account has bought the same product category before and has an assigned branch manager.
Before anything happens, the workflow checks that the quote is not part of an active opportunity, that nobody has objected to it before and that no one has already acted on it within the agreed look-back period. A duplicate quote, or one already resolved, is designed to leave the queue and not to be contacted. The reason is designed to stay on the record.
This one passes. Before it expires, the agent asks whether delivery timing, availability or the requirement has changed, and sorts the reply. A positive, complicated or sensitive reply goes to the assigned branch manager through the permitted business contact route, with the full context. There is more on how this is set up on the quote follow-up page.
What a date or an old quote does not prove
Some reasons are stronger than others. HSE says a thorough-examination report for lifting equipment must include the next due date, and it describes examination intervals of 6 or 12 months for different equipment unless a competent person’s examination scheme sets another interval. A date like that is a real reason to prepare the next service conversation, and a stronger one than a CRM record that has simply gone quiet.
It is still only a reason to talk. A due inspection does not prove that remedial work is needed, and the system does not make safety or technical decisions. Your qualified team decides the operational action. In the same way, a change in spend or an ended hire does not prove that a customer is unhappy or has a new project.
What stays with you
Before anything goes live your team approves the records, the contact route, the message, the frequency and the rules for escalation. Any offer, commercial terms and negotiating position are yours to choose. The agent works inside those rules, and objections, judgement about the relationship and sensitive conversations stay with your people.
How we start
We start with one batch and leave the rest of the database alone. You give us a focused export of the relevant CRM, ERP, quote, order or service history, showing who owns each relationship now and what has happened recently. We profile a de-identified sample of fields, define the group worth recovering and decide whether the data can support a responsible test.
Before anything goes live you receive a written recommendation: proceed, repair the data first, or stop. With it come a map of how good the data is, a list of who to leave out and clear rules for who picks up replies. If the records can be used, one approved sequence runs on a small group, and we compare the replies, bookings, reopened opportunities and hand-overs with how those records are handled today.
Spotting the reason, following up and handing over are automated only once the record group and the sequence have worked. People keep the relationship and the commercial decisions.