Online Request and Complaint Platforms for Citizens

Online request and complaint platforms for citizens

Request and complaint platforms are among the fastest-impact projects in any public body, because they make the citizen’s voice recorded and trackable. Here we explain the parts of a successful platform and how an agency runs it day to day.

Digital government 5 min read

By Nour Aldein Tleti. Updated 7 October 2026.

What makes an online complaints and requests platform effective?

An effective platform receives requests through the citizen’s preferred channel, gives a tracking number immediately, routes the request automatically to the responsible department, and enforces a clear response time. Citizens can see their request’s status, and management gets reports that reveal recurring problems. Without a team that actually handles requests, even the best platform becomes a mailbox nobody reads.

Platform components

Multiple intake channels: A website form, a WhatsApp number, phone calls and a walk-in counter, all feeding one system.
Clear categories: A short list of request and complaint types helps route them quickly to the right team.
Tracking number and status: Citizens get a number on submission and can see whether their request is under review, in progress or closed.
Set response times: Each type has an expected time, and the person responsible is alerted as it nears its end.
Closing with a reply: A request is closed only with a written reply to the citizen explaining what was done or why it was rejected.

Fitting local realities

WhatsApp as a main channel: Many people use WhatsApp more than websites, so reports can be received there and logged in the system automatically or by hand.
Small photos: Compressing photos before upload helps people with weak connections or limited data bundles.
Approximate location: Marking the place on a map or with a simple description is useful for reports about roads, lighting and water.
Protecting complainants: Allow some complaints to be filed confidentially, and protect citizens’ data from unjustified access.

Running the platform after launch

A responsible team: Named staff sort requests daily and follow up with departments that fall behind.
Regular reports: Request numbers by type and area and handling time, to direct resources to the most frequent problems.
Continuous improvement: Reviewing frequent questions and publishing the answers reduces requests in the first place.
Linking reports to planning: When one type of fault keeps recurring in an area, that is a clear case for allocating maintenance or investment there.

Launching the platform step by step

01
List request types
Collect complaints and requests received over a past period and categorise them to see which types are most frequent.
02
Assign responsibilities
Each type gets a responsible department and an agreed response time, documented and approved by management.
03
Set up channels
Start with two or three channels, and connect them all to the same ticketing system.
04
Pilot launch
Run the platform for one report type or one neighbourhood, and address feedback before rolling it out.
05
Measure and announce
After a period of operation, publish handling times and report types, and adjust categories and responsibilities based on what emerged.

Request intake channels

Channel	Advantages	What to watch
Website form	Structured, complete data	Must work well on phones
WhatsApp	Familiar and fast for citizens	Every report must be logged in the system with a number
Phone	Suits older people and urgent cases	Needs a staff member who enters the report directly
Walk-in counter	Serves people who do not use technology	Logged in the same system, not in a notebook
Email	Suits companies and detailed requests	Needs automatic conversion into a ticket

Read also

Digital government

Frequently asked questions

Is a WhatsApp number enough to receive complaints?

No. WhatsApp is a good intake channel, but without a system that logs, routes and tracks each report, messages get lost and management cannot measure anything.

How do we handle malicious or duplicate complaints?

Categorise them, merge duplicates and verify before taking any action, without letting this block genuine complaints.

Should complaints be made public?

You can publish general statistics on report types and handling times without revealing who filed them. This builds trust and shows the platform works.

What is a suitable response time?

It depends on the request type. What matters most is that the time is announced and realistic, and that citizens are told if their request needs longer.

Can the platform be linked to other systems?

Yes, for example to a maintenance or archiving system, so a report becomes a work order without re-entry. ONE DIGITAL works on this kind of automation.