Citizen Request and Case Management Systems for Public Bodies: Customer Service, Power Pages or Custom

What does a public body need from a citizen request system?

More than a ticket queue. A ministry, agency or municipality receives requests, complaints and applications through a portal, email, phone and in person, and each one has a response deadline set by law or by internal rules. Staff need to see the citizen's history, route the request to the right department, and close it with a reasoned answer. Auditors and the public need to be able to trust the record afterwards.

Write these needs down before you compare products, because they decide the answer more than any feature list. The audit trail requirement in particular shapes the data model from the first day; our guide to complaint and case handling that survives a regulated audit covers it in depth.

• Data residency and hosting: where the data may be stored and who may operate the system, as decided by your legal team.
• Armenian language: the citizen portal, staff screens, letters, emails and search, with Russian or English where you need them.
• Deadlines and SLAs: response clocks per request type, pauses while waiting for the citizen, escalations and reporting on breaches.
• Audit trail: who created, viewed, changed, reassigned and closed each request, kept for the retention period your rules set.
• Registry integration: checking a citizen, an address, a property or a company against the registries your body is allowed to query.
• Identity and access: how citizens identify themselves on the portal and how staff roles limit what each person can see.

Where is the data stored on each option, and is there a Microsoft cloud region in Armenia?

Microsoft's list of Azure regions shows no region in Armenia. The regions nearest to it in that list are in Europe and the Middle East, for example Poland Central, Austria East, Italy North, Israel Central, Qatar Central and UAE North. Dynamics 365 and Power Platform environments are created in a region chosen at setup, as described in the Power Platform regions overview, so data in Dynamics 365 Customer Service or in a Power Apps case app is stored outside Armenia.

Whether that is acceptable is a legal question for your body, under Armenian personal data law and your own regulations, and the answer should be settled before any platform is chosen. If citizen data may be stored abroad in a Microsoft region, all four options are open. If it must stay in the country, the choice narrows to a system hosted in a government data centre or with an in-country provider: a custom-built system, or a self-hosted helpdesk for the simplest cases.

How do the four options compare for a public body?

The table compares the options on the criteria that usually decide a public sector choice. No option wins every row, which is why the criteria above should be ranked before the comparison is read.

When is Dynamics 365 Customer Service the right choice?

When citizen data may be stored in a Microsoft cloud region and the request volume or variety is large. Dynamics 365 Customer Service gives case management, queues, routing rules, service level agreements, a knowledge base and channel options as standard, and Dataverse auditing records changes to the tables and columns you choose. A public body gets a mature case model on day one and spends its effort on request types, deadlines and letters rather than on building the basics.

The trade-offs are per-user Microsoft licensing for every member of staff who handles requests, data stored in the chosen Microsoft region, and interface languages limited to the language packs Microsoft ships, so check current Microsoft documentation for Armenian. The content you write, such as request categories, letter templates and knowledge articles, can be in Armenian.

When is a Power Apps case app with a Power Pages portal enough?

When the request types are few and simple, the body already uses Microsoft 365, and Dataverse in a Microsoft region is acceptable. A model-driven Power Apps app on Dataverse holds the requests, Power Automate runs the deadlines and escalations, and a Power Pages portal lets citizens submit a request and follow its status. It is a lighter build than Customer Service and suits a single department or a defined set of applications.

The portal is where projects go wrong: what an anonymous or signed-in citizen can see is controlled by table permissions, and they need careful design and testing. Our comparison of Power Pages and a custom front end for a customer portal explains when the portal should be built separately.

When should a citizen request system be custom-built on government infrastructure?

When data must stay in the country, when registry integration is the heart of the system, or when the body wants to own the code outright. A custom-built system on React, Node.js, PostgreSQL and .NET can run in a government data centre or with an in-country hosting provider, with the Armenian interface, letters and search designed from the first release and the audit trail built into the data model, including who viewed a record if your rules require it.

The body owns the source code, the data and the infrastructure, and there is no per-user licence for staff or citizens. In exchange it takes on what Microsoft would otherwise run: hosting, security patching, backups and a named owner for the system after go-live, either in house or under a support agreement. That cost belongs in the decision from the start.

When is a self-hosted open-source helpdesk enough?

More often than vendors admit. If one internal team handles simple requests that arrive by email or a web form, needs basic deadlines and a shared inbox, and has no registry checks or statutory reporting to run, a self-hosted open-source helpdesk on your own servers can be the right answer. It keeps data in the country, costs no licences, and can be running quickly.

It stops being enough when requests need structured data rather than free text, when several departments share one citizen record, when deadlines differ by request type and pause while waiting for documents, when the audit trail has to satisfy an inspector, or when the system has to check a registry. At that point the choice is between the three options above, and an honest assessment should say so.

Ո՞ր համակարգն է հարմար քաղաքացիների դիմումների համար

Պետական մարմնի դիմումների համակարգը պետք է ապահովի չորս բան՝ տվյալները պահվում են այնտեղ, որտեղ պահանջում են օրենքը և ձեր կանոնները, քաղաքացիներն ու աշխատակիցները կարող են աշխատել հայերենով, յուրաքանչյուր դիմում ունի պատասխանի ժամկետ, և յուրաքանչյուր գործողություն թողնում է աուդիտի հետք։ Microsoft-ի Azure տարածաշրջանների ցանկում Հայաստանում տարածաշրջան չկա, ուստի Dynamics 365 Customer Service-ը և Power Apps-ի ու Power Pages-ի լուծումը տվյալները պահում են Հայաստանից դուրս։ Եթե տվյալները պետք է մնան երկրում, ճիշտ ընտրությունը պետական ենթակառուցվածքի վրա պատվերով մշակված համակարգն է։ Պարզ ներքին դիմումների համար կարող է բավարար լինել նաև բաց կոդով helpdesk համակարգը։ Solzet-ն Երևանից մշակում է առաջին երեք տարբերակները։

Какую систему выбрать для обращений граждан?

Система обращений граждан для государственного органа должна обеспечивать четыре вещи: данные хранятся там, где этого требуют закон и ваши правила, граждане и сотрудники могут работать на армянском языке, у каждого обращения есть срок ответа, и каждое действие оставляет след для аудита. В списке регионов Azure от Microsoft нет региона в Армении, поэтому Dynamics 365 Customer Service и решение на Power Apps и Power Pages хранят данные за пределами Армении. Если данные должны оставаться в стране, правильный выбор - система, разработанная на заказ и размещенная в государственной инфраструктуре. Для простых внутренних обращений может быть достаточно и helpdesk-системы с открытым кодом. Solzet разрабатывает первые три варианта из Еревана.