A ticket desk shaped like your process
Helpdesk products make you adopt their vocabulary. On Faldaro a Tickets folder holds forms you designed, moving through states you named, routed by rules you wrote — and all of it changes the day your process does.
-
Intake that asks the right questions
Conditional fields mean a billing question and an outage report ask different things — one form, no irrelevant boxes, no “see attached” tickets missing the one detail you needed.
-
States your team already uses
New, Triaged, Waiting on customer, Resolved — whatever your desk actually says. Rename a state or add one in the browser; the workflow is configuration, not code.
-
Notifications that close the loop
Acknowledgement on submission, updates on transition, a resolution note from a template when the ticket closes — each one a workflow effect you configure once.
-
A desk you can answer for
Every ticket keeps its history: who triaged it, when it moved, what was said in the record. The audit log is append-only, so the answer to “what happened here?” is always the truth.
-
Requesters who never ask “any update?”
Every ticket can carry a “track your request” link — merged into the acknowledgement email — showing its current stage and reference number. Switch on the portal and requesters see all their tickets from just their email address, no account, no seat.
-
Triage on a board
The queue as a board whose columns are your own states: drag a ticket from New to Triaged and the workflow move fires, guards intact. The same records, as a table, calendar or cards when the board is the wrong lens.
Built from the same parts as everything else: the builder, workflows and the assistant for the “show me unresolved tickets from last week” moments.
Start from a free template: Contact us, Support request or Maintenance request. Each opens as an editable draft in your own account.
Questions
Support on Faldaro, plainly
Can customers raise tickets without logging in?
Yes — publish a public link for the intake form. Anonymous submission is throttled by default, and where your operator has configured a captcha it sits in front of every public form. Attachments work, and the customer sees only the form: never your routing rules, states or internal fields.
How does a ticket reach the right person?
Workflow rules assign from the submission’s own answers — product area, severity, region — and notify the assignee. Reassignment is a transition like any other, gated and audited.
Does it talk to the rest of our stack?
Transitions can call your webhooks (against operator-allow-listed hosts) and send tickets to Zapier, which reaches the rest. Slack messages, CRM records and sheets are a rule, not an integration project.
Stand up your desk today
An intake form, four states and two notification rules make a working desk — the Free plan covers all of it.
No card required.