If they say this,
say that.

Most replies fall into a handful of shapes. Only the detail should ever be new work. Find what they said, take the play, change the one specific thing.

Built from 01-library/channels/linkedin-plays-library.md · people and drafts that name real people stay private, never on this page

The lookup

They said	They are	Play
A 👍, or "thanks for connecting"	Unknown. No signal at all	P1 the qualifier
"Yes, and our opens are sliding"	A client	P2 the trade, or the free hour
"Yes, but our list is small"	Small, but still useful	P2 the trade
"Not me, but I advise people who do"	A channel	P3 the referral brief
"Who should I introduce you to?"	A referrer	P3 + P4
Generous, well connected, small list	A connector	P4 the SOS gift
Sits above a portfolio or client base	VC, accelerator, agency	P5 the perk stack
"Not there yet, but this matters"	Timing, not rejection	P7 the not-yet
"I'll look at this at the weekend"	Intent plus a date	P8 the dated defer
Out of office, or Open To Work	Nobody read it	P0 drop
Nothing, or another 👍	Nothing yet	Leave it. Cost was one message
added"Sorry, I'm in marketing, not for me"	Knows people who send	P3 + P4. P6 only for a professional referrer, and last
added"How do I get commission?"	Asking outright	P6, both options plainly
added"If you ever need anything, ask me"	Generous	P9 bank the goodwill
added"Let's do something together"	Serves senders	P10 the collab yes
added"Yes, let's talk"	Ready	P11 booking
addedThey asked a real email question	Curious, maybe a buyer	Answer from the Email Almanac, then route by this table
addedThey opened with their own credentials	Status, not need	P2 the trade, take the credential seriously
addedThey commented on the octopus	Warm	The sign-off, with the Delphi image
addedA competitor, warmly	A peer	P12 the competitor peer
addedA directory, hub or publication	A listing or media target	P13 the media or listing target
addedA public comment under a post	Everyone reading	P14 the public comment reply
addedA commenter who sells what YT cannot endorse	A seller	P15, in public stay inside your own argument
addedThey pitched their own thing	A seller	P5 if they serve senders, otherwise P0

Rows tagged added came from the reply desk and the night crawl (RME-95).

The plays

Reusable message patterns. Match the tags to the situation, grab the play, personalise the one specific detail. The point is that most replies fall into a handful of shapes, so only the detail should be new work.

Tag vocabulary

Group	Tags
What they sent	`#reply-defer` `#reply-notyet` `#reply-thumbsup` `#reply-brushoff` `#reply-broadcast` `#reply-open-question` `#reply-autoresponder` `#reply-referral-offer` `#reply-none`
What they are	`#role-sender` `#role-connector` `#role-referrer` `#role-agency` `#role-vc` `#role-nonprofit` `#role-media` `#role-jobseeker`
List size	`#size-tiny` `#size-small` `#size-right` `#size-unknown`
Sector	`#sector-retail` `#sector-nonprofit` `#sector-healthcare` `#sector-education` `#sector-events` `#sector-saas`
Outcome aimed at	`#aim-sale` `#aim-partner` `#aim-referral` `#aim-call` `#aim-relationship` `#aim-drop`

P1 · The qualifier

#reply-thumbsup #reply-brushoff #size-unknown #aim-sale

Use when they gave you almost nothing (a 👍, a "thanks for connecting") and you cannot tell if they even have a list. Never send a menu of options to a low-signal reply. Five asks in one message is the general approach the handoff doc shows losing 4 to 1, and the options are different ladders anyway.

One question, easy out, one line proving you read their profile.

Thanks {Name} 🙂
Quick one so I am not guessing: does {their org} email a list at all? And if it does, have the opens been drifting down?
That is the bit I fix. If it is not a thing for you, no problem at all, and {genuine one-liner about their content}.

Routing table for the answer

They say	They are	Next play
Yes, and opens are sliding	Client	P2 or the free hour
Yes, but it is small	Small	P2
No, but I advise orgs that do	Channel	P3
Nothing, or another 👍	Nothing yet	Leave it, cost was one message

P2 · The trade

#size-tiny #size-small #role-media #role-sender #aim-relationship #aim-sale

Use when their list is small enough that a paid clean is not the point, but they have expertise, an audience, or a door worth opening. A free clean traded for their honest opinion. A pure gift from a stranger creates obligation. A trade respects their standing and gives them a reason to engage.

