Helpdesk & reactive works
Stop retyping emails into jobs.
An inbound maintenance email becomes a drafted, structured job in seconds — site, category, and priority already filled in. A person still approves every one.
Four steps, no retyping
01
An email lands
A site contact, a client, or a tenant reports something the ordinary way — by email. No new inbox to teach anyone, no portal login required of them.
02
docket reads it
Sender, subject, and body are read together. The site is matched from the sender's known contact record; category and priority are inferred from what's actually described.
03
A draft job appears
Title, description, site, category, and priority — already filled in, sat in a review queue. Nothing is created live yet. This step is the whole point: a draft, not a job.
04
A person approves it
One click to confirm, or edit anything first — wrong site, wrong urgency, whatever. Reject it and nothing happens at all. The job only exists once someone says so.
Once approved
A job like any other
An approved email-drafted job lands on the exact same job page as one raised by phone or by hand — SLA clock already running, full timeline, ready to assign. No second-class “auto-created” jobs living in a different part of the system.
What's actually happening under the extraction
Site matched from who sent it
Every site contact in docket is a known email address. An inbound message from one is matched to their site automatically — no client reference number to hunt for.
Category & priority, inferred not guessed
Reads the actual words used — “no heating,” “minor,” “urgent” — against your tenant's own configured categories and priority matrix, not a generic keyword list.
Duplicate detection
An open job already exists for this site and category? Flagged before you approve a second one, the same warning helpdesk staff see raising a job by hand.
Review, every time
No confidence-threshold auto-approval. Every drafted job sits in front of a person before it's real — the AI drafts, it never decides.
Wrong isn't a crisis
Edit the site, category, priority, or description right there in the review screen before approving. Getting it wrong costs one click to fix, not a support ticket.
Fully logged
Every drafted job's source email, what was extracted, and who approved or rejected it stays on record — the same audit trail as a job raised any other way.
Same list, same filters
It's just another row in Work Orders
Filter, search, bulk-assign — an email-originated job behaves exactly like every other row on the list your team already lives in. Nothing new to learn on the receiving end.