Emails the portal would not turn into a job on its own — a layout it hasn't got a template for, or a known layout with a field it couldn't read. Check the details, correct anything, then Create the job or Dismiss. Nothing here has been created yet.
Paste the subject and body of a job email (a Concerto "New Job Alert" or a Chapplins "new job has been raised" works as-is). Check shows what the portal would make of it without creating anything. Create the job really logs it.
Every email the intake address receives, newest first, with what happened to it. created / updated = a job on the board · order = a Concerto order sheet filed under Client orders (cert-review) · cancelled = a Concerto cancellation applied to the job (❌ pill + timestamp on the board) · review = held for a human (above) · dropped = a reply, notice, quote or supplier paperwork · duplicate = the same email arrived twice.
| Received | From | Subject | Outcome | Job | |
|---|---|---|---|---|---|
| Loading… | |||||
Each of these is a fixed template (no AI, no guessing) matched by the sender and the email's own markers. Only these create jobs automatically; anything else is held above for a check. To add a client, send Jamie a few example emails and a template gets built and tested for it.
Only emails from these senders / domains are processed (anything else is logged as ignored and never sent to the AI). One per line — a domain like concerto.co.uk or a full address.
jobs@your-domain, action Send to a Worker → mostlane-api.noreply@concerto.co.uk or chapplins.co.uk (add any other job senders) → Forward to jobs@your-domain. Use forward, not redirect, so the copy is sent from your own address and passes the spam checks.