Delivery · Support & Helpdesk
Your customer raises the ticket. They see theirs, and only theirs.
Included from Growth upward.
Support arrives by email, on WhatsApp, and through whoever the client has a phone number for. Nothing is counted, so nothing improves.
What it does
Tickets, from the client's own portal.
- 01
Tickets against a client and a project
Raised internally or by the client themselves, and attached to the account they belong to.
- 02
A portal that cannot overreach
A client account raises tickets against its own account, whatever it sends in the payload. Scope is taken from the session, never from the request.
- 03
Free for the client
Portal accounts do not consume a paid seat, so there is no reason to keep customers out of the system.
For example
Acme raises a ticket themselves, at no cost to you
- 1Acme's project manager signs into their portal and raises a ticket.
- 2It is attached to their account whatever the request payload says — scope comes from the session, never from the request.
- 3They see their own tickets, invoices, contracts and projects. Nothing about another client, nothing internal.
- 4Your team triages, assigns and works it against the client and project.
- 5Their portal account costs nothing and never consumes a seat.
Support stops living in individual inboxes, which is the only condition under which it ever gets measured.
How it runs
In, through, out
A client raises a ticket in their portal
It is triaged, assigned and worked
It closes against the account, and counts in the reports
Support stops living in individual inboxes, which is the only way it ever gets measured.
It does not work alone
What Support & Helpdesk is connected to
The point of one set of records is that these are not integrations. They read the same rows.
Problems it solves