Intake & Triage
One broken lift is one job. Not twelve.
When the same problem is reported again and again, Laksana suggests the match, your staff link the reports to one work order in a click, and every reporter is kept informed on the channel they used. Every report stays on record, linked to the job.
- 12 reports · 1 lift · WO-1042
- Suggested match · staff decide
- WhatsApp · Telegram · Email
The problem
One broken lift, twelve tickets. The technician opens twelve jobs.
Lift Block B rosak lagi!
Twelve residents, twelve reports. Each message becomes its own ticket, and the count looks like twelve faults when there is one.
Did someone already report the lift?
Nobody can see the first report. A resident has no way to check, so they report again, and the queue grows.
Lift dah okay ke? Tak ada orang bagitau.
Only one reporter hears back. The job closes for the first reporter and the other eleven are left chasing an update.
How it works
Twelve reports in. One job out. Every reporter told.
1
Suggest the match
Reasons on the card. Open reports at the same site that share an asset, arrive minutes apart or use overlapping wording are suggested, and staff decide.
2
Link to one job
One work order. Staff link the reports to a single work order in a click. Every report stays on record, linked to the job.
3
Update every reporter
Own channel. Reporters attached to the job are told when work starts and when it is done, on WhatsApp, Telegram or email.
Key benefits
Suggested, never silently merged
A person decides. Matching open reports at the same site are suggested with the reasons on the card — same asset, minutes apart, overlapping wording. A person decides, every time; nothing is auto-linked at any confidence.
AI catches the awkward matches
Cross-language matches. Turn it on and the assistant proposes matches exact rules structurally cannot see — the same fault reported in Malay and English, filed under different categories. Every AI suggestion carries a visible badge and plain-language reasons, and your staff decide, exactly like every other match — nothing is ever auto-linked at any confidence.
Measured before it reached a resident
Tested on real pairs. Before it shipped, the AI matcher was run against a 40-pair labelled test of real Malay/English duplicates: it caught every genuine duplicate in the set, including all 6 that crossed categories the deterministic matcher cannot compare, and got it right 20 times out of 21 when it flagged a pair. A measured result, re-checked before any model change goes live.
Every reporter stays in the loop
Everyone hears back. Reporters attached to a job are told when work starts and when it is done — on WhatsApp, Telegram or email, each on their own channel, with a one-tap unsubscribe. A linked report never reads "closed" while the work is undone.
Stops duplicates at the door
Caught at submission. On the resident helpdesk form, matching open issues are shown before submission — "someone already reported this, want updates instead?" One tap follows the existing job; no reporter details are ever shown.
Works With
What feeds and follows a linked job
Issue Reporting
The intake. Every report from WhatsApp, QR or portal lands in one register before it is matched.
AI Classification
Read on arrival. Type, urgency and likely asset are read before staff review a match.
Resident Helpdesk
Caught at submission. The helpdesk form shows matching open issues before a resident submits.
Work Orders
One job to run. The linked reports hang off a single work order with one owner and window.