The list nobody has written to
The request arrives as a number. The sales team wants more meetings next quarter and asks marketing what a new channel would cost: a paid campaign, a purchased list, an outbound agency, a second trade show. Every one of those buys strangers. The CRM already holds every person who has enquired, taken a quote, sat through a demo or bought something. In most of the databases we open, the larger share of those records has had nothing logged against it for more than a year.
Those contacts cost money once. Somebody paid for the ad that produced the enquiry or the hours that went into the quote, and the company has carried the record ever since without asking anything of it. A person who enquired eighteen months ago knows the company's name and has a reason on file for getting in touch. Nobody a new campaign reaches has either.
So when a client asks for more meetings, we count what is already in the database and write to it. The new channel waits. The meetings that come out of the list are the cheapest the company will book this year, and what those contacts say about the offer decides whether the channel is worth buying at all.
Reading twelve months of silence
The count starts with a date field. Every CRM records a last activity, an email logged, a call, a deal moving stage or somebody opening the record. We pull every contact where that date is more than twelve months old. The work runs from that figure because nobody can argue with a date, and it is usually a larger share of the database than anyone expected.
Sorting comes next, by the last activity, because that is what the first message has to refer to. An enquiry that never got a reply, a quote that expired, a customer who bought once and never came back, a name collected at an event. The message that suits one would be wrong for the rest. We build the sort inside the client's CRM as a saved view, so the same person can run it again.
A share of every list is dead before anything goes out. Addresses that bounced, contacts who unsubscribed, companies that no longer exist, records with no email address at all. Those come out first. The number left goes into the baseline as the count of dormant contacts, beside the count of meetings booked from the existing database in the last ninety days. The two together are the case for the work.
What the sequence says
The first message refers to the last real thing that happened. It names the quote that went out last spring or the job finished in the autumn, and asks whether that is still on the table. It comes from the person who dealt with the contact last time, or whoever would take the meeting now, with a booking link at the bottom. Nothing in it announces a campaign.
The second message, a week or so later, needs something new in it or it doesn't go. A price that changed, or a service the company did not offer when the contact last heard from it. Where there is nothing new, one line asks whether the timing is wrong. There is no third. Two messages over three weeks is the usual shape, and the client agrees the cap before the first one goes out.
Writing them takes longer than the build. The person whose name sits at the bottom reads every message and says whether they would send it by hand to someone they quoted a year ago. If the answer is no, we rewrite it or cut it. A list that took a year to go quiet can be lost in an afternoon by writing to it like a newsletter.
The sequence stops on any reply, on a booking and on an unsubscribe. A reply goes to a person and not back into the automation, because the contact has just done the thing the whole exercise exists to produce. A rule inside the system drops bounces and marks the record, so the next campaign skips that address.
Getting the reply onto a calendar
A booking link on its own is a link to one person's diary, which is fine for a company of three. Beyond that, we route on what the record already holds. A past customer books with whoever looks after their account, and an old enquiry with the salesperson who covers that territory. Anyone whose record says nothing useful lands with one named person working the list that week.
The scheduler reads real availability and offers only the hours the person keeps. It writes the meeting into the calendar and the CRM at the same time, so the deal moves stage without anyone typing. Where the contact does not turn up, the record moves to a no-show sequence with one message in it, and the slot opens again.
Replies that are not bookings matter most, and they are the ones that go missing. A contact who writes back to say the quote was too high has given the company more than a meeting would. The system logs the reply against the contact and puts a task in front of the record's owner the same morning. The scheduler handles the yes, and everything else goes to a person.
Why it runs before the ad budget
The tools are usually already paid for. A CRM with a last activity field and an email sender with a booking link are enough, and the writing is the only real work. A campaign to strangers has to buy the attention first and then earn the reply. The dormant list starts at the reply.
Meetings booked from the existing database is one of the five numbers we take before any build, and the fastest to move. The first message goes out on the day the client switches the sequence on, so the first meetings are in the calendar before anyone has signed off the quarter's ad budget.
The dormant contacts are also a test of the offer, because these are people who asked about it once and wanted it. If a plain message from a named person can't get a share of them to take a meeting, a campaign to strangers will get the same answer at a higher price. We would rather learn that from the list.
