Your clients are the other departments
Finance, operations, and HR all send work your way through whatever channel they like. Certainty HelpDesk gives them one door and gives you a defensible queue.
The three things that go missing
Requests arrive by email, chat, a tap on the shoulder, and a spreadsheet.
Whoever escalates hardest gets served first, and the roadmap absorbs it.
You are asked what the team delivered and you go looking for evidence.
One intake route instead of five chat apps
Every department raises requests in the same place, and each one gets an ID before anyone triages it. Unsorted work surfaces first, oldest at the top, so nothing sits waiting to be noticed.
- One door for finance, operations, HR and everyone else
- Unsorted requests surface first, oldest at the top
- The requester can see it was received without asking
Triage queue
Priority set by your team, visible to theirs
You decide what is high, and the department that asked can see the decision without a meeting about it. There is no hidden queue. Where AI triage is enabled and a request is unambiguous, it is filed under the type the requester already chose; anything less clear waits for a person, with the reasoning shown.
- Priority set by your team, visible to the requester
- Overdue grouped as overdue, not by creation order
- Internal tasks and notes stay internal
Payroll export needs a new column
Retire the old asset spreadsheet
A record of what you shipped
When the review comes round, the answer is a query rather than an archaeology project. Every closed record carries who did it, when, and which department asked.
- Append-only history for reporting and review
- Closed records keep who fixed it, when, and what changed
- Maintenance records show the commitments you are carrying
Renewal email had the wrong date
The parts that carry this kind of work
Every tracker, list and calendar reads the same record, so the ticket you close is the task that disappears.
AI sorts the obvious, people decide the rest
Where AI triage is enabled, every client request is read on arrival and given a type. When that reading matches what the client already said it was, it is filed straight away and stamped as sorted by AI. When it does not, or when it needs a person for any other reason, it is held with the reasoning attached, so whoever picks it up starts from an argument rather than a blank form. Pre-triage commenting means the conversation starts the moment it lands. The feature is enabled per deployment, on request.
- auto-filed on agreement
- held with reasoning
- sorted-by-AI provenance
- enabled on request
Tasks and trackers
Every project gets a task board, a column per status and a card you drag between them, with subtasks and more than one assignee where the work needs it. My Issues, Personal Tasks and a Calendar tab cover your own week, and server-side pagination means a thousand-item project opens as fast as a ten-item one.
- subtasks
- multiple assignees
- timezone-correct overdue
- server-side pagination
Deadlines and the diary on one grid
Every dated work item, every meeting and every team day on one shared month grid, with finished items struck through and Malaysian and Singaporean public holidays sitting in amber. Attendees read Free, Busy, On leave or Holiday while you are still choosing the time, and reminders go out about fifteen minutes ahead and again on the day.
- MY and SG holidays
- free and busy
- recurring events
- reminders
Attendance, leave and claims
Staff check in and out from Home with In office or Remote marked, ask for days off, and claim back what they spent with a receipt on every line. The admin panel shows today's attendance, decides leave, and approves then pays claims with a payment reference.
- check in and out
- leave requests
- receipts per line
- MYR, SGD, USD
Per-item visibility
Sensitive records stay hidden from anyone without rights to them. That holds in search, in counts, in dashboards and in notification fan out, not only in the list view.
Every edit is versioned
Content revision history on work items. If the scope quietly changed on Tuesday, the record says who changed it, what it said before, and when.
A team layer with no leaderboard
A feed your team writes to, with images, video, tags and mentions. Peer kudos are budgeted two a month and permanent once given, streaks are capped to the current month with weekends, public holidays and approved leave neutral, and the team view reports totals that are never broken down per person. None of it is visible to a client.
- permanent kudos
- month-capped streaks
- aggregate-only totals
- internal only
Walk your own pipeline with us
Bring one messy client project. We will set it up live on the call and you can see whether the shape fits how you actually work.
partnerships@dhcertainty.com