- Sales
- v1.0.0
- outreach
- sales
Multi-sender rotation
Use this skill when one LinkedIn campaign needs more volume than a single account can safely send: scaling outreach across several sender accounts, sizing a sender pool, splitting a lead list between profiles, or reacting when one account in the pool gets a warning. Produces a rotation plan with per-account caps and an incident playbook.
SKILL.md
Run this when campaign volume exceeds what one account can safely send. It produces a sender-pool plan: how many accounts, how leads are split, per-account caps, and what happens when an account degrades.
The play
- Size the pool from the target, not the other way around: divide required daily connection requests by 20, the safe steady-state ceiling per warmed account. A 100-invite-per-day campaign is a 5-account pool.
- Only rotate warmed accounts. A new profile joins the pool after a full warm-up ramp, never on day one. Keep one warmed spare per five active senders: the bench rule. When an account degrades, the bench replaces it the same day.
- Split the lead list by account, never round-robin per message. Each prospect belongs to exactly one sender for the entire relationship: the one-voice rule. Dedupe by person and by company before launch so two senders never hit the same account.
- Stagger sending windows so the pool does not fire in one burst: each account keeps its own working hours, matched to its own timezone and history.
- Keep per-account caps individual. An account fresh off warm-up sends less than a veteran; never apply the pool average to every profile.
- On any warning: pull that account from rotation immediately, pause it 48-72 hours, and let the bench absorb its remaining volume. Never redistribute a paused account's leads mid-conversation; conversations wait for their owner.
- Review the pool weekly: acceptance rate and reply rate per account. One account trending down while others hold is an account problem; all accounts trending down together is a targeting or copy problem.
What good looks like
- Experienced operators read per-account acceptance rates as an early-warning system; the mediocre version only watches campaign totals and misses the one account quietly dying inside a healthy average.
- The common mistake is treating the pool as one big account: shared caps, shared list, leads bouncing between senders. Prospects notice a second stranger continuing a first stranger's conversation, and so does the platform.
- Done well, losing any single account costs at most one-fifth of daily volume for two days, no prospect ever hears from two different senders, and the campaign total stays flat while individual accounts rest and rotate.
Rules
- MUST warm up every account fully before it enters rotation.
- MUST keep each prospect with one sender for the whole relationship.
- MUST pull a warned account out of rotation the same day and rest it 48-72 hours.
- NEVER round-robin messages to one prospect across accounts.
- NEVER let two senders contact the same company without a deliberate multi-threading plan.
Files
1 file ship with this skill. They are installed beside the SKILL.md.
NOTICE1.4 KB
Multi-sender rotation
Imported from the GTM Skills library by Swan (https://www.gtmskills.com), skills/imad-badreddine/multi-sender-rotation
at https://github.com/swan-gtm/gtm-skills/commit/5d786aad0c7b2ca59b1abf1f601f9407ca261996. Written by Imad Badreddine (https://www.linkedin.com/in/imad-ngl/).
The skill is shared under the MIT License below; this notice must stay with any copy.
MIT License
Copyright (c) 2026 Swan
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.