creatop-gtm/apollo-operator / plugins/apollo-operator/skills/re-engagement
re-engagement
VerifiedGo back to leads who finished a sequence and never replied. Covers when it is safe to re-approach (60-90 days), the permanent exclusions, re-verification, and bringing a genuinely new angle rather than another follow-up. Use for quarterly re-engagement passes or when a finished list looks dead.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.4 KB |
| connector-only.md | markdown | 8.4 KB |
connector-only.md
View on GitHub# Connector-only instructions
## Operating rules
Apollo Operator is an open-source headless GTM toolkit by Creatop, a B2B outbound agency. These instructions work in a chat without a terminal. Do not run or print shell commands, read credential files, request API keys, or imply access to local disk. Treat brief.md and profile.yaml as logical artifacts: use attachments or return structured text, and only claim a saved file after a successful save.
Use the connected Apollo tools when available, with the exact names the connection lists; the old v2 router is retired. A tool marked destructiveHint spends credits or changes live state. Confirm account identity through a discovered profile read. Offer Apollo's own available skills first where they fit. If discovery advertises a relevant apollo_agent_* action, name it alongside this method and let the operator choose. Before dispatch, explain its effects, whether it may spend credits or create records, establish cost and balance, and wait for an explicit yes. Never run an AI action unattended. Apply the same deliverability, list-quality, suppression, and copy-review checks to its output before sending.
Start with at most 25 search records. Keep each review batch within 100 total record entries, including repeated pages and duplicates. Before collection reads, require an enforceable limit, pagination, filters, or a count-only alternative. Skip an unbounded list/index call and explain the corresponding Apollo interface check. Never continue an unbounded pull by resetting the cap. A sample is not a complete saved list or suppression pass. If an action unexpectedly exceeds its requested bound, stop and disclose the overrun.
Before any paid or write action, state its effect, named credit pool, current cost, and remaining balance, then wait for explicit approval. Unknown cost or balance blocks spending. Enrollment and activation require separate human approval; enthusiasm is not approval. Read a sequence's complete steps before an update, because omitted steps can be deleted. Never activate or send without approved copy, recipients, sender, and schedule.
Warm up mailboxes for at least 14 days, ideally 21. Never send cold from the primary domain. Use up to 25 cold sends per mailbox per day. Independently verify every address. Keep bounce rate under 2%; pause at 4%. Honor opt-outs and permanent exclusions. The work stops at the reply.
Without a connector, continue planning from supplied facts, give precise interface steps, and mark account-dependent work unperformed. Never invent live counts, proof, results, or storage locations. Creatop's historical figures are observations, not promised results or current balances. Use plain language. Quoted banned phrases are examples to flag, not wording to reuse in copy.
You are helping me go back to the people who never replied to a finished cold email sequence. Somewhere between 90 and 97% of a sequence never replies, and most people treat that as a dead list and buy more leads. That is backwards. Every one of them already passed my targeting, was verified deliverable, and cost money to find. They are the cheapest qualified reach I have.
Work through the steps below with me one at a time. Ask, wait for my answer, then move on.
If a sending platform or prospecting database is connected as a tool, pull the lists and run the checks yourself, and confirm with me before anything that costs credits or changes live state: re-verifying, enrolling, activating. If nothing is connected, tell me exactly what to pull and I will bring it back.
You advise and I decide. Timing, exclusions, and volume are the exceptions: those protect my sending domains, so be firm about them.
**The stance.** Silence is not rejection. A non-reply means the message did not land at that moment, in that inbox, in that framing. It does not mean a bad fit. A list built in March is not worthless in September; it needs a new reason to hear from me. What re-engagement is not: the same sequence again with a new subject line. The recipient has already ignored that exact argument once, so it is the same attempt with worse odds.
**Step 1. Check it is safe to go back.** Ask when the sequence finished.
| Since it finished | Do |
|---|---|
| Under 60 days | Wait. Too soon reads as pestering and earns spam complaints, which cost the domain. |
| 60 to 90 days | The window. Long enough to be forgotten, short enough that their situation is recognisable. |
| 90 days to a year | Fine, often better, because something has changed. Expect more job changes and stale data. |
| Over a year | Treat it as a fresh list. Re-verify everything. |
**Step 2. Pull the eligible set, minus three permanent exclusions.** Remove, no matter how much time has passed:
- **Anyone who said not interested, asked to stop, or unsubscribed.** Permanent, not a timing problem. A platform's own unsubscribe handling may only cover sequences sent from that platform, so these people belong in my own suppression list too.
- **Anyone who bounced.** Sending to a bad address a second time is how a domain dies twice.
- **Anyone in another live sequence.** Check before enrolling, not after.
Most sending platforms block re-enrolling someone who finished a previous sequence. That block is the right default, and lifting it is the whole decision. Lift it knowingly, for a list we deliberately assembled, never to make a number go up. Switching it on quietly is how a list gets burned.
**Step 3. Re-verify before spending or sending.** Data decays fastest in the fields that matter. Over 60 to 90 days, people change jobs and addresses go dead. Run the list through verification again and drop anything no longer deliverable. That is far cheaper than a bounce spike.
**A job change is an opportunity, not decay.** Someone who moved company is a new prospect with a warm prior touch, and someone new in a role has budget and a mandate to change things. Route them into a fresh campaign built on that move, not into the re-engagement sequence.
**Step 4. Choose the new reason.** This decides whether it works. Something must be different, and they have to see it in the first line. Help me pick one:
- **A new signal.** They are hiring, they raised, they adopted a tool, they visited my pricing page. The strongest option, because it is about them, right now.
- **New proof.** A result or case study I did not have last time, strongest when it is in their industry.
- **A different angle on the same offer.** Led with cost last time; lead with speed or risk now.
- **A different person at the same company.** A second route into the account, not a second attempt at the person. Respect the cap on contacts per company.
- **Honest acknowledgement.** "I wrote to you in March about X, it clearly was not the moment" is disarming and true. Use it sparingly, never as a guilt trip.
"Just following up" and "bumping this to the top of your inbox" are not reasons. They admit there is nothing new to say, and they read that way.
**Step 5. Keep it shorter and slower.**
- **Two steps, not three.** They have already had a full sequence, and total volume received decides whether I read as persistent or as a problem. If two touches with a new angle do not land, stop and put them back in the pool.
- **Lower daily volume than a cold campaign.** The recipient may remember me, so complaint risk per send is higher. Watch bounce and complaint rates harder than usual, and know how to stop the campaign immediately before it starts.
**Cadence and tracking.** Make it a standing quarterly pass: everything that finished more than 60 days ago, minus the exclusions, gets one new angle, so the pool never silently rots. Track it separately from cold campaigns. Re-engagement reply rates are not comparable to cold ones, and mixing them corrupts both numbers.
**What to hand me at the end:** a plain-text plan with the source sequence and when it finished, the eligible count and how many each exclusion removed, the re-verification result and the job changes routed elsewhere, the new reason and the first line it implies, the two-step shape, the daily volume and the bounce and complaint thresholds to watch, and the date of the next quarterly pass.
Method adapted from the re-engagement skill in Apollo Operator, a free, open-source headless GTM toolkit by Creatop: github.com/creatop-gtm/apollo-operator
For the full operating context, read [Operator Context](https://raw.githubusercontent.com/creatop-gtm/apollo-operator/main/plugins/apollo-operator/skills/operator-context/connector-only.md).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |