An agency hires a person to read replies all day. Codex matches each reply to its send, gives it one of seven labels, and files it before you read it.
Somebody reads the inbox all day. Every reply is opened, judged and moved by a person paid to do nothing else. At a twenty-person software company that person is whoever opened email last.
By hand today
“Every reply that comes in gets read and sorted.”
A job advert for an Email Reply Manager, on OnlineJobs.ph, read 7 September 2026
That is the whole job, in one line. An agency hires a person to sit in front of the replies and decide what each one is. The advert does not ask them to write anything.
A smaller company has nobody in that seat. Replies land in the founder’s inbox next to the accountant and a newsletter. An out-of-office notice sits in the same pile as the one person who said yes. The sort happens when the founder gets to it, often at the weekend, and by then the yes has cooled.
The other failure is quieter. Someone writes “please do not contact me again”, the message is skimmed and left, and the next follow-up goes out on schedule. Nobody meant it. Nobody sorted it either.
What it costs you each week
80 to 120 replies a day is one full-time job in an agency. The advert exists because nobody sorts an inbox in the gaps between other work. Below that volume the job does not go away. It just has no name.
Source: a job advert for an Email Reply Manager, OnlineJobs.ph, read 7 September 2026
The advert prices this stage at a hire. A company sending under the caps in chapter seven will never see that many replies in a day, so it never hires, and the stage is done by nobody in particular.
What it costs is delay, and delay is measurable. Count two things in your own week: replies still unsorted when the day ends, and the minutes between a reply arriving and someone deciding what it is. Reply rates are not given here; every figure found for them was a vendor’s own send log.
The build
Codex: a sorter that never sleeps. Every reply is matched to its send, given one label, and written to the CRM before you read it. The human ones wait for you. The rest are filed.
The labels come first, because the tool can only sort into boxes you have named. Seven cover what actually arrives: interested, not now, wrong person, referral, stop, out of office, and bounce.
Open Codex in the folder that holds sends.log from chapter seven, and give it read access to the mailboxes that sent the messages. Type:
Read sends.log. Every few minutes, fetch new replies to the mailboxes in it.
Match each reply to the send it answers, by thread and by address. Give it
one label: interested, not now, wrong person, referral, stop, out of office
or bounce. For out of office, record the return date. For stop, mark the
lead so nothing is ever sent to them again. Append every objection in the
reply, word for word, to objections.md. Write the label and the full reply
to the CRM. Show me the interested ones and anything you are unsure about.
Never send a reply yourself.
What comes back is a short list: the person, the label Codex proposes, the sentence that decided it, and the original message underneath. An automatic reply that reads like a person goes on the unsure list rather than being filed; that is the case rules get wrong.
Everything else is saved without you. replies.log records when each reply arrived and when it was sorted. objections.md grows by one quoted line per objection, in the words the person used. The CRM gains one activity per reply, so the lead’s page shows what they said and when.
A public tool, OpenOutSend, does part of this for email: it sorts bounce, automatic reply, opt-out and human by headers and pattern matching, and stops at the human reply. Sorting the human replies by what they mean is the part it leaves to you.
The pattern is ArkOne’s own inbound lane, at src/app/api/email/inbound/route.js lines 341 to 372: an email arrives as a notification, is fetched from storage and parsed, with no human in the path. The objection file follows plans/clinic-dubai-campaign/icp.md line 304: every objection is appended verbatim, and the third time the same one appears, the message that provoked it has to change. The reader builds their own version of both. There is no demo to download.
What it feeds
Following up without remembering. A labelled reply tells the next stage what to do: stop, pause until a date, or carry on. Proof: zero replies unsorted at the end of the day.
Chapter nine runs follow-ups by position in a sequence, and it can only stop one if the reply has been matched and labelled. Interested and stop end the sequence. Out of office pauses it until the return date. Wrong person and referral open a new lead with the name the reply gave you.
Three numbers prove this stage worked. Replies unsorted when the day ends, which should read zero. Minutes from arrival to sort. And objections logged verbatim, because an objection nobody wrote down is a message nobody will fix.
What stays with a person
Answering, and the silence. The tool sorts. It never writes back. A human reply gets a human answer, and a stop gets nothing at all.
The interested pile is yours to answer, in your own words, the same day. A tool should not draft it.
The stop is harder, because doing nothing feels like rudeness. It is not. One sender on Hacker News, on the people who tell him to stop: “To them, I do not even reply” (hunter-2). The lead is marked, the sequence ends, and no confirmation goes out.
The third judgement is the unsure list: an automatic reply written in the first person, a “not now” that might be a polite never, a referral to a name with no address. A person reads those, and the label they choose is the one the CRM keeps.
The tools you already pay for
Nothing new to buy.
Mailbox: the same Google Workspace or Microsoft 365 seats that sent the messages.
CRM: one activity per reply, carrying the label and the words.
A text file: objections.md, read once a week before any message is rewritten.
LinkedIn: replies read by hand and pasted in; the tool labels them the same way.
No shared inbox product. Two files beside the send log.
Sort every reply in the hour it lands. Then nobody has to remember the follow-up.
Ask: How many replies are sitting in your inbox right now that nobody has labelled?
This is chapter eight of twelve, after sending without getting banned and before following up without remembering. The book, Building a real outbound engine with Claude Code and Codex, end to end, runs the whole engine in order, from writing down the market to reading the weekly number, one chapter per stage. A free starter edition for firms under fifty people is coming through the 100k programme.