Where the lead goes quiet
When a qualified lead goes quiet, the audit goes to the sequence. The wording gets reread and somebody asks whether the third message was one too many. We used to start there as well, because the sequence is the one part of the process that keeps a log, and a log is the only place an audit can begin.
The trace usually ends somewhere else. When we follow a quiet lead back step by step, the last thing the automation did to it was correct. The contact replied or booked, and the sequence stopped and moved the record to a qualified stage with a note on it. Then nothing happened to it until the following week, and what was supposed to happen in that gap was the handoff.
A handoff is the point where the record leaves a system that logs everything and enters a person's working day, which logs nothing. The salesperson got an email notification that landed in the inbox with everything else, or saw a stage change on a pipeline board they open on Friday afternoons. The contact, meanwhile, had been told that a person would be in touch. The sequence did its job and the lead went quiet inside the building.
Why nobody sees it break
A message that fails to send produces an error. Nothing comes back from a record nobody opens, because from the CRM's point of view it is exactly where it should be, sitting in the qualified stage, waiting. There is no alert for a lead that a person has not looked at, and none of the tools we build in ship with one, so the silence looks identical to a lead being worked.
Both teams read the same blank and reach different conclusions. Marketing marked the lead qualified and counts the job as finished, because qualified leads produced is the figure marketing is measured against. Sales opens a record with no call notes on it and reads the blank as a sign that the lead isn't ready or that marketing is still working it. Neither side is careless. They are looking at an empty field and each is filling it in with the reading that costs them the least.
The contact is the only person who knows. They said yes to a call and heard nothing. By the time anyone in the building notices, they have either bought from whoever answered first or decided the company was not serious about them. When the loss is recorded at all it goes down as a lead that went cold, which puts it back on marketing's side of the ledger and sends the audit back to the sequence. So the count of qualified leads and the count of first sales conversations almost never match, and in most teams we have sat with nobody has put the two numbers side by side.
What qualified has to mean
Before we build a notification we get marketing and sales into the same room and settle the single event that hands a lead over. The event is something the contact did. They booked a slot, or they answered the qualifying questions and asked for a call. A lead score crossing a threshold hands nothing to anyone, because no salesperson can act on a number that moved on a dashboard. The teams that hand over on a score are the ones where the handoff is most often ignored.
The event gets written down in the words of the salesperson who will receive it. If sales says a lead is only real once a budget figure is on the record, then the sequence asks for the budget before the stage changes, and marketing stops marking leads qualified without one. That argument is uncomfortable, because it usually shows that the two teams have been using the same word for two different things for years. It happens once. It is also the part of the build that does the most work.
We also settle who receives it, by name. A handoff addressed to the sales team goes to nobody. A round-robin rule works and so does a single named person. Whatever the rule is, it has to produce exactly one name every time it runs, and it has to say what happens on the day that person is off. The rule for absence is the one that gets forgotten, and it's the one that loses the lead on a Friday.
The notification and the clock behind it
The notification goes where the salesperson already looks, and for most of the people we build for that is a phone. A text message or a push from the CRM's mobile app carries the contact's name, the company, what they asked for and a link that opens the record. Email is the default in every CRM we have configured and it is the wrong channel for this job, because the notification lands in the inbox with everything else and gets read at the same pace. The salesperson chooses the channel. We hold them to it.
Everything the sequence learned goes onto the record before the notification fires. The source, the answers to the qualifying questions, the thread of messages and replies, and the wording the contact used when they said yes all sit on the record when it opens. A salesperson who finds only a name and a phone number starts the conversation from nothing, and the contact, who already answered three questions on a form, gets asked them again on the phone. That is the call that makes a company look like it doesn't talk to itself.
A clock starts the moment the notification goes out. If the record hasn't been opened within an agreed window, a second notification goes to the same person, and after a second window it goes to the next name on the rota or to that person's manager. The windows are set by sales, in hours they can defend, and we write them into the rule exactly as sales stated them. The escalation is unpopular the first time it fires. It fires less each month, because the thing it measures is the thing people start doing.
The contact is told what happens next. The message carries a name. It fires when the stage changes and says who will call and by when. The salesperson named in it writes it, the same way every message in the sequence is written by the person who signs it. A promise of a call within the hour is a commitment to be at the phone at the hour it was made, so the wording is theirs to set.
Nothing closes the task except a logged first contact, and the log is a field with a date in it, because a field can be counted and a note cannot. At the end of the month the number of leads marked qualified sits next to the number of first conversations logged, and the gap between them is the figure this whole build exists to shrink. Once a team can see that gap, it stops arguing about the sequence.
