A queue that tells you whose move it is, remembers what each request cost you, and lets the person who asked follow it without an account. The other eight are somewhere else, and that's fine.
Your work doesn't arrive because you sat down and planned it. It arrives by text, by email, by voicemail, by somebody catching you in a parking lot — and a to-do list models the wrong moment entirely.
So you get a helpdesk built for a team with a manager, or a task app that can't tell the difference between something you chose and something you owe somebody. Neither one knows that seven of your twelve open things are with other people.
The most valuable thing software can tell a one-person practice is whose move it is.
Yours to move · waiting · comes back later · sorted. Twelve open things become four you can actually do this morning.
StandardOn a person, on a date, or on something arriving. A date leaves the pile and comes back the morning it matters.
StandardOne thread with their words, your replies and your private notes. They answer from their inbox or a link — no account, ever.
StandardThe tasks, the hours, the miles, the note. Which is how you find out one client is 40% of your unbilled time.
StandardNothing here turns red for getting old, nothing is labelled overdue, and nothing closes itself. A request sitting twelve days might be sitting in somebody else's backlog — and that isn't your failure.
Two kinds only: something's broken, or I need something. Nobody has ever meaningfully filled in a priority dropdown.
A helpdesk would be. This is a list that knows who asked and when — which you already keep, badly, across your inbox, your messages and your memory. The overkill version has SLA clocks, priority matrices, satisfaction surveys and an agent dashboard. None of that is here, and none of it is coming.
What you get instead is the one question a solo practice actually needs answered every morning, and a record that survives the conversation.
No response targets, no breach colour, nothing labelled overdue. You are not answering to a service desk manager.
Nothing closes because it got old. Old is not the same as done, and pretending otherwise is how a queue becomes fiction.
Whoever asked gets one link showing one thing. No logins, no password resets, no support load about support.
That's Ground Control, +$12 — a public page, a per-app embed, or a private link per client. Without it, you raise every ticket and the conversation is still fully two-way.
From their inbox, or on the link — both land on the same ticket. Replying is standard; it just needs a name and an email on the ticket.
If it arrives twice it becomes a second line on the ticket you already have. If you notice later, you fold one into the other — nothing is deleted and the old link keeps working forever.
One click makes a task, a loose task, an estimate line, a trip or a note — and the thread home survives in both directions, so an invoice line can point back to the sentence that caused it.
The useful spine of it, yes — incident and request, and with Ground Control, change and release. Written by somebody who has run those professionally since 2007, with every committee removed.
Yes — the kinds, the states, the word “ticket” itself, and your own fields throughout. One setting also flips every label to ITIL's own words for practices whose auditor expects them in writing.
One line, eight seconds, and in three weeks you'll know exactly who asked and when. Two weeks free, no card, and if you go quiet you simply stop.