Digital citizen service: identity, documents, case

A citizen receives a decision letter whose amount does not match her application. She calls, is asked for a supporting document, sends it by post, waits for an answer and finally has to sign a declaration. Five steps, three media, several weeks.

This guide shows how the same request can be resolved in one continuous case: contact, identity, signature, document check and reply, with no printing and no detour through the letterbox. It names the legal bases with sources and the questions to settle before you start.

The guide focuses on Germany, where the relevant law is federal and state law.

#Where broken hand-offs arise

A broken hand-off happens whenever information has to change format for a case to move on: from a phone call into a note, from paper into a scan, from a scan into a case management system. Every change costs time and invites errors.

The three most expensive breaks almost always sit in the same places: identity, signature and supporting documents. Close those three digitally and most of the way is done.

#The target state: one request, one case

In the target state, every request starts as a contact and immediately becomes a case. Everything that follows is attached to that case: conversation history, proof of identity, submitted documents, check findings, signature and reply.

1. Contact: the request arrives by phone, chat, email or messaging and is routed.
2. Case: the case officer sees history and context on one desktop.
3. Identity: where needed, the citizen identifies with the online ID, without an appointment on site.
4. Documents: supporting documents are uploaded and checked against rules; deviations appear as findings.
5. Decision: the case officer decides and records it; if needed, the citizen signs during the conversation.
6. Reply: outcome and note go back into the case and to the citizen.

Service EN· active

Queues

Voice3 waiting

Chat5 waiting

Email2 waiting

Messaging1 waiting

Conversation

AI agent, disclosedHandover from AI agent · context complete

I received the decision letter, but the amount does not match my application.

I have the case in front of me. One moment, I am checking the calculation.

Sentiment: calmVoice

Context

Case

2026-0412

History

3 · 14 d

Univerx Assist

Suggested reply

The letter deviates from the application. I will propose a correction and send you the confirmation by message.

InsertAccept

Summary

Request: deviation in the letter. Documents on file. Next step: correction, confirmation by message.

#Contact: every channel in one queue

Citizens choose the channel that suits their situation. What matters to the administration is that every channel flows into one queue and every employee sees the same history. The Univerx Contact Center is built for exactly that.

Many requests recur: opening hours, case status, required documents. AI agents can answer such questions, disclosed as AI, and hand over to people with full context as soon as a decision is involved.

Correct answers rest on a well-kept knowledge base. Univerx Knowledge serves employees, AI agents and self-service from the same source, with grounded answers. That way the chat says the same thing as the phone line.

Administrations know their predictable peaks: after a batch of decision letters, before a deadline, when benefit rules change. A callback instead of a queue, and proactive notices about appointments, deadlines and case status, take the edge off such peaks. The article Informing proactively shows how.

For work that needs processing in the background, there is task routing: requests for documents, checks and callbacks are routed like contacts, with deadlines and workbins.

#Identity: online ID and eIDAS

Many requests may only be processed once it is clear who is asking. Until now that has often meant an appointment on site or a copy of an ID card. Both are cumbersome, and a copy is weak evidence.

The electronic identity function of the German ID card lets holders aged 16 and over prove their identity electronically to public and private bodies (Section 18 PAuswG). Across Europe, the eIDAS Regulation governs electronic identification and trust services.

The amendment by Regulation (EU) 2024/1183 adds European digital identity wallets. For administrations, this means the number of ways to identify digitally is growing.

The Univerx Channel brings identification into the conversation. A link from chat, email or text opens a guided dialogue with no download. The Channel is designed for identification with the German online ID and eIDAS identities, and the result goes back into the case.

Sign4 / 5

Online ID card✓ Identity confirmed

Shared view

SignatureSigned

#Trust: how citizens recognise a genuine link

A link by text or email is convenient. It is also the tool fraudsters use. Anyone inviting citizens into a digital dialogue therefore has to make genuine invitations easy to tell apart from fake ones.

A few rules have proven themselves:

• Announced: the link arrives during or right after a conversation in which the employee mentions it.
• Recognisable: sender and target address clearly belong to the authority and are listed on its website.
• Restrained: the invitation never asks for passwords, PINs or bank details. Identification uses the online ID, not typed-in secrets.
• Time-limited: a link is valid for one case only and for a short time.
• Verifiable: citizens can always call back on the known number and ask.

Publish these rules as well, for example on your service page. People who know what a genuine invitation looks like spot a fake one faster.

#Written form: what can be replaced electronically

Where a legal provision requires written form, the answer used to be paper and a signature. The German Administrative Procedure Act explicitly allows electronic routes. Under Section 3a VwVfG, written form can be replaced, among other things, by:

• an electronic document bearing a qualified electronic signature,
• a declaration made directly in the authority's electronic form, combined with electronic proof of identity when submitted over public networks.

For social law, Section 36a SGB I contains a corresponding rule. Which form suffices for a particular declaration depends on the specific law; both provisions apply "unless otherwise provided by law".

#Documents: checking without handing over the decision

Many requests come with paperwork: decision letters, invoices, contracts, evidence. Checking them takes time, especially when amounts, periods and rates have to be compared with rules and booked payments.

