A quiet list is a list that got the wrong reason
When a sequence ends, most of the people on it have said nothing. The usual responses are both poor: drop them into the same sequence again next quarter, or write them off. Neither asks what silence after several touches tends to mean. The reader saw your name, understood the pitch, and found no reason to answer it that week.
That is different from a no. People who said no, or asked to be left alone, are out, and this play removes them before anything else happens. The ones who stayed silent were qualified once and their addresses worked. They do not need a reminder. They need a different reason.
So there is no "bumping this to the top of your inbox". The play reads what the first sequence argued, finds something true and recent about the company or the person, and writes one message built on that. One, not a second cadence.
What you get back
A table of the non-responders who survived the filter: the person, the angle the first sequence used, the fact found, its source link and date, the angle chosen and the draft. Rows where nothing true turned up have a flag and no draft. A second list shows everyone removed and why: replied, bounced, unsubscribed, or on your opt-out file.
On your approval the drafts sit in a separate campaign that is paused. Nothing is sent.
Variations worth knowing
Openers first. Someone who opened every email and never answered is the warmest silence on the list. Ask for them as the pilot group. Opens are an imprecise measure, so use them to sort, not to decide.
Drafts only. Take the file and send from your own inbox. For a short, senior list that is often the better route.
Not contacted yet. If the list has never been written to, one sourced opening line per person is the play to run. What comes back from either campaign is handled by sorting campaign replies.
Where this goes wrong
A reply the sequencer never saw. Someone who answered by phone, on LinkedIn or to a colleague still looks silent. Check the list against your inbox and your CRM before you approve it.
A campaign too large to read in one go. lemlist returns a capped number of leads per read, newest first, with no paging. For a large campaign, work from an export.
Going again too soon. A message sent straight after the last step is one more touch of the same sequence, whatever it says. Leave a gap, and let the fact you found set the timing.
A lead lemlist treats as a duplicate. lemlist can refuse someone it already holds. Refusals come back row by row and are reported, never forced.
A variable that cannot be corrected. lemlist sets a custom variable once, when the lead is added. Fix the drafts in the review, before the load.
