Our own operation at Horizon Dev
A hundred sender inboxes. One person reads only the replies that matter.
Cold email at volume produces replies at volume: out-of-office, "unsubscribe", "wrong person", and, buried in there, "sure, send me a time." Someone used to read all of it.
Every reply, classified
100+ inboxes, one human
Interested, not now, wrong person, out of office, unsubscribe, bounce.
The AI part
Every reply that lands in any of our sending inboxes goes to Claude with one job: say what kind of reply this is. Interested. Not now, follow up in a month. Wrong person, with the right one's name if they gave it. Out of office. Unsubscribe. Bounce. The model returns the category and a one-line reason, and the rest is plumbing.
What happens next
- Interested: a lead and a follow-up task are created in Close, our CRM, assigned to the right person, with the thread attached. That person sees it within ten minutes.
- Not now: the contact is paused and a dated task comes back when they said to.
- Unsubscribe and bounce: removed from every sequence, across every inbox, automatically.
- Out of office: ignored, and the sequence keeps going.
Why it matters
A hundred inboxes produce more replies than one person can read, and the positive ones are rare enough that they get missed when someone's tired. The model never gets tired, and it writes down why it decided what it decided, so a human can check it. One person now runs the whole reply side.
The small-business version
You don't need a hundred inboxes to want this. One shared inbox where customer questions sit for hours is the same problem. That version takes an hour. Here's what it looks like.
The task you're thinking of right now. That one.
Twenty minutes, free. By the end of the call you'll know if an hour fixes it.
No pitch. No deck. If it's not a fit, I'll say so.