How replies are detected
What counts as a reply, how Funkel pauses follow-ups, and what stays in your court.
The moment a lead replies, Funkel does two things at once: it cancels every remaining workflow step for that lead, and it lands the message in your inbox so you can take it from there.
What counts as a reply
Any incoming LinkedIn message from a lead Funkel has reached out to. Connection acceptance is not counted as a reply, it’s a separate event that simply unblocks the next workflow step.
How fast is detection
Funkel listens for incoming messages on a webhook from the LinkedIn integration, so reply detection is near-instant for most accounts (typically under a minute). A polling fallback runs in the background to catch anything the webhook misses.
What happens automatically on reply
- All scheduled later steps in this lead’s workflow are canceled.
- The lead is marked as replied.
- The conversation surfaces at the top of your inbox.
- If you have a
reply.receivedwebhook subscription, it fires. - If Slack is connected, a notification posts to your channel.
What doesn’t happen
Funkel never auto-replies. The conversation is handed back to you the moment a human shows up, which is usually the whole point of running outbound in the first place.
Edge cases
- Out-of-office replies. Funkel treats these as replies and pauses follow-ups. If you’d rather follow up after their OOO ends, send a manual note from the inbox a few days later.
- Auto-decline of connection. Not a reply, no inbox event: the lead simply moves to declined and their workflow ends.
- Conversations from before Funkel was installed. If a lead messages you on LinkedIn before they entered a campaign, that conversation appears in the inbox but it’s not tied to any campaign or workflow.