Support Portal
The one public page: what the unit handles, what evidence to gather first, and the consent notice.
Citizens report from the messaging app they already use. Officers triage, assign and close from one console. Every action is written to an audit trail that nobody can edit afterwards.
Bilingual বাংলা / English · deployed inside the agency’s own boundary
Public agencies that take complaints from citizens and have to show, later, exactly how each one was handled.
A citizen messages the official number, or follows a one-time secure link into a longer web form with evidence upload.
A numbered case, a bilingual status message at every change, an enquiry report, and a complaint document as PDF.
One complaint record behind all three surfaces, an SLA clock on every case, and audit logs nobody can edit.
Every complaint enters through a citizen surface and is worked in the officer console. All three write to the same record, so the citizen’s status message, the officer’s timeline and the audit log always agree.
The one public page: what the unit handles, what evidence to gather first, and the consent notice.
Bilingual guided intake inside WhatsApp, from consent through to an instant complaint number.
A one-time secure link for longer reports, with evidence images and supporting case files.
A citizen can ask where their complaint stands at any time, in either language, from either surface.
Volume, disposal and ageing across the whole caseload, by category, channel and district.
The triage workbench: every incoming complaint, tinted by how long it has been waiting.
Each complaint arrives with a proposed category, severity and disposal for an officer to accept or override.
The assigned officer works the case and files a report; a supervisor accepts or returns it.
A formatted complaint document, generated in Bangla or English and printed to PDF.
Officers, users, roles, citizen blocking, and the record of who changed what.
Access and case actions are both logged, and neither log can be edited from the console.
Report summaries for oversight, exported without leaving the console.
Four steps from first message to assignment. Each one names the surface where it happens, and each produces something the citizen can see.
The citizen messages the unit’s official number and chooses guided chat intake or a secure web link.
A guided in-chat form, or a time-limited web form that accepts evidence images and supporting case files.
A complaint number is generated straight away and returned in both languages, ready to quote later.
The case lands on the board, AI proposes category, severity and disposal, an officer is assigned and the SLA clock starts.
Most people will not install anything to file a complaint, and many will not use a desktop browser. Intake runs inside WhatsApp, with a time-limited web form for the longer reports that need evidence attached.
The only page a citizen can reach without a link. It says what the unit handles, what evidence to collect before reporting, what consent the submission implies, and then hands them straight to the official number.
Submitting a complaint means your information may be stored, processed and shared with authorised agencies. False complaints, fabricated evidence and portal abuse are offences, and all access is logged.
A guided conversation, one question at a time, in বাংলা or English, that ends with a complaint number the citizen can quote later.
The public page states what the unit can help with, what evidence to collect before reporting, and exactly what storing, processing and sharing the submission implies, before the first question is asked.
বাংলা and English are equal throughout: intake, status messages, the officer console and the generated complaint document. Nothing is a translation layer bolted onto an English product.
Chat intake and the web form write to the same complaint record, so a citizen’s status message, the officer’s timeline and the audit log can never disagree with one another.
The secure web link is short-lived and made for a single complaint from the citizen who asked for it. A lost or expired link is simply re-issued on request.
Every card, filter and chart is bound to the same filter state, so a date range or a category narrows the whole page at once, and any number can be clicked to open the cases behind it.
Metric cards, an insight strip and a full set of charts. It answers three questions at a glance: how many complaints are open, where they are stuck, and who is carrying them.
Where cases are actually worked. One wide row holds the complaint, its full status timeline, how long it has been open, who is enquiring, and the actions available right now, with row colour carrying the SLA.
Every row in the workbench is tinted by how long it has been waiting against the unit’s own SLA, so a case drifting towards its deadline looks different from one that has passed it. Nothing quietly ages out of view.
Each complaint arrives with a proposed category and sub-category from the unit’s own taxonomy, plus a severity and a suggested disposal. Every one of them is an officer’s to accept or override.
The assigned officer works the case and uploads a report. A supervisor accepts it or returns it with a reason, and the citizen is told which happened, automatically, in their own language.
Each role sees only the tools it needs, but the restriction lives on the server, not in the interface. Administrative accounts are themselves under role control, so no one can quietly widen their own access.
A complaint system is only as good as its record of what was done. Access and case actions are both logged, and no role can alter those logs from the console.
Citizen Portal is configured to a unit’s own taxonomy, roles, SLA thresholds and retention rules, and runs inside the agency’s infrastructure. We will walk the three surfaces on demonstration data.