Contents
A mid-sized European government agency that handles permits, local taxes and everyday citizen services rebuilt how it engages with citizens on SAP Customer Experience (CX). It used SAP Service Cloud for cases, SAP Customer Data Cloud for one login and consent, SAP Emarsys for reminders and SAP Commerce Cloud for payments. SAP Business Technology Platform (BTP) connected them to the back office. Processing times fell by nearly 50 percent. The change that mattered most was simpler than any module: citizens and staff saw the same status for the same request.
Citizens had started to expect public services to work with the clarity of online banking. That is what we heard from the people we interviewed. They wanted to log in once, see everything in one place and trust that their request was being handled fairly. The legacy systems could not do that. Departments kept separate records, every counter asked the same questions, and staff re-entered data they had already received somewhere else.
The first thing we learned was simple. You have to listen before you design. Most of our early priorities came from complaints at counters, survey notes and quick conversations, and that was more useful than any planning deck.
We chose parts of the SAP CX portfolio, each with a specific job.
| Module | Problem it solved | What changed |
|---|---|---|
| SAP Service Cloud | Cases scattered across departments, no shared view | One case view for staff, a trackable status for citizens |
| SAP Customer Data Cloud | A separate login per service, consent invisible | One secure login; citizens see and manage their consent |
| SAP Emarsys (now SAP Engagement Cloud) | Citizens chased the agency; the agency never reached out | Reminders for renewals, fees and deadlines |
| SAP Commerce Cloud | Payments in person; reconciliation by hand | Online payment, instant receipts, finance updated directly |
Service Cloud became the workhorse. Whether a request came in online, by phone or at a counter, it followed the same process. A case worker could finally see that the citizen who had just applied for a parking permit had also called last week about a tax question. We set service levels inside the system, which forced accountability. Citizens noticed when timelines were visible and realistic.
We kept chatbots on simple ground. One citizen told us it was a relief to get quick answers about opening hours without waiting on hold, but she also said, "If I have a dispute, I want a person." We agreed.
Customer Data Cloud ended the separate logins for permits, taxes and business licensing. It also made consent visible. During a feedback session, a local business owner said, "At least now I know where my data goes. Before, it felt like I was signing blind." That transparency mattered more than we expected.
Emarsys flipped the model from waiting for calls to sending reminders, deadline notices and updates. It taught us restraint. Too many reminders get ignored. A renewal or tax deadline notice got attention because it felt relevant.
Commerce Cloud moved applications, fees and confirmations into a single online session. Receipts were instant, queues got shorter, and finance staff no longer spent evenings reconciling spreadsheets.
I remember a test run where a citizen's portal showed "in progress" while the staff screen showed "waiting for approval". Same request, two statuses. That mismatch created new calls instead of fewer.
We fixed it by making both sides read exactly the same data from the same Service Cloud record. That fix, more than any feature, is where call volumes started to fall. We learned that citizens value clarity above all else, even more than speed.
At first we underestimated how much manual work sat in the gap between systems. A citizen could apply for a permit online, but staff still had to push the request into the ERP by hand. Payments arrived digitally but were reconciled against finance at the end of the week. Social services ran their own case management with no visibility to anyone else.
BTP became the link. Once Service Cloud was connected to S/4HANA and the older platforms:
- Permit requests started workflows directly in the ERP.
- Payments through Commerce Cloud updated the finance records as they happened.
- Social service case statuses became visible to other departments, within privacy rules.
- Reminder sentEmarsys, now Engagement Cloud, for deadlines
- One loginCustomer Data Cloud, consent visible
- Apply and payCommerce Cloud, instant receipt
- Case openedService Cloud, same process on every channel
- ERP workflow startsThrough SAP BTP, nobody re-keys it
- One statusCitizen and staff read the same record
Citizens stop calling to ask where their request is
Social programmes were the hardest part. Privacy rules set limits, so we exposed case status only at summary level, never the detailed notes. Even that made a difference. Housing authorities could see whether a citizen was already in a support programme, which avoided duplicate support. One case worker told me, "For the first time, I can see the full picture of a citizen's case without digging through four systems."
If integration is where your programme is stuck, my article on SAP Integration Suite delivery delays covers the common causes.
"360 citizen view" sounded like jargon at first. To staff and citizens it meant something simple: stop asking people to tell their story five times. We brought identities, transactions, service requests and communication history into one profile. When someone applied for a housing grant, the case worker could also see an ongoing medical claim and a recent conversation with the tax office. The agency started to act like one organisation.
Cleaning the data was slow and at times boring. But when the errors dropped, trust went up. A 360-degree view built on duplicate records shows everyone the duplicates.
| Area | Before | After |
|---|---|---|
| Processing times | Baseline | Reduced by nearly 50 percent |
| Tracking a request | Phone calls and counter visits | Citizens track applications online |
| Logins | A separate account per department | One secure login with visible consent |
| Staff data entry | Re-keying between systems | One case view; staff handle exceptions |
| Payments | In person, reconciled weekly by hand | Online, with instant receipts |
Permits, taxes and licences finally followed the same steps, and citizens noticed the consistency. Citizens stopped asking "where is my request?" because they could see it themselves.
Citizens value clarity above all else, even more than speed.
- Listen first. Use counter complaints, surveys and satisfaction scores to set the priorities, not a vendor's demo script.
- Show one status. Citizens and staff must see the same record. Nothing reduces calls faster.
- Omnichannel does not mean mobile-only. Everyone said "make it mobile-first", but older residents preferred web or phone. We let citizens start online and switch to a call, with staff picking up at the same point.
- Automate the simple cases first. We started with renewals, where the rules were clear. Staff were nervous about losing control of complex cases, so we went gradually, and that patience built trust.
- Send reminders, not marketing. Keep messages to deadlines and case updates.
- Clean data before integrating. Otherwise the 360-degree view shows every error at once.
The biggest lesson was also the simplest. Respect people's time. When we did that, trust followed. For the regulatory side of public sector SAP work, see my guide to SAP public sector compliance. For a procurement example from the same sector, see my SAP Ariba UAE public sector case study.
What has changed in the SAP portfolio since
One name has changed. In February 2026 SAP renamed SAP Emarsys to SAP Engagement Cloud. SAP Marketing Cloud has reached end of life, so a new programme would use Engagement Cloud for proactive communication. The design lessons above do not depend on product names.
Which SAP CX modules work best for public sector citizen engagement?
In this programme: SAP Service Cloud for case management, SAP Customer Data Cloud for one login and consent, SAP Emarsys (now SAP Engagement Cloud) for reminders, and SAP Commerce Cloud for payments. Start with the case layer, then add identity, then outreach and payments.
What results did SAP CX deliver for the agency?
Processing times fell by nearly 50 percent. Citizens could track applications online instead of calling, one login replaced several, staff stopped re-keying data between systems, and payments moved online with instant receipts.
How is SAP Service Cloud different from a standard CRM for government?
A sales CRM is built around leads and pipelines. Service Cloud is built around cases, service levels and resolution, with one view across web, phone and counter. Connected to SAP BTP and S/4HANA, a citizen request can start a back-office workflow without anyone re-keying it.
How should privacy and consent be handled in a public sector SAP CX rollout?
Give citizens one identity with consent settings they can see and change, which SAP Customer Data Cloud supports. Share sensitive information between departments only at the level needed: in this case, social service cases were visible as a summary status, not detailed notes. Transparent consent also supports GDPR compliance in the EU.
How do you measure success in a citizen engagement programme?
Time to resolution by case type, first-contact resolution, the share of transactions completed online, citizen satisfaction scores, cost to serve and whether status calls actually fall. Portal registrations alone mean little; if people register and still call to check status, the transparency problem is not solved.
What role does SAP BTP play in citizen-facing services?
It connects the citizen-facing front end to the back office. Without it, a digital request still gets re-keyed into finance or case systems. With it, permit requests start ERP workflows, payments update finance records as they happen, and case status flows between departments within privacy rules.
Written by
