Run an account-based campaign
Target named accounts, multithread into each buying committee, and report by account — not by contact.
Outcome: Coverage of every target account with multiple threads per buying committee, and an account-level view of engagement your team can act on.
Availability: 2 of 6 steps coming soon — the rest is callable today.
ABM is coordination work — exactly what agents are good at. The account and account-list objects exist in the Contact Data API today, so the skeleton of this recipe runs now; the prospecting and enrichment steps light up as Live Data ships.
Step-by-step guide: docs.reply.io/guides/launch-outreach — the canonical per-surface instructions (MCP, CLI, Skills, API) for this workflow.
Steps
- Load the target account list
Create account records for the named companies and organize them into an account list for the campaign. Uses Contact Data API .
- Find the buying committee Coming soon
Search for contacts at those companies across the roles that decide — champion, economic buyer, technical evaluator. Uses Prospect Search API .
- Enrich every stakeholder Coming soon
Fill emails, phones, and firmographics so each thread can start personalized. Uses Contact Enrichment API .
- Multithread the outreach
Run role-specific sequences per persona — different message for the CFO than for the ops lead — linked back to the same account. Uses Sequence API .
- Watch replies account-wide
Track conversations across all threads of an account; one positive reply changes the play for every other thread. Uses Conversations & Inbox API .
- Report by account
Roll engagement up to the account level and hand the sales team a ranked list of warming accounts. Uses Analytics API .