Government e-services desk
Balady, Najiz, Absher, and Qiwa work was a WhatsApp menu. We shipped a bilingual desk that lists each official transaction as a product.
The situation & problem
A Riyadh e-services office executes platform work for individuals and companies. Clients could not see what could be done remotely.
The operational constraints
Dense taxonomy across municipality, real-estate registry, Absher, Qiwa, and insurance — each with its own call / WhatsApp path.
Architectural tradeoffs & what was refused
One paragraph that said “we do government services.” A ticket tool the walk-in desk would not use.
What I built & shipped
Service catalog by platform, working hours, bilingual switch, and direct call / WhatsApp CTAs per service.
Architecture & stack
TypeScript, Next.js, bilingual catalog. Click-to-call and WhatsApp as the handoff, not a fake case-management UI.
Result & measurable impact
A customer can request “renew balady license” instead of “help with papers.”
Next iterations & roadmap
Case intake with platform + transaction type so operations stop re-asking in chat.
System surfaces & interface captures
Hover and click any record to open the full-resolution pixel inspector with zoom lens and 1:1 precision.
Have a similar constraint?
Tell me where your current operational system or product is breaking.