Split the offer and the ask into separate paragraphs, and answer the four unspoken objections: what they send, what comes back, how much work it is, what happens to their data.

So, a trade rather than a pitch.
You send a CSV straight out of your {platform}. Any extra columns ride along untouched, and you get the same file back with a verdict on every address: Keep, Monitor or Suppress, the reason behind it, and what to do about it. Encrypted, deleted after 60 days, never resold. Free, and it is small enough that it will not take long.
What I would want back is your honest read on the report. Not on me, on the output. Would that actually help a {their kind of} marketer decide what to send, or is it noise dressed up as insight? You have spent {N} years on that side of the table and I would rather hear it straight than keep guessing.
And if the list comes back clean, that is a good answer too and you will know.

Guardrail: ask for a private opinion, never a public review. The fix plan is explicit: "the review ask stays conditional or the gift stops being a gift."

P3 · The referral brief

#reply-referral-offer #role-referrer #role-connector #aim-referral

Use when they say no for themselves but offer to refer, or ask who to introduce you to. Always carry the size filter. The documented failure of the campaigns is a pipeline of prospects roughly 30 times too small, and a referral partner with no brief will reproduce it exactly.

Name two concrete groups, never "anyone who does email".

Useful introductions would be people running events, summits or memberships, and marketing or CRM leads at companies of roughly 50 to 500 staff. That is where lists get big enough for this to actually matter.

Pair with P4. Add the 15% only where it fits (see below).

P4 · The SOS gift

#role-connector #role-referrer #aim-relationship #aim-referral

Use when someone is generous, well connected, or their own audience is too small to buy. A connector's currency is having something good to hand people, and this costs nothing until someone uses it.

And something you can hand out straight away: I run a free SOS hotline. Anyone whose email has suddenly stopped landing can ask me and get a real answer, no charge and no pitch. reviewmyemails.com/sos. Send people whenever it is useful, it exists for exactly that.

Doubles as the honest boundary: spam placement is often SPF, DMARC or a blocklist entry rather than the list, and saying so prevents selling a clean nobody needs.

P5 · The perk stack

#role-vc #role-agency #aim-partner

Use when they sit above a portfolio, a cohort or a client base rather than owning a list themselves. They have no stack to replace. What they have is a set of companies who need one.

Ask to be the deliverability slot, and offer a free clean of their own list as proof rather than as a pitch.

Is there a deliverability slot in the {accelerator / agency} stack? If there is not one you use consistently or trust, I would like to be it.

Guardrail: a cohort-wide free perk breaks the five-free-cleans-a-week cap. Agree the number before offering.

P6 · The 15%

#role-referrer #aim-referral

Mention it last or not at all. With a professional referrer it gives them upside and is honest. With someone being generous unprompted it cheapens the offer, and P4 already carries the reciprocity.

If an introduction ever turns into paid work, I pay 15%. Not why I am asking, but you should know it is there.

P7 · The not-yet

#reply-notyet #size-tiny #aim-relationship

Use when they say some version of "not there yet, but this matters". That is a timing objection, not a rejection, and the worst possible response is to argue. Push here and you convert a warm door into a closed one.

Three moves, no ask at all:

Accept it completely and say you prefer the honesty.
Give one piece of timing advice they can file. The genuinely useful one: check a list before the first real send on a new domain, not after. Reputation damage is slow to do and slow to undo, so the cheap version always happens early.
Give one thing of value inside their own expertise, not yours. This is what separates a peer from a vendor. It requires actually reading what they do.

Thanks {Name}, and "not there yet" is a genuinely good answer. I would rather hear that than have someone pretend. 🙂
One thing worth filing for when you are: {the timing advice}. Nothing for you to act on now.
Separately, and only because it sits squarely in your world rather than mine: {something real from their field}.

Guardrail: the gift in step 3 must be verified at a primary or professional source. Handing a wrong fact to an expert in their own field is worse than sending nothing.

P8 · The dated defer

#reply-defer #aim-relationship

Use when they say some version of "I will look at this at the weekend / next week". That is intent plus a timeframe, which is different from a maybe and very different from P7's "not there yet". The trap is answering it with more pitch.

Two moves:

Give them the one thing to look at. Usually they have said they will look without having been given anything specific, so a single link does more than another paragraph of explanation.
Pre-authorise the no. Most people who defer and then find it is not relevant go quiet, because saying no feels rude. Removing that friction converts silence into an honest answer, which is worth more.