Semantic² reads such documents, structured or scanned, checks them against readable rules, the contract and the booking, and reports deviations as findings in euros. Every finding names the amount, the rule, the location in the document and the related booking.

Invoice

Item 4 · deviating rate€184.50

FindingSample

€184.50

Rule

Rate × hours

Source

Invoice, line 4

Booking

Voucher 2026-0412

AcceptReject

The decision stays with the case officer, who accepts or rejects each finding, and every such action is logged.

This matters especially in the public sector, because AI systems that help decide access to public services and benefits may be classed as high-risk under the EU AI Act.

The guide Using document intelligence in cases explains how to plan a Semantic² deployment.

#Social data protection: separate rules for sensitive cases

Anyone handling social benefits is bound not only by the GDPR but also by social secrecy.

Under Section 35 SGB I, everyone is entitled to have their social data protected from unauthorised processing, including within the benefits agency itself. Further definitions and rules are in Sections 67 et seq. SGB X.

For platforms, Section 80 SGB X is particularly relevant. Anyone having social data processed on their behalf must notify the competent supervisory authority in good time beforehand. Processing is permitted in Germany, in the EU, in equivalent states, or where an adequacy decision exists.

This translates into concrete operational requirements:

• Role-based access: only those working on the case see the social data; team leads see metrics, not content.
• Recording: only with consent, and with retention periods that match the purpose.
• Analytics: agree conversation analytics and performance metrics with the staff council.
• Data location: Univerx stores data and media in EU regions; hosting in Germany is planned. The page Data residency & hosting in Germany gives the current status.

The article Social data protection in the contact centre covers the practice in more depth.

#One request, worked through

Back to the decision letter from the start. The citizen calls because the amount does not match her application. The employee sees the case with application and letter on her desktop and notices that a supporting document is missing.

Instead of asking for a letter, she announces a link and sends it by text. The citizen opens it without a download, identifies with the online ID and uploads the document. Both see the same view while the employee explains what is needed.

Semantic² checks the document against the rules of the benefit and the booked amount. It finds a deviation and shows it as a finding with amount, rule and source.

The case officer reviews the finding, accepts it and initiates the correction in the case management system.

If the correction requires a declaration from the citizen, she signs in the same dialogue. Outcome, signature and note go into the case. The citizen receives a message with the result. At best, several weeks and three media become one conversation and one case.

Not every request can be handled this way. Some declarations require a specific form, some documents need checking in the original. The flow is a target state to test for each service, not a promise for all of them.

#Accessibility from the start

Public bodies are obliged to make their websites and applications accessible; for federal authorities this is set out in BITV 2.0, and the federal states have their own rules. That includes chat, forms and the guided dialogue in the Channel.

So plan accessibility as a requirement at the start, not as a test at the end: keyboard operation, screen readers, plain language, no time limits without an extension.

For customer-facing interfaces, Univerx aims for WCAG 2.1 AA and EN 301 549. The guide Accessibility in customer service goes into detail.

#The framework: the Online Access Act

Germany's Online Access Act (OZG) requires federal and state governments to offer administrative services electronically via administrative portals. Portals thus handle the application route. Questions, document requests and signatures during an ongoing procedure need a contact route as well.

This is where portal and citizen service complement each other. The portal takes the application, the contact centre resolves what is still open. What matters is that both look at the same case and no parallel file emerges.

#Getting started: one service, one channel

The safest route starts with a public service that is in high demand and where identity, signature or supporting documents cause broken hand-offs today. One channel is enough at first, for example phone with a link into the Channel.

1. Workshop: choose the service, map today's flow with every broken hand-off, settle legal bases and form requirements.
2. Preparation: define roles and rights, notify under Section 80 SGB X where social data is involved, involve the staff council.
3. Pilot: one team, one channel, one service; a weekly review of lead time, follow-up questions and feedback.
4. Rollout: more channels, then more services; document checks wherever evidence is regularly checked against rules.

Measure what citizens and employees feel: time to resolution, number of follow-up questions, share of cases without postal mail. There are no figures in advance; they come from your pilot.

#Frequently asked questions from administrations

#Do citizens need an app?

Not for the Univerx Channel: the link opens in the browser.

For the online ID, as with any use of the eID function, the device needs an eID application and the ID card needs its online function activated. Say so in the invitation so nobody is caught off guard.

#What about people without a smartphone or online ID?

The digital route is an offer, not an obligation. In-person visits, phone and post remain open. Done well, the digital route relieves the counters enough to leave more time for people who need personal support.

#Where is the data stored?

Univerx stores data and media in EU regions; hosting in Germany is planned. A data processing agreement and documents for the data protection impact assessment are available on request. Where social data is involved, the notification under Section 80 SGB X applies as well.

#Does document checking replace the case officer?

No. Semantic² reads and checks; the case officer decides. The benefit is that deviations become visible earlier and with evidence, not that decisions are made without people.

#Checklist before the pilot

#Next steps

Citizen service without broken hand-offs is not a mega-project but a series of small, proven steps. The Public sector page shows what this can look like in your administration; the use case Identification & online closing describes the flow.

The glossary explains terms such as online ID, eIDAS and co-browsing. If you would like to choose a service for the pilot together, book a demo.