Built around how the work actually arrives
Not a scheduling product with email bolted on. WorkOrders starts at the inbox, because that is where a trades job starts — and follows it all the way to a closed-out record you can export.
What you get today
Everything below is in the product now. Try all of it during the trial.
Email-to-work-order
Connect Gmail or any IMAP mailbox. Requests become work orders with the original message, its thread and every attachment kept alongside.
AI triage
A plain-English summary, an urgency read, and the site, contact and trade pulled out of the message — all editable before anyone acts on them.
Attachment descriptions
Photos that arrive with a job are described in words, so a picture of a failed valve is findable six months later.
Dispatch and assignment
Give a job to a technician and it is on their phone with everything attached. New, assigned, ongoing, completed — four states people will actually keep current.
iPhone app for the field
Today's jobs, the details, the photos, and status changes that land back in the office the moment they are tapped.
Automatic customer updates
Status emails go out as a reply to the customer's own message, from your firm, with your sign-off — not from software they have never heard of.
Customers and sites
Every job hangs off a customer and an address, so the history of a building is one click from the job you are looking at.
CSV and reports
Pull completed work out by date range for invoicing, payroll or a client who wants a summary. The same export the legacy system produced, byte for byte.
Roles that make sense
Owner, admin, technician. Technicians see their work; they do not see the reports containing every customer address and completion note.
Ingestion
Connect the mailbox you already use
IMAP is the launch path and works with any provider, including Gmail with an app password. Point it at the address your customers already email and requests start becoming jobs.
Gmail over OAuth is in beta. It works, but Google's restricted-scope verification is still in progress, so a connected Gmail account needs reconnecting periodically until that clears. We'd rather tell you that now than have it surprise you in week two.
Processed mail is labelled, never deleted and never moved to trash. The legacy system deleted what it consumed, and one downstream failure destroyed a customer's request with nothing to replay. That is not a mistake this rebuild is allowed to repeat.
Triage
A suggestion, never a decision
The model reads the message and fills in what it can find: a summary, an urgency, the site, the contact and the trade. Every one of those lands in a normal editable field.
Nothing is sent to a customer off the back of it. Nothing is auto-assigned. If the extraction is wrong, you fix the field — and the original email is sitting right there to check against.
Inbox · unread
- From
- building.manager@example.com
- Subject
- Urgent - water coming through ceiling L2
Water is coming through the ceiling tiles in the level 2 kitchenette, has
been going since about 7 this morning and there's a bucket under it. Tenant
is on 021 555 0142 if you need access. Can someone come today please.
Regards
Facilities · 128 Example Street, Te Aro
Water ingress through level 2 ceiling
Active leak above the level 2 kitchenette since ~7am, contained with a bucket. Same-day attendance requested.
- Site
- 128 Example Street, Te Aro
- Contact
- 021 555 0142 (tenant, for access)
- Reported
- Around 7:00am today
- Trade
- Plumbing — leak / water ingress
The original email is kept in full, attachments and all. Every extracted field is editable — you have the last word, not the model.
Mobile
What the technician sees
An iPhone app with today's jobs, the full detail of each one, the photos that came in with it, and a status they can move in three taps from the back of the van.
Firms migrating from the legacy system keep the app they already have: the old API still answers, byte for byte, so nobody has to be retrained on the day you switch the office over.
iPhone only for now — Android is below.
Not yet
What we're working on, and what we're not
None of this exists today. It is listed because people ask, and because the honest answer to "do you do X" is more useful than a page that implies you do. Nothing here is a delivery commitment or a date.
Xero integration
Push completed work through to invoicing instead of exporting a CSV and re-keying it. The most-asked-for thing on this list, and not built yet.
Android app
Today the field app is iPhone only. An Android crew can still use the web app on a phone browser, but it is not the same experience and we will not pretend otherwise.
Gmail out of beta
Google restricted-scope verification, including an annual third-party security assessment. Under way. Until it lands, IMAP is the path we recommend.
Scheduled maintenance
Recurring jobs that raise themselves — backflow tests, filter changes, the annual round.
Customer portal
A place for a property manager to see their own jobs without emailing to ask.
Annual billing
Monthly only right now. An annual option with the usual discount is on the list.
See it against your own inbox
Connect a mailbox on the trial and watch a week of real requests turn into jobs. That is the only demo that ever convinces anyone.