Contact · Helpme.software
One address, and no form to fill in first.
[email protected] is the whole contact surface. There is no form on this page and no lead capture behind it: this marketing site stores nothing about you, which is easiest to guarantee by not asking.
A support-software company that makes you fill in a form to ask a question has already told you something about how it thinks.
What to say, so the first reply is useful
Four things, and you can skip any of them.
✓Who answers support today
A front office of a dozen people with other jobs, one IT director, a district team, a studio operations desk. This is the single most useful sentence, because it decides whether the per-organization pricing shape is the point or an afterthought.
✓What breaks now
Tickets answered from personal mailboxes with no record. A promise made on the phone that nobody can find. A roll-up the board does not trust. A parent asking twice because the first request went nowhere. The specific failure is more useful to us than a feature list.
✓Which capability decides it
If email-to-ticket intake, automation rules or satisfaction reporting is the thing that decides your purchase, say so first — all three are on the built-not-switched-on list, and you deserve a date and a caveat in the first reply rather than a demo that skirts it.
✓Whether a data review is the gate
If a data-handling question or a district review stands between you and a pilot, lead with it and we will too. The privacy and data page is the short version and it is written for someone who will ask what the system CAN do, not what it is set to.
Which conversation
Pilot, review, licensing — or a correction.
A pilot. One queue, one term, every guarantee on the site holding exactly as it would at full scale. We will tell you which parts of the category are not switched on here before you commit a term to it.
A data-handling review. Put “review” in the subject and it gets routed ahead of sales. We would rather answer a counsel’s question in writing than schedule a call about it.
Licensed or self-hosted. The engines are ours to license. Tell us which held capabilities you need enabled and we will talk about a schedule rather than a wish.
A correction. If something on this site is wrong — a comparison row, a capability we have described too generously, a held item that has quietly switched on — we want to know. Accuracy on this page is the product.
Helpme field guide
A product question needs a result and a boundary.
A useful inquiry can be brief while remaining specific. In this fictional example, an adult operations colleague writes: “We need to record administration-screen reports and manually assign them. We also need to understand whether the escalation result changes the saved ticket. Your guide says persisted:false. Please clarify that boundary.” The question identifies a job, an expected result and the exact uncertainty.
That is more useful than an unexplained request for every feature. It does not require a real ticket export, a contact list or a detailed incident history. The writer can describe the operation with invented text and still ask a precise question about creation, assignment or status. Keep information that belongs in an established operational support process out of this initial product inquiry.
If the question concerns a report, name the measurement rather than asking whether analytics exists. Volume, backlog, response time and satisfaction trend are different outputs. The current routes supply different answers for them. A question about first-response performance should acknowledge the null timestamp projection rather than assume that a chart label proves a working measurement.
If the question concerns a refusal, preserve the condition in the description. Open to close is different from resolved to close. A manual assignee is different from automatic agent selection. An accepted calculation is different from a saved response. Those distinctions let the recipient answer the actual product question without inferring which action the writer intended.
A contact link is only the contact surface on this page. It does not file the fictional ticket, guarantee a reply, create an account or accept payment. The page offers no live checkout. If the inquiry concerns active operational work, use the appropriate channel already established for that work and keep its record references within that process.
The practical objection is whether a writer must understand every implementation term first. No. An ordinary sentence such as “I need to know whether this change is saved” is enough. The guides provide the terms for readers who want them, but the purpose of contact is to clarify a concrete result, not to test the reader's technical vocabulary.
Before you write
Two things worth knowing first.
There is no live checkout on this site and getting in touch does not start a billing relationship. No card, no charge, no contract signed on a web page. The getting-started page sets out the four steps.
And some of what a help desk usually does is built here and not switched on: email intake, cross-channel dedupe, automation rules, AI triage, deflection analytics, agent presence, audit replay. Corridor up-routing is registered and gated off by default. Satisfaction and escalation both compute correctly and do not persist. Ask which side of that line your requirement falls on; we will tell you straight, and we would rather lose a deal on it than win one.