Keynote · Zurich

How ewz closes the customer feedback loop between Screver and SAP

Markus Kappen, CX Project Manager at ewz, on how service feedback flows from SAP to Screver and back as callback tickets – around a dozen always-on surveys and more than half of invitations opened. Full keynote and transcript.

Markus Kappen of ewz presenting the ewz customer feedback program at The AI & CX Hype Bubble in Zurich
Markus Kappen of ewz presenting the ewz customer feedback program at The AI & CX Hype Bubble in Zurich

Watch the full video

Enter your work email and the recording opens right here.

Oops! Something went wrong while submitting the form.

ewz, the electricity utility owned by the City of Zurich, invites customers who contact its customer center to rate the service – and sends unhappy customers straight back into SAP as a callback ticket. In his keynote at The AI & CX Hype Bubble in Zurich on 13 June 2025, Markus Kappen, Customer Experience Project Manager at ewz, showed how Screver and SAP work together in this loop, and why the connection is "actually just an email".

ewz's customer feedback program in numbers

  • Since 2017 ewz runs a customer feedback program; on Screver since mid-2024
  • Around a dozen always-on surveys, plus a new ad-hoc survey roughly every two months
  • Around ten regular internal users build and run surveys themselves
  • Dozens of invitations a day after service contacts, with a handful of responses
  • More than half of the invitation emails are opened
  • 3 months without a new invitation after each survey, so customers are not over-surveyed
Markus Kappen of ewz presenting to the audience at The AI & CX Hype Bubble in Zurich
Markus Kappen of ewz presenting the ewz feedback loop at The AI & CX Hype Bubble, Zurich, June 2025.
"The connection from Screver to SAP might look like a big challenge, but it's actually just an email." – Markus Kappen, ewz

Why ewz asks about service – not about electricity

ewz is 100% owned by the City of Zurich and covers the full electricity value chain, from production and grid to trading and sales. Customers rarely think about electricity – they speak up when it fails. The most important contact is the customer center, so ewz focuses its feedback on the service experience. ewz does not ask for NPS: customers cannot change their energy supplier anyway. Instead, ewz measures:

  • Customer satisfaction (CSAT) on a scale from 0 to 10, with a follow-up on what to improve or what customers liked most
  • First contact resolution (FCR) – also a KPI ewz is measured on
  • Customer effort – how difficult it was to complete the process
Slide from ewz: always-on customer surveys and ad-hoc surveys and user testing in Screver
Two kinds of feedback at ewz: always-on customer surveys and ad-hoc surveys or user testing – for sentiment snapshots, recognition, targeted optimizations and KPIs – slide from Markus Kappen's presentation at The AI & CX Hype Bubble, Zurich, June 2025.

How ewz connects Screver with SAP

  1. Service ticket: every customer-center interaction – in person, on the website, by email or by phone – ends in a service ticket in SAP
  2. Invitation: ewz segments the tickets by topic and channel and invites private customers and SMEs by email from SAP Marketing Cloud
  3. Hash: the survey button carries a long hash that links each answer back to the business partner in SAP, without exposing personal data in Screver
  4. Survey: Screver stores the hash, uses targets for each customer service unit and categorizes every comment by topic and sentiment
  5. Callback: if a customer is unhappy or the issue is unresolved, the survey asks "Do you want to be contacted?" – Screver then sends a structured email that SAP turns into a callback ticket automatically
  6. History: each answer is saved as an interaction in the customer's history, so agents see how happy a customer was last time before they pick up the phone
