€125/mo, on top of your plan
Helpdesk
One inbox, every channel, every SLA.
Customer support run end to end: requests from email, web forms, the API, your app, Slack, WhatsApp and SMS land in one ticket inbox, and every reply goes back the way it came. SLAs, automations, macros and satisfaction surveys run on top.
- Inbound channels
- 7
- SLA metrics
- 3
- Automation actions
- 10
- Permissions
- 12
One inbox for every channel
Email, the web form, the public API, the in-app button, Slack, WhatsApp and SMS all feed one queue. Each request becomes a ticket, and each reply goes back through the channel it arrived on.
- Email threads on a signed reply token first, then the standard headers, and auto-replies are held back so two systems never loop
- WhatsApp keeps to the 24-hour service window and sends an approved template outside it
- A text that says STOP is recorded, and no further SMS goes to that number
- Every inbound webhook is signature-checked before anything is written
- Channel credentials are encrypted at rest and never shown again
One conversation per ticket
Agents work each ticket as a single thread: public replies the requester sees, and internal notes only your team sees.
- Public replies and internal notes, with attachments, in one timeline
- An internal note can never become public: the ticket itself refuses it
- Six statuses from New to Closed; by default a reply to a closed ticket opens a linked follow-up instead of reopening it
- Tags, typed links between tickets, and a permanent merge for duplicates
- An append-only activity feed of who changed what, and when
SLAs measured in your hours
Policies set first-response, next-response and resolution targets per priority, measured against your business-hours calendar or around the clock.
- Calendars with your own timezone, weekly hours and holidays
- Each target can pause while the ticket waits on the customer
- Due times recalculate when the priority or the status changes
- A breach notifies the assignee and your escalation role
Triggers, automations and macros
One set of ten actions drives three tools. The actions set the status or priority, assign, tag, reply, add a note and notify.
- Triggers react as a ticket is created or updated, with a loop guard built in
- Time automations act on tickets that have waited too long
- Macros apply a canned reply and a status change in one click
Satisfaction surveys
A day after a ticket is solved, the requester gets a short survey. They can answer for 28 days, even after the ticket closes.
- Good, neutral or bad, with an optional comment
- Answered on a public page, with no account needed
- Scores and comments reported in the panel
Help from every page
A floating support button sits on every page of the panel, the sign-in screen included, so nobody has to hunt for where to ask.
- Signed-in users send a request as themselves
- Signed-out visitors leave an email address so the reply can reach them
- Three dashboard widgets: open tickets, the status mix and SLA health
- With Customers installed, a requester links to the shared customer record; without it, the Helpdesk runs on its own
- With Chat installed, the Helpdesk menu opens it in one click
Worth knowing: There is no knowledge base, and nothing balances tickets across agents on its own. Assignment is by hand or by your own trigger rules.
What every module inherits.
- Installs from the marketplace with no redeploy — the menu and the permission list update immediately.
- Creates its own tables, in its own schema, inside that customer's database.
- Packages are cryptographically signed when they are built, and the signature is checked before the host unpacks one.
- Uninstall switches a module off and keeps its data. Dropping the tables is a separate, deliberate choice.
Want to see Helpdesk running?
Thirty minutes, a live workspace, and an honest answer about what each module does and doesn't do yet. Missing a module? A custom build is a fixed-scope project, from €25.000.
Book a call