Perfect, no rush at all. 🙂
If it helps, {one link} walks through what you actually get back, which is probably quicker than me explaining it.
And for what it is worth, size is not really the thing. A thousand addresses that have sat for two years cause the same trouble as a hundred thousand, it just costs less to fix.

Then log the date. A defer with a stated timeframe is the easiest kind of lead to lose, because nothing arrives to remind you. One light nudge a couple of days after their date, then leave it.

Snippet · The episodic close

#size-tiny #aim-relationship #aim-referral · bolts onto P2, P7 or P8

For anyone whose list will not produce a meaningful invoice today. Turns "not a customer yet" into "remembers you exist" without ever telling them they are not the target.

Most people only need me twice: when something breaks, or when a list has sat long enough to need a clean. It is not a subscription you forget you are paying for.
So the useful thing might just be knowing I exist for when it does come up, for you or for someone you work with.

Why it works: it reframes occasional use as a benefit against subscription validators, and "for you or for someone you work with" makes the referral ask implicit.

Never tell anyone their list is too small. Corrected 2026-08-28 on YT's instruction. It is insulting, it is factually wrong, and it costs the referral and the review. A thousand stale addresses cause the same trouble as a hundred thousand, they just cost less to fix, and anyone sending outreach, a newsletter or even invoices arrives at the same problem. Who you help and who you hunt are different questions. The 50 to 500 staff filter belongs in Sales Navigator targeting, where it decides where outreach effort goes. It has no place in a conversation with someone who already came to you.

The invoice angle is underused. Nobody thinks of transactional mail as a list, and unpaid invoices sitting in spam is a sharper stake than a newsletter's open rate.

Known weakness, decided 2026-08-27: occasional-use products have poor recall, so awareness alone does not survive a twelve-month gap with nothing to remind them. The real answer is being findable at the moment of need, which the almanac and the SOS hotline already do. Wiring those to the tell-a-friend motion beats building another page. Do not build a new referral or awareness landing page: /partners exists and is linked from contact, /for-agencies exists and is orphaned. A third would be the third.

No decay statistic in this snippet. The 25 to 26 percent figure is on the Do Not Use list in STATS-citable.md.

P0 · Drop

#reply-autoresponder #role-jobseeker #size-tiny #aim-drop

Autoresponders mean no human read anything. Job seekers are not buyers, and Open To Work is already set to 0 in Ulinc for that reason. Stop the sequence rather than spending four more follow-ups on it.

Snippet · The sign-off

#aim-relationship #aim-referral · closes every LinkedIn message

YT's signature is - YT 💌🐙. Confirmed 2026-08-30. Use it as the default close on LinkedIn messages unless a specific message calls for something else.

Where the conversation is warm enough to ask for recall, the octopus line goes immediately above it:

If you ever hear someone say their email has gone weird, remember the octopus.
- YT 💌🐙

This belongs in a DM, not on a landing page. Decided 2026-08-29: telling someone to remember you is a thing you say to a person. From a webpage it is strange. In a message it is the last line they read, and it only lands because they have just seen the octopus on the profile. The page carries 💌🐙 beside her name instead, and nothing more.

Snippet · The money argument

#aim-sale · use once a prospect accepts the list is the problem

Added 2026-08-29. Every other argument in the kit is a fear argument: your list is worse than you think. This is the only one a finance director forwards.

You stop paying to mail the void. A cleaned list often drops a client a whole plan size with their provider, sometimes two or three. What they pay me two or three times a year is usually less than what that saves them annually.

Keep the hedges. "Often" and "usually", never a guaranteed saving. A savings claim is the one thing a client will actually measure.

Snippet · The pre-check

#size-unknown #aim-sale · removes the risk of buying blind

I can pre-check first and tell you roughly what share of the list looks risky. If it is tiny, do not buy anything.

Pairs with "sometimes nothing is wrong". Same promise, made before the money instead of after, which is what makes it credible.

Standing rules for every play

