A digital city hall kiosk fails when it tries to be a brochure. People at the lobby are not browsing. They are trying to transact: which window, which requirements, how long the wait is, and whether they are in the right place.
Nexus Kiosk is software plus hardware for that moment. Government solutions is the wider civic layer: portals, request tracking, and the workflows behind the counter.
The jobs a kiosk should finish
Orient. Directory of offices, hours, and requirements in the language people actually use, including Filipino when that is how the floor runs.
Route. The citizen should leave with a queue number or appointment tied to the right department, not a screenshot of a PDF.
Reduce the counter load. Forms that can be started at the kiosk should not be restarted at Window 3. Check-in, not data entry theater.
Stay honest about the wait. A display that shows the queue is only useful if the same system is calling the numbers.
What it should not try to be on day one
It does not need to replace the entire LGU stack. Most municipalities already have something for records, payments, or civil registry. The kiosk should complement those systems, scan, look up, print, or hand off, rather than invent a second source of truth.
It also should not require a citizen to “have an account” before they can find the assessor’s office.
Software first, hardware second
The enclosure, screen, and printer matter. The service design matters more. A beautiful cabinet running a PDF is still a brochure. A modest unit connected to queueing and request tracking is a service.
If you are comparing options, kiosk cost in the Philippines covers what actually drives the number. For the industry view, see government.
Start from the service, not the device
Pick one painful lobby flow, business permits, civil registry, or general information, and make that flow finish at the kiosk. Expand once staff trust the queue.