Getting started · Helpme.software
There is no sign-up form on this page, and that is the honest option.
Self-serve tenant provisioning is not built. We could put a form here and email you afterwards, but a form that does not create an account is a form that lies about what it does. So: a conversation first, and a plain account of what runs.
The desk itself is real — durable tickets, a scope-walled queue, canned replies, a family portal, an SLA grid. Several ordinary expectations of the category are built and not switched on, and you will hear which ones before you see a screen.
What actually happens
Four steps, and you can stop after any of them.
✓1 — Tell us the shape of the problem
Write to [email protected] with who answers support today, roughly how much of it there is, and what actually breaks — tickets answered from personal mailboxes, no record of what was promised, a district roll-up nobody trusts. One paragraph is plenty.
✓2 — A walkthrough that names the held list out loud
We show the live surfaces and we say the words “built, not switched on” about email intake, automation, AI triage and the rest, before you see them on a slide. You should leave the call able to repeat back which is which. If you cannot, we did it badly.
✓3 — A pilot on one queue
Almost nobody should start everywhere. Pick the queue that hurts — usually the front office or the family portal — and run it for one term. Every guarantee on this site (the schema wall, the scope wall, the suppression, the legal-move table) holds on one queue exactly as it does on all of them.
✓4 — Widen when the first one is boring
A second queue is a scope, not a second procurement. That is worth nothing until the first one is dull and reliable, which is the only honest signal that the thing works.
Four conversations, depending on who you are
School, district, studio, licensed.
School. The front-office queue and the family request portal. Unlimited staff accounts, because the point of the pricing shape is that everyone who helps is in the system rather than answering from a personal mailbox.
District. One school first, then the roll-up, so you can see what small-cell suppression does to your numbers before it is everywhere. We will also be explicit that the compliance percentage is not computed yet and volume and backlog age are.
Studio and services. Usually a scope-wall conversation: studio scope is separated from school scope at the same chokepoint that walls tenants, and a ticket can carry an opaque order or page reference without carrying a person.
Licensed or self-hosted. Which held capabilities you need switched on, and what that schedule looks like. The engines are ours, so this is an engineering conversation rather than a reseller one.
What starting does not involve
No card, no charge, no contract signed on a web page.
There is no live checkout on this site. Getting in touch does not create a payment, does not store a card, and does not commit you to anything. The pricing published on the home page is the planned launch tier, not a price you can be billed at today, and there is no payment surface inside the help desk at all.
And the part worth repeating before you spend a term on this: email-to-ticket intake, cross-channel dedupe, the automation rule engine, AI triage, deflection analytics, agent presence and audit replay are built and have no production callers. Corridor up-routing is registered and gated behind a flag that defaults off. Satisfaction responses validate and do not persist. SLA compliance is not computed — the response stamps ARE stored now, but the SLA projection does not read them yet. And the staff per-ticket read reaches across tenants because it runs in a system-lane transaction; that one is a defect we are naming, not a capability. You should hear all of that here rather than discover it in week two.