Capital I. No em dashes. Her voice, first person, not the company's.
No spam-trap claims, no inbox guarantees, never name the validation vendor, spell out Review My Emails.
Statistics: only from docs/content-engine/STATS-citable.md. The 25% list-decay figure is banned, it is unsourced-by-circulation. Approved: Google reserves the right to delete accounts unused for two years, and BLS has 22% of workers in their job a year or less.
Personalisation must come from something they said themselves. A reshared post tells you what someone said about a thing, not what the thing is. Verify at the publisher or use something they stated directly. This has already gone wrong twice on one line.
Nothing sends without YT's go on that specific message.

Expansion, 2026-09-23 (RME-95): built around YT's plays, not over them

Everything below adds to the plays above. Where the two ever disagree, YT's section wins.

X1 · Where each kind of reply goes

The reply desk (RME-70) sorts every unanswered thread into one play. This is how the reply shapes seen in the 2026-09-17 export map to YT's lookup.

They said	Play
A 👍, "thanks for connecting", "sounds interesting", a short polite no with nothing else	P1 the qualifier
"Not me, I'm in marketing" / "not relevant" but they clearly know people who send	P3 the referral brief, plus P4 the SOS gift. P6 only if they are a professional referrer, and last
"Who should I introduce you to?"	P3 + P4
"Yes, our opens are sliding" / "send me more info" / "let's talk"	P2 the trade, or the pre-check snippet, or the Calendly link if they asked for a call
Agency, fractional CMO, accelerator, VC	P5 the perk stack
"Not there yet"	P7 the not-yet
"I'll look at it this weekend" (then silence)	P8 the dated defer, then one light nudge after their date
They asked a real email question	Answer it from the Email Almanac (cite the question), then route by the lookup
They commented on the octopus	Sign-off snippet with the Delphi image, then route by the lookup
They pitched their own thing at YT	P5 if they serve senders, otherwise P0
Autoresponder, Open To Work	P0 drop

Correction learned the hard way: the first desk batch (RME-70) led most brush-offs with the 15%. That breaks P6 ("mention it last, or not at all"). The desk is re-drafted by play (RME-95).

X2 · Snippet · The slow-reply opener (bolts onto any play)

For a thread that has waited about 10 days or more. One honest line first, then the play. The reason is true: YT was building the app. Never invent one. YT picked B as the default and wants A and C tested (00-inbox/decisions/2026-09-23-linkedin-slow-reply-opener.md).

A · "Sorry for the slow reply. I have been heads down getting the Review My Emails app live, and my inbox paid for it."
B (default) · "You caught me coming up for air. We just put the Review My Emails app live, and I am finally working through the messages I let pile up. Yours was one I wanted to answer properly."
C · "Honest version: I have been building our app and my LinkedIn inbox lost the fight. Sorry it took this long."

Mix by warmth (how warm they were sets how warm or plain we can be): warm leans B (50% B, 25% A, 25% C), medium is even (40% B, 30% A, 30% C), cold leans plain (50% C, 30% A, 20% B). Warm means interested, an open question, or a real back-and-forth. Medium means social. Cold means a brush-off, gone quiet, or their pitch.

X3 · Snippet · Endings, only where the play has no close of its own

YT: "can end in SOS or Email Almanac or something clever". Added as a PS, never as a second offer. The signature stays - YT 💌🐙.

E-SOS is P4. Use it only where the message has no other offer.
E-ALMANAC · "PS. This one might be useful for your world: {question} {link}". Pick the Almanac question that fits what they said. Starting set: 005.007.019 (valid but still dangerous), 021.002.001 (bigger lists), 005.011.003 (list decay).
E-CLEVER · a variant of YT's octopus recall line: "And if your emails ever start ghosting you, you know where to find me. And a very busy octopus 🐙", or "PS. Delphi says hi. She is the octopus, and she takes list cleaning far too seriously 🐙".

Mix: warm leans Almanac, medium even, cold leans clever.

X4 · The Ulinc sequence and what it actually got

The connection note, openers and follow-ups are in 01-library/channels/linkedin-outreach-sequences-playground.md (served as linkedin-outreach-sequences.html, client names removed). Measured from YT's 2026 sends in the 2026-09-17 export. "Replied" means any answer before the next template, so read it as attention, not buying intent.

Step	Message	Sent	Replied	Rate
0	Octopus connection note	1,006	243	24.2%
1	Migration / warmup ("grateful to connect")	280	101	36.1%
1	Blocklist recovery ("pleasure to connect")	116	28	24.1%
1	Money loss	142	29	20.4%
1	Validator gap	265	29	10.9%
1	"Reaching out to my network today"	502	39	7.8%
2	Soft nudge	550	123	22.4%
3	Offer plus two dates	291	32	11.0%
3	Testimonial follow-up	66	5	7.6%
4	Polite close plus SOS	147	32	21.8%

