For ADUN service centres
Every constituent who walks in stays on the record — not lost in a file.
A constituent walks into your pusat khidmat with a problem. They scan a QR, tell you what happened in their own language, and walk out with a reference number. Your office sees it the same second — open, in progress, or settled with the date it closed.
50 cases free. No card needed.
Your reference number
SSA-2608-0412
- Category
- Infrastructure & public facilities
- Received
- 14 August 2026
- Status
- Settled
- Date settled
- 27 August 2026
“The streetlight on Jalan Melati 3 has been broken over a month. The area is dark and unsafe for children walking home from afternoon school.”
The problem
The work gets done. The record of it does not.
Most pusat khidmat run on a buku 555, a WhatsApp group, and the memory of whoever was at the counter that morning. That works right up until it does not.
Cases fall through the gaps
A case comes in on Friday evening. The officer who took it is on leave Monday. Nobody else knows it exists. The constituent comes back in three weeks and has to tell the whole story again — to someone who has no record of the first visit.
No proof of the work
At the end of the term, an ADUN who genuinely settled two thousand cases has no way to show it. The evidence is in a stack of exercise books and a WhatsApp group that scrolled past months ago.
Constituents left guessing
“Has it been settled yet?” is the hardest question at the counter, because usually nobody can answer it. The constituent is left guessing, and the office is left defending work it actually did.
None of this is a failure of effort. Service centre staff work extremely hard. It is a failure of record-keeping — and that is a solvable problem.
The solution
One QR at the counter. Everything else follows from it.
The design constraint was simple: a constituent who has already waited an hour will not download an app, create an account, or remember a password. So they do not have to.
Scan
Fill in the form
Get a reference
Through to settled
Four languages
Bahasa Melayu, English, 中文 and தமிழ் — labels, categories, helper text and error messages all switch together. The language they chose is recorded on the case, so you know who can call them back.
12 real categories
Drawn from what actually walks in: cash aid, streetlights and drains, school fees, OKU cards, JPN paperwork, flood relief, complaints against agencies. Not a generic helpdesk taxonomy.
No duplicate files
A returning constituent is matched on their IC. You see their history immediately rather than creating a second file for the same person.
For the rakyat
Treated with respect, not told to come back later.
The person at the counter is often having one of the harder weeks of their life. A bill they cannot pay. A child with no birth certificate. A roof leaking since the last storm.
What they need from the process is not efficiency for its own sake. It is the sense that they have been properly heard, and that something will actually happen.
Their own language
A Tamil-speaking pakcik reads the form in Tamil. A Chinese auntie reads it in 中文. Nobody has to fill in an official form in a language they are not confident in.
A reference number
Proof they were here, and something concrete to quote when they follow up. No more “I came last month and spoke to a man”.
Privacy respected
Their IC and address go to that one pusat khidmat and nowhere else. They tick a consent box that says exactly that, in their own language.
No repeating themselves
Come back six months later and the office already has the file. They pick up where it left off instead of starting again.
For the ADUN
The work you already do, finally on the record.
You are not being asked to work differently. You are being given proof of the work you have been doing all along — the kind that survives a staff change, an audit, and an election.
Reports for the DUN
Settlement rate, median days to close, breakdown by category, district, age band and gender. The kind of report that takes a week to assemble by hand, ready in a click.
A daily case board
Filter by today, this week or this month. See what is open right now, what has been sitting over thirty days, and who is handling it — before a constituent has to ask.
Several branches
Each branch has its own QR, its own case numbering and its own plan. Data never mixes between them, so a branch manager sees only their own.
“How many cases did we settle this year?” should take five seconds to answer, not five days.
Data protection & PDPA 2010
You hold the data. Not us, and not the ADUN next door.
This system holds IC numbers, home addresses and written accounts of personal hardship. Under the Personal Data Protection Act 2010 you are the data controller and WakilDesk is the processor — we hold it on your behalf, not for our own use. Here is exactly how that is enforced.
Every centre is walled off
Every constituent and case row carries the id of the centre that collected it. Ownership is part of the database query itself, not a check performed afterwards — so a request for another centre's data matches nothing and returns “not found”. The data never loads at all.
Two ADUNs, two separate files
If the same person visits two different pusat khidmat, they become two independent records. Neither office can see the other's file. This is deliberate: what a constituent asked one representative for is not another representative's business.
Even our admins cannot read it
Our platform panel shows accounts, plans, revenue and case counts. It has no constituent browser and no case viewer — not restricted, simply not built. If we ever need a record to help with a support case, we ask you to export it and send it.
Consent, recorded
Every submission carries an explicit PDPA consent tick, shown in the constituent's own language and naming your centre specifically. The consent is stored against the record, so you can show when and how it was given.
Append-only audit trail
Every export, plan change, deletion and administrative action is logged and cannot be edited. If anyone ever asks who downloaded what and when, the answer exists.
Billing never holds data hostage
A centre that stops paying drops to the free tier. The dashboard, search and both exports keep working — only the monthly intake allowance changes. Your constituents' records remain yours.
Minimal data, by design
The form asks for what is needed to act on the case and nothing more. Date of birth and gender are derived from the IC rather than asked for separately, and the visitor's IP address is stored only as a salted hash for spam control.
Pricing
Priced per service centre.
Per centre, per month, on the number of cases collected. Each branch has its own plan and its own limit — nothing is shared, so a busy branch never eats a quiet one's allowance.
Trial
per service centre
50 cases a month
- 50 records / month
- QR intake form
- Search, filter & Excel export
- Duplicate IC detection
Starter
per service centre
1,000 cases a month · 10 sen each
- 1,000 records / month
- Everything in Trial
- Visit history per constituent
- Email support
Growth
per service centre
5,000 cases a month · 5 sen each
- 5,000 records / month
- Everything in Starter
- 5x the Starter allowance for 2.5x the price
Scale
per service centre
10,000 cases a month · 4.5 sen each
- 10,000 records / month
- Everything in Starter
- Lowest cost per record
- Priority support
Every plan includes all four languages, Excel and PDF export, and the same data protection. Cancel any time — your data stays yours.
Common questions
What people ask before signing up.
Something else on your mind? Talk to us before you register — we would rather you knew exactly what you are getting.
Do constituents need to download an app?
No. They scan the QR with their phone camera, the form opens in their browser, and they submit. No app, no account, no password. The whole point is that someone who has queued for an hour is not then asked to create a login.
Can it be used in Bahasa Melayu?
Yes — and English, 中文 and தமிழ். The first thing a constituent sees is a language choice, and every label, category and error message changes with it. The office still reads everything in one language on the dashboard.
What about older people who are not comfortable with phones?
Your staff can fill the same form on a counter tablet, or use the short link on any browser. Nothing about the system assumes the constituent is comfortable with technology — it assumes they have a problem and limited patience.
Is constituent data safe under the PDPA 2010?
Every constituent and case row is scoped to one pusat khidmat and never leaves it. The same person visiting two ADUNs becomes two independent records that cannot see each other. Consent is captured at submission, and every export is written to an append-only audit log.
Can WakilDesk staff read my constituents' cases?
No. The platform admin panel shows accounts, plans, revenue and counts — it has no constituent browser and no case viewer at all. You are the data controller; we are the processor. If we ever need a record for a support case, we ask you to send it.
What if I run more than one service centre?
Each centre gets its own QR, its own case references, its own plan and its own monthly limit. Nothing is pooled, and one branch hitting its cap never affects another.
Can I export to Excel for DUN reports?
Excel and PDF, both honouring whatever filters you have on screen. The Excel file has a summary sheet with settlement rate and average days to close; the PDF is formatted to hand across a table.
What happens if I stop subscribing?
Your data stays. A cancelled centre drops to the free tier — the dashboard, search and exports keep working, only the monthly intake allowance changes. Nobody's constituent records are ever held hostage over billing.
Try it with one QR poster.
Sign up, choose your DUN seat, print the QR and put it on the counter tomorrow morning. Fifty cases free — enough to see whether it actually helps your office before you pay anything.