The pipeline is the same regardless of how it got here.

The receive path you choose only affects how a reply reaches us. Once inside, every reply runs the same checks.

1

Identify the application

Four matchers, in order of strength: per-application address (if you used one) → reply-thread headers (when the original message preserves them) → sender plus subject → sender alone. If none of the four fires, the email is held for you to attach by hand (see Step 6).

2

Deduplicate

Each email gets a stable ID derived from its RFC Message-ID. If we have seen it before — via any path — it is rejected at the database level. Status is never flipped twice for the same message.

3

Detect self-sent

If the sender is your own address, the email is recorded as outbound for thread completeness and classification is skipped. Re-importing your own sent message is a clean no-op.

4

Classify with AI

The reply’s text plus the application’s current state goes to a language model with a deliberately conservative prompt. The model returns a proposed status, a confidence score, an explanation, and a flag for whether the email needs your reply.

5

Apply the status update

A proposed status only takes effect if confidence is above your threshold and the transition is valid (first interview → second interview is fine; rejected → under review is not).

6

Recover unmatched forwards

If none of the four matchers fires, we email you a single-use link (good for 14 days, no login required) that opens an attach page with your active applications. Pick the right one and the email runs the same classification pipeline. Nothing is lost.

7

Notify you

A real-time event hits any open dashboard via Server-Sent Events. A recommended action is computed. A confirmation email is sent based on your preference in Settings → Reply Capture (three modes: manual forwards only, always, or never).

8

Reconcile

A periodic task re-checks each active application’s recommended action. If a signal was missed at classification time, it gets corrected later.

What we promise, in plain language.

Five lines. No fine print. The full versions live in our Privacy Policy and Terms of Service.

We can’t read your inbox

Job Beast doesn’t hold a key to your mailbox. We only see what you explicitly hand to us.

Backend-only mailbox

[email protected] is operated by Job Beast, read by our backend. No humans browse it.

You control both doors

Send-only OAuth on the way out. Manual forward or one-click import on the way back. We only see what you decide to send our way.

AI without retention

Email content goes to our AI provider for status classification. They do not store it and do not train on it.

Stop any time

Stop forwarding or uninstall the add-on. Delete any imported email from its application page.

Pick the integration that fits how you work.

You can change your mind any time — nothing is locked in.

Get Started Free