Tracking what comes back

To track responses you need to see them, and a job seeker’s inbox contains far more than job applications — medical correspondence, finances, private conversations. Asking for broad access to read it is asking for a great deal.

Narrow it as far as the provider allows: a dedicated address for applications, a specific label or folder the user controls, or scoped read access rather than full mailbox permission. What the agent cannot see, it cannot leak.

Read-only is the other half of the ask and the one most easily conceded. Tracking requires reading and nothing else, so a scope that cannot send, delete or modify removes an entire category of possible harm at the cost of nothing the feature needs.

• A dedicated address used only for applications, where practical
• Scoped access to one label or folder, not the whole mailbox
• Read-only, since tracking never needs to write
• Retain only what relates to a tracked application
• Revocation that genuinely deletes retained content

Fine-grained classification is a distraction. What changes the candidate’s behaviour is a short list: this needs your attention now, this is a rejection, this is an automated acknowledgement, this is not about a job at all.

Anything needing action now — an interview invitation, a request for availability, a question — should surface immediately and prominently. Everything else can be summarised.

The fourth category carries more weight than it appears to. Correctly identifying that a message is not job-related is what stops the agent processing, storing and summarising personal correspondence it had no business reading, so it deserves to be an explicit outcome rather than a residual bucket.

Rejections are frequently written to be gentle, which makes them genuinely hard to classify. "We have decided to move forward with other candidates at this time, but we would like to keep your details on file" contains a decision and an encouragement, and systems regularly read the wrong one.

Report confidence and route uncertain cases to the person. Misclassifying a rejection as an open thread leads to a follow-up that makes the candidate look like they did not read their own mail.

A deferral is a third thing that neither category fits. "We are pausing this search and will be back in touch" is not a rejection and not an open process, and forcing it into either produces a wrong follow-up or a wrongly closed record — so it deserves its own state.

It is technically easy and almost always wrong. An automatic acknowledgement of an interview invitation can commit a candidate to a time they cannot make, and an automated answer to a substantive question can say something they would not.

Draft, do not send. The agent’s value is that the reply is ready in five seconds; the candidate’s value is that it is theirs.

A draft with the context attached is the version that saves real time. Showing the original application, what was sent, and the thread so far means the candidate answers in two minutes instead of spending twenty reconstructing six weeks of history first.

A notification for each classified message recreates the inbox the candidate was trying to escape. The point of tracking is to reduce attention spent, not to redistribute it.

Interrupt for the few things that are genuinely time-sensitive, and batch the rest into a daily summary of what changed. That is the difference between a tool that lowers the anxiety of a job search and one that raises it.

Rejections in particular belong in the digest rather than as an alert. A push notification delivering a rejection is a needlessly unpleasant way to receive news that requires no action, and it is the single easiest thing to get wrong in a product used by people already having a difficult few months.