Follow up with inbound leads
React to every inbound lead in minutes — qualify, personalize, respond, schedule.
Outcome: Every inbound lead gets an enriched record, a qualification decision, a personalized response sequence, and its meeting intent flagged for scheduling — the human enters only when the conversation is ready for a meeting.
Availability: 1 of 8 steps coming soon — the rest is callable today.
Speed-to-lead as a workflow: the difference between a 5-minute response and a 5-hour response is most of the conversion rate. This recipe is event-driven end to end — no polling, no batch jobs.
Steps
- Receive the signal
A webhook event (or your product's own signup/demo-request event) tells the agent a lead arrived. Reply's webhooks push email and LinkedIn engagement events to your endpoint. Uses Webhooks & Events API .
- Create or update the contact
Upsert the lead as a contact with source and context captured in custom fields. Uses Contact Data API .
- Enrich the lead Coming soon
Fill in title, company, and phone from the email address or LinkedIn URL. Uses Contact Enrichment API .
- Qualify agent logic
The agent scores the lead against the ICP using the enriched fields — its own logic, informed by the data modules.
- Select and start the right sequence
Route hot leads to a short, direct sequence and colder ones to a nurture sequence; add the contact and start. Uses Sequence API .
- Send a personalized first response
For immediate one-off replies outside a sequence, send a direct email or LinkedIn message. Uses Outreach Actions API .
- Manage the conversation
Read the thread, watch the reply category, toggle meeting intent when the lead asks for a call. Uses Conversations & Inbox API .
- Log the outcome
Meetings and activity show up in reporting; the CRM stays in sync via Reply's native CRM integrations. Uses Analytics API .