Approve before send: why your application e-mails wait for you

Auto-apply tools promise volume. The risk is that you cannot see what went out in your name. One wrong attachment, one invented claim, one e-mail to the wrong person, and you have spent a reputation you were building for years.

Careers takes the opposite position: nothing is sent without your approval of that exact message.

What "exact" means#

When you review an application e-mail you see the whole message: from, to, subject, text and attachments. Approve it, and the approval is tied to that revision. If anyone edits the draft afterwards (you, an AI, a second tab), the approval no longer holds and you read the new version. Before delivery, the system compares the message with what you approved once more. This is a design rule, not a setting.

Your AI cannot approve either#

If you connect Claude, ChatGPT or Grok through Geenius OS, it can create and edit drafts and ask for approval. A note appears in your outbox: "Waiting for you", with one line about why. The door has no send or approve action at all, and refuses those words by name. A signed-in person approves; that is the only path.

After you approve#

Approval does not mean instant. The e-mail waits a random delay (7 to 25 minutes by default) and is moved into the recipient's business hours, Monday to Friday 08:30 to 18:00 in their time zone, up to a daily limit (ten by default). Two reasons: it avoids the look of a bot, and a message that arrives in the recipient's morning is more likely to be read. You can cancel while it is scheduled, and it becomes a draft again.

Your own sending account#

Applications go out through your own Resend account, from your own domain. There is no shared key of ours to fall back on. That means setup (a verified domain, an API key) and it also means that the e-mails come from you, with your sender reputation. If something goes wrong, it is your domain, and you control it.

Replies#

Replies need an address Careers can read. You create one in Mail settings and forward replies to it, for example with a Gmail filter. Replies are matched to their thread and application, so the pipeline shows where you stand.

Why not a faster mode#

We are often asked for an auto mode. We do not offer one, for a reason that has nothing to do with caution for its own sake: an application is a promise made in your name. Reading it takes twenty seconds. That is cheap compared with what one bad send can cost, and the twenty seconds are also when you notice that you would rather phone the client.

A good rhythm#

Tailor in the morning, read and approve in one sitting, let the schedule spread the sending, and rehearse for the replies. The tool carries the work. You carry the decisions.