Triage replies, draft responses

SDR / founder running outbound · One-time voice setup ~20 min; recurring triage batch <10 min per inbox sweep.

GTMEdit flowon X◆ new (unverified) 91

step 1ready

Capture your voice and reply preferences

brand-voice11 alts

step 2connector

Pull inbound replies from inbox

⚡ bring your own tool

step 3ready

Triage and classify replies

inbox-triage

step 4ready

Handle objections with evidence-backed counters

objection-handling

step 5partial

Draft context-aware replies for all other types

dm-respond10 alts

step 6ready

Polish drafts to remove AI writing patterns

avoid-ai-writing

step 7ready

Assemble final triage report and send queue

taskflow-inbox-triage

Did this recipe work for you?

What you get

▸Classified triage table (intent type per reply, prioritized)
▸Polished, voice-matched draft per reply — ready for one-click send
▸Objection-handling responses with evidence-backed counters
▸Unsubscribe and wrong-person flags for list hygiene actions

tools: Gmail MCP or sequencer API (Instantly/Smartlead) — free tier or $49-99/mo depending on volume

tokens: ~$1-3 per 20-reply batch

≈ $3-10/mo in tokens at steady SDR volume; external inbox tool cost is additive

What stays yours

· Review each draft and hit send — never fully autonomous sending without human approval
· Flag and process unsubscribe requests through your ESP to maintain legal compliance (CAN-SPAM / GDPR)
· Tune the voice profile after the first two batches once you see where drafts miss your tone

The problem

When inbound replies pile up from a campaign, I want an agent to classify each reply type (interested, objection, OOO, wrong-person, unsubscribe...) and draft a context-aware response grounded in my voice, so my inbox doesn't become a graveyard and outbound stays manageable without a team.

Cybernetic layers

Memorypartial

Voice profile (step 1) is a persistent local file — that's stable memory. Reply history (who said what, which stage they're in) has no harvested artifact; store in a Google Sheet or local CSV between sessions.

Background-schedulingbyo

Nothing in the pool auto-triggers on inbox arrival. Schedule daily as a Claude Code cron task or run manually on demand after each campaign wave.

Harnessready

Claude Code is the runtime. Install skills into ~/.claude/skills/ and invoke in sequence. Steps 1-7 run in a single session.

Click any step to see what fills it — and the ranked alternatives you can swap in.