Slide from ewz: the service experience loop from customer interaction via Screver feedback back to SAP callback
The ewz service experience loop: interaction, feedback request, Screver survey, callback ticket in SAP and summaries for internal stakeholders – slide from Markus Kappen's presentation at The AI & CX Hype Bubble, Zurich, June 2025.
Slide from ewz: feedback request email to private and SME customers
The feedback request email: private and SME customers, dozens of automated emails a day, a handful of responses a day, a 3-month block after each invitation and an individual SAP ID per email – slide from Markus Kappen's presentation at The AI & CX Hype Bubble, Zurich, June 2025.
Markus Kappen of ewz on stage in Zurich in front of a slide about thanking customers for their feedback
Markus Kappen on why a good feedback loop starts with asking the right question at The AI & CX Hype Bubble, Zurich, June 2025.

How ewz protects staff and customer data

As a company of the City of Zurich, ewz works under strict data protection rules. It stores only the information it is allowed to keep, uses the roles and permissions add-on in Screver so that not everyone has the same rights, and crosses out names of service staff in comments – customer feedback may not be used to evaluate individual employees.

Slide from ewz: customer service survey in Screver with targets, SAP ID, categorization and content moderation
The customer service survey in Screver: usage targets per organizational unit, the individual SAP ID saved with each answer, categorization and deleting inappropriate content – slide from Markus Kappen's presentation at The AI & CX Hype Bubble, Zurich, June 2025.

How ewz makes customer feedback visible inside the company

  • Screens and small billboards show selected customer comments internally
  • Internal blog posts share feedback and the current customer satisfaction score
  • Topic owners get their own summary – for example, the person responsible for invoices receives all invoice feedback quarterly
  • Self-service: teams across ewz build and publish surveys on their own, for the moving process online, new products or campaigns such as the switch to email bills
Slide from ewz: internal screens and blogs, team KPIs and internal emails sharing customer feedback
Making feedback visible at ewz: internal screens and blogs, team KPIs and quarterly topic summaries by internal email – slide from Markus Kappen's presentation at The AI & CX Hype Bubble, Zurich, June 2025.
"Now the people in customer service know how happy you were last time, and when they answer the phone they can react to that better." – Markus Kappen, ewz
Markus Kappen, Customer Experience Project Manager at ewz, speaking at The AI & CX Hype Bubble in Zurich
Markus Kappen, Customer Experience Project Manager at ewz at The AI & CX Hype Bubble, Zurich, June 2025.

What other utilities can learn from ewz

  • Measure what customers can influence – CSAT, FCR and effort fit a utility better than NPS
  • Close the loop in your core system – a structured email is enough to create a callback ticket in SAP
  • Protect people and data by design – a hash instead of personal data, roles and permissions, no evaluation of individual agents
  • Don't over-survey – a 3-month block after each invitation keeps response quality high
  • Route feedback to owners – categorized summaries reach the people who can act

Transcript: the ewz feedback loop, in Markus Kappen's words

Edited for readability from the keynote recording. Speaker: Markus Kappen, Customer Experience Project Manager, ewz.

ewz and an "unsexy" product

How happy are you today with the electricity in this building? We are responsible for that – not directly, but my colleague and I work for ewz, and we are responsible for the feedback systems. ewz is a company of the city: we are 100% owned by the City of Zurich. What always amazes me is that we are in so many parts of the electricity value chain – from production to the grid to trading and sales. It is a very unsexy product. We have never asked our customers whether they are happy with the electricity – when there is an outage, you will definitely tell us. We ask other questions.

How ewz uses Screver

We have implemented Screver with some individual requirements, especially because we have SAP as our data backbone – and SAP is difficult to connect. Over the last year we managed this well with the Screver team. We use Screver on our website and in our portal, for example for our biggest process, moving: when you move in the city, we need to know the address, who lived there before, what product they had, whether there is a solar panel on the roof. That process online is very important, so we need good feedback on each step. We also use it ad hoc to test a new product, and sometimes even as a replacement for our website – for example in a campaign asking customers to switch to email bills. We have around a dozen surveys running all the time, a new ad-hoc survey every two months or so, and around ten regular users. It is easy to use – you can build your survey and test it right away.

The value of feedback