The specific painful situation wins again, 3 to 4x the generic opener. The leak was never the openers. It was the 825 threads where the other person answered and got nothing back.

X5 · How the plays learn

Weekly loop: YT exports LinkedIn. The desk (local only, ~/Documents/RME-private/linkedin-reply-desk/) drafts every unanswered thread by play. YT sends the ones she likes herself. The next export shows who wrote back.
What it counts: sent, replied back and outcome (referral, partner, SOS, signup, call) by play × variant, by opener × warmth and by ending × warmth. Only the counts are committed, to 03-analysis/reports/.
The winner becomes the default for its play or warmth level.
A new reply shape becomes a new play (P9 onward), written the same way: tags, use when, the words, the guardrail.
The method is written up in 01-library/channels/linkedin-reply-playbook.md.

X6 · Launch state

DMs are written as LIVE (reviewmyemails.com/get-started, and the free 1,000 are cleaned inside the account after signup). The WAITLIST line activates when YT logs the launch date, until then use LIVE. Once it does, a DM sent in the two-week pre-launch window swaps only its app CTA line for: "The Review My Emails app opens on [date]. Join the list now. When it opens, set up your account and your first 1,000 addresses are cleaned free." The softer CTA is "Rather talk it through first? Book a call." with calendly.com/reviewmyemails.

X7 · Where YT's plays and today's repo rules differ (for YT to settle, one at a time)

Nothing in YT's section was changed to resolve these. They are listed so nobody trips on them.

Statistics source. The plays say docs/content-engine/STATS-citable.md. This repo's rule (CLAUDE.md) is Email Almanac only. In this repo, the Almanac wins until YT reconciles the two.
P2's free clean and the five-free-cleans-a-week cap. Since 2026-09-23 the free 1,000 is the first clean inside an account, after signup with a card. Whether a hand-run free trade clean still exists is YT's call, per message.
"The free hour" (P1 routing) is defined in dnsbl-monitor/docs/content-engine/OUTREACH-FIX-PLAN.md, the RIGHT-SIZE offer: "I will give you an hour on a call for free, no charge and no pitch, and show you what is actually sitting in your list. If you want the full clean after that, we price it properly for the size you have." It sits in the other repo, so it is quoted here. The same plan caps free cleans at five a week, which is where P5's cap comes from.
Signature. For LinkedIn DMs it is - YT 💌🐙 (confirmed 2026-08-30). The BIBLE's "Yanna-Torry Aspraki" stays for everything else.
Partner pages (YT, 2026-09-23). /partner is the 15% referral and partner programme. /directory is the listings for agencies, freelancers and companies. YT believes /for-agencies no longer exists, but it still loads, which is logged as a gap. /partners also loads. Link /partner and /directory only.

Expansion, part 2 (RME-95 night crawl, 2026-09-23): the other reply systems, folded in

Three more reply systems were found outside git and are folded in here, so there is one library.

The eight shapes: a reply playbook drafted 2026-09-03 in YT's register, not dictated by her. It was never committed, and its Reply Router tool was built on it.
The agency response library: 33 rows the outreach agency used for booking, pricing and common questions.
The old RME-70 message library variants.

The plays below (P9 to P15) and the variants carry their source. Anything drafted rather than written by YT waits for her voice pass before it counts as hers.

X8 · New plays

P9 · Bank the goodwill

#reply-generous #role-connector #aim-relationship · from the eight shapes (#3)

Use when they say "if you ever need anything, ask me", or pitch their own help back. It is the polite reverse pitch. Do not counter-pitch. Match the generosity and take nothing.

That is kind of you, thank you 😊 Same offer back.
If email ever misbehaves for you or for a client, bounces creeping up, a domain suddenly landing in spam, send it over and I will tell you what is going on. No charge, I do it all the time.
And tell me what you are working on, so I know who to point your way when it comes up.

Pairs naturally with P4, since the SOS hotline is the concrete version of "same offer back".

P10 · The collab yes

#reply-collab #role-media #role-connector #aim-partner · from the eight shapes (#6)

Use when they say "let's do something together" and they serve senders or have an audience that sends.

