~/robynrocha.io

RWork Every Reply

Pelican Reply Hub

Interested replies become Slack alerts; reps answer in one click. Nothing dropped, nothing doubled.

SlackPlusVibeClaude Code

When a prospect replies to a cold email, Pelican filters out the auto-replies, detects interest, and posts an alert to Slack with a Reply button. The rep writes their response in a Slack form and Pelican sends it through the email platform — instant confirmation, the send finishes in the background, and it never double-sends even when Slack retries a click. A daily sweep catches anything the instant alerts missed.

Interested replies stop falling through the cracks. Reps answer from the tool they already live in instead of digging through a sending platform they rarely open, and response time on the most valuable moment in cold email — someone saying “tell me more” — drops to one click.

Behind the hub runs a full post-send chain: every reply typed with a human approving the read, cadence that halts the instant anything comes inbound, booking handled on the prospect's behalf rather than behind a link, and a do-not-contact list read at send time — never cached, never negotiated with.

$render pelican.mmd

No diagram code provided

rendering diagram…

Goes deeper

SDR Systems — Pelican, and the chain behind it
System breakdownA suppression list you cache is not a suppression listDo-not-contact is the one rule in outbound with no acceptable failure rate. Almost every implementation quietly introduces a window where it is wrong.System breakdownThe gate that trains its own replacementHuman review is usually framed as a temporary cost you remove once the model is good enough. Built differently, it is the thing that makes the model good enough, and the thing that tells you when to stop.

RAlso in this stage