We started our feedback loop in 2017 with another company. With Screver we can narrow it down to snapshots of how customers feel right now – about campaigns on billboards all over the city, or about things that go wrong with invoices. Customers appreciate that we ask. We try to steer optimization in the company through feedback, and we are measured on customer satisfaction KPIs.

The service experience loop

An interaction in the customer center – in person, a process on the website, email or phone – ends up in a service ticket in SAP. That has been the case forever. What is new is that we segment the topics and the channel and invite customers through an email campaign in SAP Marketing Cloud. The button in the email carries a very long hash, and we can use it to recognize the customer across the whole process. That is the magic behind it. We send this to private customers and small and medium enterprises, and we block them for three months so they don't get emails from us all the time. On average we send dozens of emails a day and get a handful of responses, with an open rate of more than half. As a company of the city we are seen as reliable, so I think we have a better open rate than many others.

Inside Screver: targets, categories and privacy

We built the survey in Screver ourselves. We use the roles and permissions add-on – a requirement from the city, so that not everyone has the same rights. We use targets for our different customer service units, we save the SAP hash with each answer, and we use the categorization, so we know the sentiment and roughly what the feedback is about. We cross out inappropriate content: if someone writes that a named agent was unfriendly, we cross out the name. We are not allowed to evaluate people from customer feedback.

The questions: CSAT, FCR and effort – no NPS

We don't ask whether people would recommend us, because people can't change their energy supplier anyway – we did that in 2017, and it is a weird question for us. We ask for customer satisfaction on a scale to 10 and what we need to improve or what they liked most, first contact resolution, which is also one of our KPIs, and how much effort it took. If the answers show that you are unhappy or your issue is unsolved, we ask whether you want to be contacted, and we save your phone number for exactly that case.

Slide from ewz: survey questions on effort and the option to request a personal callback
Unhappy or unresolved? The survey offers a personal callback and asks for a phone number – slide from Markus Kappen's presentation at The AI & CX Hype Bubble, Zurich, June 2025.

Back into SAP: "actually just an email"

We screen the feedback ourselves and send it to an internal group of people. The callbacks go to SAP. The connection from Screver to SAP might seem like a big challenge, but it's actually just an email. Screver sends emails in exactly the shape we need, the service cloud filters out what it needs and creates a service ticket internally. Every customer who gives feedback has it saved as an interaction in their history, and callbacks are answered right away because they are linked automatically.

Slide from ewz: SAP detects the SAP ID in the Screver email and creates service tickets
Back into SAP: the SAP ID in the Screver email is detected and a service ticket is created automatically – slide from Markus Kappen's presentation at The AI & CX Hype Bubble, Zurich, June 2025.

Making feedback visible

We came up with creative ideas to make customer feedback visible: small billboards, screens with the best feedback, and blog posts with feedback and our customer satisfaction score. People now know a little better what the issues are for our customers. The person responsible for invoices gets a quarterly summary of all the feedback relevant to him. And the people in customer service now know how happy a customer was last time, so when they answer the phone, they can react to that better.

Frequently asked questions

Which metrics does ewz use instead of NPS?

ewz measures customer satisfaction (CSAT) on a 0–10 scale, first contact resolution and customer effort. NPS is not used because customers cannot switch their energy supplier.

How is Screver connected to SAP at ewz?

Invitations go out from SAP Marketing Cloud with a hash that links each answer to the customer. When a customer asks for a callback, Screver sends a structured email that SAP turns into a service ticket automatically.

How does ewz handle data protection?

ewz stores only what it is allowed to keep, uses roles and permissions in Screver and removes names of service staff from comments. See how Screver supports energy and utilities.

Where can I find the other keynotes from the event?

See The AI & CX Hype Bubble – Zurich 2025 for all client keynotes, including MSD, Zillertal, Europa-Park and MS Sports.

Source: keynote recording and slides from Markus Kappen's presentation. Published: 18 November 2026.

More customer stories