LinkedIn-first outreach
Lead with the warm channel — connection requests and voice notes first, email as the follow-through.
Outcome: A running multichannel motion where LinkedIn opens the door and email carries the details - with all replies, from both channels, landing in one inbox.
Availability: runnable today — all 5 steps are callable now.
Email-first outreach fights spam filters; LinkedIn-first borrows social proof. Everything in this recipe is available today — including LinkedIn voice messages via the Outreach Actions API, which very few stacks can do programmatically.
Step-by-step guide: docs.reply.io/guides/launch-outreach — the canonical per-surface instructions (MCP, CLI, Skills, API) for this workflow.
Steps
- Connect LinkedIn accounts
Link the team's LinkedIn accounts and set daily action limits that keep accounts safe. Uses LinkedIn Accounts API .
- Open with a connection request
Send personalized connection requests — or voice messages for accounts that allow them — as one-off touches. Uses Outreach Actions API .
- Sequence the follow-through
Build a sequence that leads with LinkedIn steps and falls back to email for prospects who don't accept. Uses Sequence API .
- Converse in one inbox
LinkedIn replies and email replies arrive in the same unified inbox with the same categories — one conversation surface for the agent. Uses Conversations & Inbox API .
- Compare channel performance
Read the LinkedIn overview against the email overview and shift mix toward what converts. Uses Analytics API .