Yes please 😊 I would much rather make something with someone than at them.
What I can bring: real anonymised examples of what actually kills a list, and a way of talking about deliverability that does not send an audience to sleep.
What did you have in mind? A live, a post swap, or something built for your audience?

Guardrail: the old agency library declined every collaboration ("We're not looking for any collaboration at the moment"). That contradicts the collaborate rung of the offer ladder, so it is retired. When a collaboration ask is really a pitch for their product, use P0 or the short no in X9.

P11 · Booking, the logistics

#reply-yes #aim-call · from the agency response library

Use when they said yes to a call and the only job left is getting a time in the calendar without friction. Each line does one thing.

They said yes: "Love that. I'd like to learn a bit more about your setup, see where I can help, and walk you through how we clean lists at the level most skip. Are you free {DAY} at {TIME} or {DAY} at {TIME}? Or pick whatever suits you here: calendly.com/reviewmyemails/30min"
Their intent is unclear, or they send their own calendar unprompted: "Happy to! Just so I make the most of our time, are you looking to sort out a specific issue (spam placement, a blocklisting, a messy or inherited list), or get a general read on how safe your list is to send to?"
No email address yet: "That works! What is your email address please? I will send you over a calendar invite. :)"
They propose another time: "Let me check... Okay yes, I think I can make that time work. :) What's your email address please so I can send you a calendar invite?"
Time and email confirmed: "Great, just sent a calendar invite for {TIME}. Looking forward to connecting!"
The slot got taken: "I apologise, I just went to book you in and someone snagged that spot first. I've booked you in at my next best time, {DATE} at {TIME}. If that doesn't suit, pick any time here: calendly.com/reviewmyemails/30min"
They send their calendar link: book it, then "Thanks {Name}! I went ahead and booked you in for {DATE} at {TIME} 🙂 Looking forward to connecting!"
Nudge 1 (1 to 2 days later): "Hi again! About that quick chat we mentioned, are you free sometime {DAY} or {DAY}?"
Nudge 2 (2 to 3 days after that): "No worries if you're no longer interested, but in case you're just busy, here's my calendar to make finding a time faster: calendly.com/reviewmyemails/30min" Then stop.

P12 · The competitor peer

#role-peer #aim-relationship · the "no play" case in PEOPLE-library, now a play

Use when a founder or employee of a validation or deliverability competitor engages warmly, usually in public. They are worth more friendly in public than as any sale.

Reply peer to peer. Say something true about the craft that lifts both of you, then stop. One example from 2026-09-23:

Two people in deliverability agreeing in public. Somebody screenshot it.

Guardrail: never compare, never say one is better or worse, never say we use a competitor in the background. No pitch, ever. Never put a competitor into a sequence.

P13 · The media or listing target

#role-media #aim-relationship · the other "no play" case in PEOPLE-library

Use when someone who runs a directory, a review hub, a podcast or a publication engages, especially one on the get-listed list.

Be generous and memorable in public. Say something sharp about their own subject. Never mention listings, submissions or the product in the thread. A warm introduction beats a cold submission form. Tell whoever owns get-listed that contact was made. If it is a collab post, the Review My Emails page may add one short, exact line after YT's.

P14 · The public comment reply

#public #aim-relationship · from the 15MIN chat and LNKDN/LINKEDIN-INTERACTION-RULES.md

Use when the reply is a public comment under a post, not a DM. The real audience is everyone else reading the thread. Reply as YT, not the page, since her reach is roughly 15 to 20 times the page's.

The four shapes:

They share an insight: validate the core truth, add one layer from practitioner experience, and at most offer to go deeper. Never pitch.
They ask a question: answer directly first, then explain. Facts from the Email Almanac only. If it is complex, point to a free tool or the Almanac, or suggest a DM.
They credit Review My Emails: acknowledge warmly and briefly, and add value instead of just saying thanks.
They are wrong: correct gently, with evidence rather than authority ("What we see in practice is..."). Never punch down on beginners.

Guardrail: the never-say list applies in full in public. No emojis in public comments. No links in the comment body. Never sell in a comment.

P15 · The commenter you cannot endorse

#public #role-seller #aim-drop · from the 15MIN chat

Use when the commenter sells something YT's name must not sit next to: cold outreach, list building, warmup tools.

