Find and contact prospects

From an ICP definition to booked meetings — the complete outbound loop.

Outcome: A running multichannel campaign against a fresh, enriched prospect list, with replies monitored and meetings landing on the calendar.

Availability: 2 of 9 steps coming soon — the rest is callable today.

The canonical outbound motion, decomposed into API calls. Each step is one module; the output of each step is the input of the next. An agent can run the whole loop or take over any single step — for example, bring its own prospect list and enter at step 3.

Step-by-step guide: docs.reply.io/guides/find-prospects — the canonical per-surface instructions (MCP, CLI, Skills, API) for this workflow.

Steps

  1. Define an ICP agent logic

    The agent turns the user's goal into concrete filters — job titles, seniority, department, industry, company size, location.

  2. Search for matching people and companies Coming soon

    Run a Live Data search over the 1B+ contact B2B database and preview results before committing credits. Uses Prospect Search API .

  3. Store them as contacts

    Import the selected prospects as contact records, organized into a contact list for this campaign. Uses Contact Data API .

  4. Enrich what's missing Coming soon

    Find missing emails and phone numbers; enrich records from LinkedIn URLs. Uses Contact Enrichment API .

  5. Validate before sending

    Schedule email validation on the list to protect deliverability. Uses Email Validation API .

  6. Create a multichannel sequence

    Create the sequence, add email and LinkedIn steps with A/B variants, assign sending mailboxes, set the schedule. Uses Sequence API .

  7. Add contacts and start

    Bulk-add the enriched contacts to the sequence and start it. Uses Sequence API .

  8. Monitor responses

    Subscribe to email_replied and reply_categorized webhook events — or poll the inbox — and read full threads as they arrive. Uses Conversations & Inbox API .

  9. Measure outcomes and track meetings

    Track opens, replies, and the meetings report (meetings are booked via Reply's in-app scheduler; the API reports them); pause losing variants and double down on segments that convert. Uses Analytics API .