Outreach · Recruiter running sequences
Follow up without talking over a reply
Every follow-up checks the thread first. A reply stops the sequence, and your agent drafts the answer for you to confirm.
Who it is for
Recruiters running multi-step sequences who have been burned by a follow-up sent after the candidate already answered.
The problem
Sequencers that do not read the inbox keep sending. A negative reply should end the conversation for good.
Workflow
- 01
Check
Before each follow-up the thread is read. A reply stops the sequence for that person.
- 02
Mark
A negative reply marks the person do-not-contact.
- 03
Draft
Your agent reads the reply and drafts an answer.
- 04
Confirm
send_reply needs confirm=true. There is no auto-reply.
Sample transcript
- Tool call: list_replies { needs_reply: true }
- Result: ← follow-up for Ada skipped: reply received · sequence stopped
- Agent: Ada replied and asked about remote days. Draft below. Send it?
- You: Send it.
- Tool call: send_reply { conversation_id: "enr_4", body: "…", confirm: true }
- Result: ← reply queued inside working hours
Outcome
- No follow-up after a reply, and no second sequence for someone who said no.
- Every reply you send has been read by you first.
Example prompts
Morning check
“Who replied overnight on LinkedIn? Summarise each thread and draft an answer for me to approve.”
Stop one
“Stop the sequence for Jonas, he's taken another offer.”
Send
“Send the reply to Ada as drafted.”
Tools and endpoints
| tool | endpoint |
|---|---|
| list_replies | GET /v1/outreach/conversations |
| get_conversation | GET /v1/outreach/conversations/{conversation_id} |
| send_reply | POST /v1/outreach/conversations/{conversation_id}/replies |
| update_enrollment | POST /v1/outreach/enrollments/{enrollment_id}/stop |
Credit cost
example data| Reply checks and replies | 0 |
|---|---|
| Connected account | €49 / month |
| Total | 0 credits |
Example data.