A helpdesk that closes tickets and ships the work
Tickets, tasks, chat and a client portal in one place, so a request never gets re-typed into a separate project tool.
Permissions enforced on the server. Never a menu trick.
One request, four honest states
Requests that live in chat threads have no number, no owner and no memory. In Certainty everything is a record, so everything is traceable.
The client raises it
REQ-041 · 09:41You give it a type
ISS-104 · 11:02Someone owns it
Owner: Abdullah · 08:15It closes with a trail
Closed · 7 Auga stat tile is also a filter: click the number, get the list
Everything attaches to the record
Set by your team, shown in the client's own view.
Privacy holds in search, counts, dashboards and notification fan-out.
Where AI triage is switched on, it files the clear ones and holds the rest, with its reasoning, for a person.
Shared ownership is how things quietly stop moving.
live chat on real sockets: the socket is the source of truth
Farah: attaching the screenshot from the client
ISS-104: export returns an empty CSV on Safari. Updated by Shahin
Project Beacon · TSK-233
Shahin asked to join. Approve or decline
real web push that lands on iPhones, with email as the fallback
The call is part of the record, not a link beside it
Meetings run in the browser, with a lobby, guests, screen share and live captions. Deadlines and meetings share one grid, and the public holidays for Malaysia and Singapore are already on it.
one grid: what is due, and what the team has on
attendance, transcript, recording, write up, and the work it changed
A lobby, and guests who need no account
Anyone with the link gives a name, checks their camera and waits to be let in. Fifty fit in a call, one screen holds the stage at a time and can be taken over with a confirmation, and the owner decides who may admit and who may share.
Captions that do not depend on the browser
Where a browser cannot caption, the words are written down on the device itself and the audio never leaves it. The host decides whether a transcript is kept and whether a write up is made.
One record per occurrence
A repeating meeting keeps one join link and still gives every run its own transcript and its own summary, so last Tuesday's decisions are not folded into three months of them.
Recorded by the host's browser · No server-side recording
Four portals, one sign-in, permissions you can see
Client, team, admin and auth: every view enforced by roles on the server, not hidden menus.
| Resource | Read | Write |
|---|---|---|
| Requests | ||
| Issues & FR / CR | ||
| Tasks & subtasks | ||
| Members | ||
| Access requests | ||
| Announcements | ||
| Leave requests | ||
| Error log | ||
| API tokens |
Client portal
Raise requests, upload files, watch progress, chat with the team.
Team workspace
Triage, trackers, subtasks, calendar and chat in one place.
Admin panel
Roles, orgs, projects, members, tokens and access requests, editable without a deploy.
Auth gateway
Microsoft sign-in, with module switching that keeps your session.
Installable on iOS & desktop today · Native apps Soon
Permission changes reach a page you already have open. No reload.
Fully managed. Nothing to patch at 2am.
Your helpdesk is agent ready out of the box
Certainty ships its own MCP server. Any agent can file issues, sort a backlog, assign work and track the time it spent, under exactly the permissions a person would get.
- Same permissions as a person. A token carries its role
- Agents write, not just read. File, assign, move statuses
- Every action is attributed in the same revision history
- Time too. Start a timer, stop it, log what it spent. A timer an agent starts closes itself after two hours, and the entry waits for a person to confirm it.
over forty tools, one permission model
Issues mirror one-way to GitHub. Certainty stays the system of record.
Teams who owe someone an answer
Built for teams who deliver work for other people, and get asked where it stands.
Digital agencies
Many clients, each one convinced they're the only one. Every client gets their own view of their own records.
How they use it →IT teams & MSPs
Inbound breakage, and a record of what you did about it. The window, the allowance and every visit, on the project rather than in somebody's memory.
How they use it →Software studios
Bugs, asks and "small changes" in one honest queue, each with its own lane and its own commitment.
How they use it →Consultancies
Billable work that has to be evidenced, not remembered. Time is tracked against the record that caused it.
How they use it →Internal ops teams
Your clients are the other departments. One intake route instead of five chat apps and a spreadsheet.
How they use it →NGOs & public sector
You answer to funders, not just users. Append-only history is the only evidence an auditor accepts.
How they use it →Pricing is a conversation, not a slider
Team size and module mix change the number. Twenty minutes on a call gets you a real answer, with your own workflow in the product.
no card, no trial timer, no sales sequence