highlarge
Repair
Front office
Garretttoday
Features
Everything here is shipped.
No roadmap items dressed up as features. This is what is in the installer you can download today, screenshotted from a demo install.
The wall
The wall
The anonymised corkboard, open to everyone. Notes are sized by effort, coloured by priority and pinned by severity, and they grow as they wait — so a job that has been sitting for three weeks physically takes up more of the board than the one raised this morning. A big note can never be covered by a smaller one.
What it does not show: subjects, descriptions, names of requesters, or anything typed into the form. Anyone can read the wall without reading anyone’s business.
New in 1.6
Photos on every request
The request form takes up to ten photos or PDFs. Phones shoot straight into it, so the person standing in front of the jammed printer sends you a picture of the jammed printer instead of a paragraph describing it.
Images are shrunk in the browser before they upload — a 12‑megapixel photo lands as a few hundred kilobytes, which matters on a wifi network that is already the reason half your tickets exist.
- Up to ten photos or PDFs per request.
- Staff attach before‑and‑after shots to their own notes.
- Photos arriving by email are kept on the ticket.
- Never shown on the public wall — only staff on the ticket page see them.
normalsmall
Quick fix
Warehouse
Sam1 day
The wall stays anonymous: the photos live on the ticket, not the board.
Requests
The request form on the wall
The form sits directly under the board, so the pile is the first thing a requester sees. There is no account to create and no password to forget — anyone in the building can raise a request in about fifteen seconds.
Email and phone are both required, so every request can be followed up by whoever picks it up. Requesters get an acknowledgement, and can watch their own item move on the wall afterwards.
- No account, no login, no licence needed.
- Email and phone required on every request.
- Categories and departments are yours to define.
My wall
My wall — one board per person
Each agent gets their own board of exactly the work that is theirs, in the same visual language as the public wall. It is the day’s to‑do list, ordered by what is actually loudest rather than by what arrived last.
Dispatch
Dispatch — drag work between people
Every agent’s board, side by side, with a load meter under each name reading light, steady, busy or swamped. Hand a job over by dragging its note onto someone else’s board. The meter tells you what you are about to do to their week before you let go.
Email intake
Email intake
Connect any number of mailboxes — or just one folder inside a mailbox, if the helpdesk address is shared with other traffic. Microsoft 365 and IMAP/Gmail are both supported.
New mail becomes a ticket. The acknowledgement goes out from that same mailbox, so replies land where people expect, and every reply threads back onto the ticket by its [WW‑123] tag. Nobody has to be taught a new address.
- Microsoft 365 or IMAP/Gmail, one mailbox or many.
- Watch a whole mailbox or a single folder.
- Replies thread by ticket tag; acknowledgements come from the same address.
Projects
Projects
A project is a named piece of work with assignable tasks — and because those tasks are ordinary tickets, they show up on the wall like everything else. The office can see that the file server migration is real work and not an excuse.
- Progress, overdue items and load by person.
- Paste a list of steps and get a task for each line.
- Notifications to the manager as things move.
And the rest of it
Smaller things, all shipped, all in every download.
Recurring tasks
Standing work — backup checks, filter changes, the monthly patch run — appears on the wall before it is due, and counts toward load like everything else.
Per‑agent visibility
“Can see” controls what each person’s account shows them. A remote contractor sees only their own work; nothing else on the wall is theirs to read.
AI intake
Point it at a local model through Ollama, or at an API. It reads each new ticket and suggests — or sets, if you let it — category, priority, severity and size. Local models mean the text never leaves the building.
Remote access
One click gives you a test link for someone working from home. For a permanent address, a named Cloudflare tunnel with a login gate is set up from inside the app — and the app checks that the connector is running and the hostname answers from the internet, so you know it is healthy rather than hoping. Local Pro.
Updates, backups, licence, Help
Updates within your version download and install themselves. Backups run nightly. The licence is a file, checked offline. Help is built into the app, not on a website you need signal to reach.
Runs anywhere you have a spare machine
A Windows installer, a Linux tarball with a systemd installer (x64 and Raspberry Pi), or a Docker image. Same app, same data, three ways in — and whichever you pick, the data stays in the building.
Editions enforced in the app
Your key carries the edition, and the app holds the line on staff accounts and mailboxes. Moving up a tier is pasting a new key under Admin → License — no reinstall, no migration, nothing to redo.
What it is not. WorkloadWall is not a Jira or Zendesk replacement for a support team of fifty, and it is not a field‑service app — there is no scheduling, quoting or invoicing, and none is planned. It is a wall with a queue behind it, for a department of one to ten.