In public: stay entirely inside your own argument. Do not mention what they do, do not validate it, and still say something worth reading. One example: "The uncomfortable part is that the fix is usually subtraction... Smaller list, more inbox."
In a DM: YT's call, since private is hers ("the dm in private i can say what i want"). Keep offers to her own terms.

Decided (YT, 2026-09-23): cold-outreach operators can partner ("they can, but only some"), and YT picks which ones go into the directory. So a partner offer to one goes in a private DM only, and a directory listing only on YT's yes. In public the rule above still holds.

X9 · Variants folded into existing plays

P1, the sorting question (eight shapes #1): "Thanks for accepting, {first name} 😊 Good to have you here. While you are on my radar, one nosy question. Do you send email to your own list, or are you more often the person other people ask about it? Both answers are interesting to me, for completely different reasons."
P1, "what is it you actually do" (eight shapes #4): "Fair question 😊 People hand me their email list and I tell them which addresses are safe to send to and which ones are quietly damaging their reputation, with the reason behind every single one. Not just does this address exist, but should you be mailing it at all. Are you sending to a list at the moment, or is email somebody else's problem where you are?"
P2, size and symptom (eight shapes #5, the one worth money): "Perfect, that is exactly my corner 😊 Two quick questions so I do not waste your time. Roughly how big is the list, and what is going wrong right now? Bounces, spam folder, or just a feeling that it has gone stale."
P6 when they ask outright (eight shapes #2). If they ask how the commission works, answering is not "leading with it", so give both options plainly: "Two ways, and you take whichever fits you. One, you send someone my way and you get 15% of what they spend. I do all the actual work, so you stay out of it. Two, you offer clean lists as your own service. You keep the client and the credit, and I do the cleaning quietly in the background." Link the partner page (see X7.5 for which URL).
P7, close and stop (YT picked, 2026-09-23, her own words from her September messages): "No worries, thank you for letting me know! If there is ever anything I can do for you, email related or not, let me know. Always nice to create actual connections here 💌🐙"
P7, "reach back out in a few months" (agency library): "Great! I'll circle back in {timeframe}." Then log the date, as in P8.
P8, the nudge after the date (old message library 5.4): one line that picks up exactly where they left off. Never "just checking in".
The Delphi / octopus variants of the sign-off:
Eight shapes #7, with the pronoun fixed to "she": "Hahaha the octopus is doing more selling than I am 😊 Genuinely nice to meet you. She is the mascot of an email company, which is a strange sentence to type out."
YT's own lines: "She is pretty happy to hear it", "It is a very busy octopus, I must say", "Straight from the coast of Rhodes!"
The Oracle of Delphi line, for anyone in foresight or strategy: "So glad Delphi caught your eye! She's named after the Oracle of Delphi, so she's practically a colleague of yours."
P3 + P4, the old brush-off variants, corrected for P6. The RME-70 variants 5.1-A, B and C opened with the 15%. The corrected order: the P3 brief first ("Useful introductions would be people running events, summits or memberships, and marketing or CRM leads at companies of roughly 50 to 500 staff"), then the P4 gift, then P6 last and only for a professional referrer. The originals are kept in 99-archive/2026-09-23-linkedin-message-library.md.

X10 · Common questions (from the agency library, cleaned)

They ask	Say
"How are you different?"	"Good question. Honestly, it comes down to what you walk away with. Most validators answer one thing: does this address exist. I go further and tell you whether each address is actually safe to send to, with a Keep, Monitor or Suppress verdict and the reason."
"What platform do you use?"	"We built our own. It's Review My Emails, and the app is live: reviewmyemails.com/get-started" (the old line said "going SaaS in the coming weeks", which is now out of date)
"Do you have examples?"	"Here's a demo report so you can see exactly what comes back: insights.reviewmyemails.com/demo-clean"
"What do you do? Can you send more info?"	The P1 "what is it you actually do" variant, or reviewmyemails.com/hello
"Why did you connect with me?"	"Thanks for asking! I reached out because {the real reason from their profile or post}." Never invent one
"I already have this"	"Good, that puts you ahead of most! The only thing is, most cleaners only confirm an address exists, not whether it's safe to send to." The old line's spam-trap clause is removed (no spam-trap claims on marketing surfaces)
"Have you helped coaches and consultants?"	"Yes, coaches and consultants are a big part of who I help, both directly and through their clients." No invented numbers
"How much do you charge?"	See X11.2. With a list size, quote from the pricing table. Without one, share the pricing PDF once YT approves it
"Do you have lists of investors?" / lookalike lists	"No, I do not sell data. I validate the emails people send to us." Do not recommend a third-party data tool
Their pitch for their own product	"Thanks for the info! Not interested at the moment. Wishing you the best." (or P0)
A chat request that is not about our services	"Thanks so much for the invitation, but honestly I don't have time for calls with all the lovely people I meet here. I hope you understand."

X11 · Folded-in rules, and what is still open

Tag every contact with its play. The old router tagged each Ulinc contact with the message used (L1 to L8), so the tag later showed which message booked the call with nothing logged by hand. Keep the habit with play IDs instead: tag the contact P3, P11-yes and so on. The weekly export then reports by play.
Pricing (YT, 2026-09-23). "if they ask for specific size, if not we have some pdf with pricing etc, as long as we double check them or confirm they can be used then i can share it in the chat". So when they give a list size, quote the price for that size from the pricing table (from $0.008 per email down to $0.0026 at volume). When they don't, share the pricing PDF in the chat, but only a version YT has checked and approved. Until then, ask for the rough list size. The old agency line ("I can't give you a quote without understanding your situation") is retired.
The tag #reply-credential (from PEOPLE-library): they open with their own credentials ("I used to run a million-record database"). Read it as a status move, not a need. Take the credential seriously and never explain the basics. The P2 trade lands better on them than on almost anyone, and P4 answers "what can you do for me".
Segment to offer (old message library): Heads of and Directors at real companies go to clean. Agencies, fractional CMOs and consultants go to partner or white label. Owners and solo founders go to referral or partner, never a doomed clean pitch. A live spam, blocklist or DNS problem goes to SOS.
Never in a DM (old message library): no em dashes, no semicolons, "Review My Emails" spelled out, never the vendor name, never a sibling brand, never a client or testimonial name, never YT's personal address, never a label count, no "no card", no inbox promises. YT sends every message herself.
The agency library's "No, free app trial" row pointed at a Slack message nobody here can see. It is dropped.

X12 · Candidate plays (shapes seen on the desk, no play yet)

Found while re-drafting the 2026-09-17 export by play. Each needs YT's words before it becomes a play.

"Your pitch ignored my own posts." They called out that the message was generic. The only right move is a short, real apology, with no ask.
"Is it launched yet?" You told them a launch was coming, and now it is live. A one-line "it's here", plus the LIVE link.
A peer asks YT a strategy question about her own market. Answer as a peer. It is not a sales moment.
"Where are you based?" as the whole reply. A friendly one-line answer, then route by the lookup.

X13 · Open notes for YT

P3's size line ("That is where lists get big enough for this to actually matter") sits awkwardly with the episodic-close rule ("Never tell anyone their list is too small"). P3 is a brief to a referrer about who to introduce, not a verdict on their own list, so it may be fine. YT's call, and neither is changed.
P7 close and stop: settled. YT picked her own line (see X9).
Sign-off emoji: settled. It is the octopus, - YT 💌🐙, not the squid that crept into some September messages.
"Polite no" is a role question, not a text question (learned re-drafting 261 threads). The same "no thanks" goes to P3 + P4 when the sender works near email (marketing, sales, growth, comms, ecommerce, agencies, fractional CMOs, consultants, publishers, podcast hosts), and to P7 close and stop when their work has no link to email or the reply was irritated. On the 2026-09-17 desk that split was 37 to 35. The first weekly export after sending should compare the two, so the split gets tested instead of assumed.
P3 + P4 may be too long after a one-line no. The brief plus the SOS paragraph runs to about 90 words. A short variant is a candidate for YT's words.
"Free, no signup" is for the free tools only (YT, 2026-09-23). Email capture on the tools is for bot reduction. Some webinar pages offer a clean with no account (they pay and send the list by email). Everything else is the self-serve app, where the free 1,000 are cleaned inside the account after signup. So no DM offers a "free, no signup" clean.

X14 · The PDFs a play sends

YT's sales PDFs (value, SOS, pricing, partner) are catalogued in 01-library/channels/linkedin-sales-pdfs.md, with each one's newest version, its clashes and which play sends it. The PDFs stay private. Only a version YT has checked goes out in a DM.

Generated from 01-library/channels/linkedin-plays-library.md by build-say-this.py · edit the markdown, not this page

If they say this,say that.