How can you effectively measure NPS after a customer interaction?

To effectively measure NPS after a customer interaction, send the survey within 24 hours of the interaction, via the same channel used for the interaction, with no more than two or three questions. The faster and more relevant the survey is to the experience, the higher the response rate and the more reliable the insights you’ll receive. In this article, we answer the most frequently asked questions about measuring NPS after customer contact, from timing and channel to interpretation and follow-up. Would you like to learn more about the technology behind it first? Check out our CX solutions for a complete overview.

At what point after customer contact is the response rate highest?

You’ll achieve the highest response rate by sending the NPS survey within one to two hours after the customer interaction ends. At that point, the experience is still fresh, and the customer feels a direct connection between the survey and the interaction. If you wait longer than 24 hours, the response rate drops significantly, and the responses become less representative of that specific interaction.

Timing isn’t just a matter of speed, but also of context. A customer who has just had a long and frustrating conversation is more likely to respond than someone whose question was resolved in thirty seconds. That difference in motivation leads to skewed data if you don’t take the type of interaction into account. If you send the survey too early—for example, right in the middle of the conversation—it disrupts the interaction itself.

From a practical standpoint, an automatic trigger based on call completion works best. As soon as a ticket is closed, a call ends, or a chat session is terminated, the system automatically sends an invitation. This ensures consistency and prevents surveys from depending on manual actions by employees.

Through which channel do you send an NPS survey after customer contact?

Send the NPS survey through the same channel used for the customer interaction. Did the customer call? Send a text message or a short IVR survey immediately after the call. Did the interaction take place via email or chat? Then follow up through that same channel. Channel matching increases both the response rate and the relevance of the feedback.

The reasoning is simple: the customer is already in the context of that channel, and the barrier to responding is lower when the medium feels familiar. An email survey following a WhatsApp conversation feels like a step backward and requires extra effort on the customer’s part.

Text Messages vs. Email

SMS surveys typically have higher open rates than email, but they are limited in the amount of information you can include. Email offers more room for context and a follow-up question, but requires the customer to actively open their inbox. For phone contact, SMS is the most logical choice; for email contact, a short email survey is the best option.

WhatsApp as a Survey Channel

WhatsApp is gaining ground as a customer service channel and is also well-suited for NPS surveys. The informal tone of the platform is well-suited to short, direct questions. Keep in mind that to send messages outside of an active conversation, you must use approved message templates, which requires some preparation.

What is the difference between transactional and relational NPS?

Transactional NPS measures satisfaction immediately after a specific interaction, such as a phone call or a resolved ticket. Relational NPS measures a customer’s overall loyalty to your organization, regardless of a specific trigger. After customer contact, you almost always use transactional NPS because you want to capture the customer’s perception of that specific experience.

This distinction is important because the two variants provide different insights. Transactional NPS tells you what went wrong or right during a specific touchpoint. Relational NPS gives you a picture of the long-term relationship and the likelihood of a recommendation across the board. Both are valuable, but confusing the two leads to incorrect conclusions.

A customer may give a high transactional NPS after a successfully resolved interaction, but still have a low relational NPS because previous experiences with your organization were disappointing. By measuring and combining both, you can see not only how a single interaction scores, but also whether improvements in customer interactions are actually translating into the overall customer relationship.

How many questions should an NPS survey include after customer contact?

An NPS survey conducted after customer contact should contain no more than two to three questions: the core NPS question itself, one open-ended follow-up question asking for the reason behind the score, and, optionally, one closed-ended question about a specific aspect of the interaction. More questions lower the response rate and increase the likelihood of respondents dropping out halfway through.

The core NPS question is always: “How likely are you to recommend us to a friend or colleague?” on a scale of zero to ten. The open-ended follow-up question, such as “What is the main reason for your score?”, provides the qualitative context you need to understand what lies behind the number.

Resist the temptation to ask more questions. Every extra question lowers your response rate. If you want to measure specific aspects, such as wait time or employee expertise, consider a separate CSAT survey or a periodic, more comprehensive survey, rather than cramming everything into a single NPS form.

How do you interpret NPS scores by contact channel?

Always interpret NPS scores by contact channel in relation to one another and never as absolute values on their own. A score of 40 for phone contact can be excellent if that channel handles complex complaints, while the same score for a simple chat conversation is disappointing. Context determines the meaning of the number.

Consistently segment your NPS data by channel, question type, and time of day. This will help you identify patterns that you might miss when looking at aggregated scores. Phone support consistently scores lower than chat—not because employees perform worse, but because customers pick up the phone for more complex and emotionally charged issues. If you compare your channels without that context, you’ll draw the wrong conclusions about where to invest.

Also look at the breakdown of promoters, passives, and detractors by channel. A high percentage of detractors on a specific channel indicates a structural problem, while a low average score with few detractors suggests passivity rather than dissatisfaction. That nuance will steer your follow-up actions in a completely different direction.

What should you do about low NPS scores from customer interactions?

If NPS scores are low after customer contact, take three immediate actions: contact the individual customer who gave a low score, analyze the open-ended responses for recurring patterns, and provide feedback on the findings to the employees involved or the relevant process. Responding quickly and personally to detractors is the most effective way to prevent churn.

Following up with individual detractors should be a priority. A customer who gives a low score and then receives a personal phone call or message feels that the organization is listening. That opportunity to make amends can actually strengthen the relationship. Automate the notification of low scores so that the appropriate employee or team leader receives an alert immediately.

At the structural level, you use the aggregated data to identify areas for improvement. Do customers consistently complain about long wait times on a specific channel? If so, that’s a capacity or routing issue. Do customers give low scores after being transferred? If so, that indicates a problem with internal call handling. Without that analysis, NPS remains just a number without any action.

How Pegamento Helps Measure NPS After Customer Interactions

Effective NPS measurement starts with a well-designed contact center platform that centralizes data across all channels. We help organizations integrate NPS measurement into their customer contact processes, so you don’t have to report manually but instead automatically gain the right insights.

What we offer in this regard:

  • Automatic NPS triggers after calls, chats, emails, and WhatsApp messages are completed—via the right channel and at the right time
  • A central dashboard displaying NPS scores by channel, employee, time of day, and question type, so you can immediately see where action is needed
  • Connect to your existing systems through smart integrations, without having to choose between your current tools and new capabilities
  • Agentic AI assistants that automatically initiate a follow-up action—such as a callback request or a personalized message—based on low scores, without requiring an employee to manually flag the issue
  • Everything under one roof: from phone and chat to reporting and automation, without complex supplier structures

Would you like to know how your organization can set up an NPS survey in practice and what steps are involved? Contact us, and we’ll explore the options together.

Frequently Asked Questions

What response rate do I need to use NPS data reliably?

A response rate of at least 20–30% is generally considered sufficient for reliable insights, but the higher the better. Below 15%, you run the risk that only the most satisfied or, conversely, the most dissatisfied customers will respond, which skews your data. Improve your response rate by sending the survey shortly after contact, keeping the number of questions limited, and choosing the right channel.

What do you do if a customer contacts you multiple times a month? Do you send an NPS survey every time?

No, it’s highly recommended to set a survey frequency limit, also known as a ‘survey fatigue’ limit. A common approach is to send the same customer an NPS survey no more than once every 30 to 90 days, regardless of the number of contact moments. This prevents customers from becoming annoyed by repeated surveys, which actually has a negative effect on both the response rate and the customer experience.

How do you handle NPS scores from customers who did not initiate contact themselves, such as in outbound campaigns?

With outbound contact, the context is fundamentally different from inbound: the customer did not ask a question themselves and may be less receptive to a direct request. In that case, consider asking the NPS question only if a substantive conversation has taken place, not after a brief or interrupted interaction. Segment these scores separately so you don’t compare them with inbound transactional NPS data, as that will result in a distorted picture.

What common mistakes should I avoid when setting up NPS measurement after customer contact?

The most common mistakes are: sending surveys too late (more than 24 hours after contact), asking too many questions—which causes customers to drop out—failing to segment scores by channel or contact type, and collecting data without a clear follow-up process. Another pitfall is measuring NPS without analyzing the open-ended responses—the score itself tells you little without the qualitative context provided by the follow-up question.

How do you involve employees in NPS results without making it feel like a monitoring tool?

Share NPS results at the team level rather than just at the individual level, and always link scores to concrete improvement actions rather than performance evaluations. Actively involve employees in interpreting open-ended responses so they can recognize patterns on their own and feel a sense of ownership over improvements. A culture in which NPS data is used to learn rather than to evaluate leads to higher engagement and, ultimately, better scores.

Can you also use NPS measurement for internal customer contact processes, such as an IT help desk or HR service desk?

Yes, transactional NPS works just as well for internal services as it does for external customer interactions. The setup is identical: send the survey immediately after a ticket is closed or a conversation ends, via the channel through which the interaction took place, with a maximum of two to three questions. Internal NPS scores provide management with insight into the quality of support processes and help prioritize investments in internal service improvements.

How long does it take for NPS improvements to become visible in the scores?

With targeted improvements in a specific contact process or channel, initial shifts in transactional NPS scores are typically visible within four to eight weeks, provided you collect a sufficient volume of surveys. Structural improvements in the overall customer relationship, as measured by relational NPS, take more time and can only be reliably assessed after three to six months. Establish a regular measurement cycle so you can compare trends over time rather than relying on isolated snapshots.

More blogs

Download the white paper here

Deepen your knowledge with Pegamento’s white papers.

Joost Schaap-Account manager Pegamento

Joost Schaap

Senoir Account Manager

When a customer contacts an organization because they have a complaint, it is crucial that the employee of the organization begin by listening carefully. What does this complaint mean for the customer and also for their own organization? How can this complaint be resolved? After listening carefully the employee needs the right information so that a solution can be offered.

This piece was written by Joost Schaap, working as an Account Manager at Pegamento.

Tim Treurniet-AI developer Pegamento

Tim Treurniet

Designer of Intelligent Systems

Real childhood heroes I never had. But in retrospect, I believe figures like Willie Carrot or Dexter’s lab may have had an influence on me. I get energy from actually making innovative and useful products myself. Nothing like seeing the effect of a project that automates a boring task, or makes a complex process suddenly accessible.

A nice bridge to my photograph is the physical aspect of my work. By working with image recognition, I am often very directly connected to the physical world and my work is more than just programming. For example, our image recognition software ensures safety on bridges, tracks players on a soccer field or uses your own smartphone to accurately measure yourself. This combination between physical and digital provides variety and extra challenge. For me, these are the main reasons for my interest and enthusiasm in what I do!

This piece was written by Tim Treurniet, employed Designer of intelligent systems at Pegamento.

Vera van der Plas-UI-UX designer

Vera van der Plas

UI/UX Designer

As a UX/UI designer, I deal daily with transforming complex data into user-friendly visualizations. All of this topped off with a digital lick of paint which should attract the visitor’s attention to take action.

One of the interesting aspects of this field I find the effects that small tweaks, both textual and visual, can have on conversion. The psychological impact that a simple background color of a CTA button has on our behavior is huge. After all, that color can determine whether or not you are going to buy that product.

What we see and how our brains process and interpret this information fascinates me. The possibilities of subconsciously pointing potential customers in your chosen direction are endless. I hope to apply my expertise more often within our solutions in the future.

This piece was written by Vera van der Plas, working as a UX/UI Designer at Pegamento.

Fouad Rahaoui-Finance Pegamento

Fouad Rahaoui

Financial Controller

A Financial Controller within a company should not only be an expert in Finance. You must also have knowledge of the latest IT developments. Because these are also moving very quickly in the world of Finance.

At Pegamento, I can learn all about the latest IT developments. Like the latest development in the field of Machine learning and deep learning.

Through these application areas, as Financial Controller, I can further automate the financial business processes within Pegamento and implement improvements for the automatic processing of financial data.

This piece was written by Fouad Rahaoui, working as a Financial Controller at Pegamento.

Ernst Vegter-Business consultant Pegamento

Ernst Vegter

Business Consultant

Hospitality is one of my deepest motivations.
Not surprisingly, of course, customer service is a common thread in my career. Aspects of hospitality is being able to connect, to facilitate but mainly to make someone feel genuinely welcome. My intuition is my greatest asset to be able to put myself in the shoes of a guest. A customer is my guest.

Fed by various senses, an image forms around the client. I listen to what is being said, watch facial expressions, taste the underlying tone and get a feel for the challenge to be addressed. An image literally forms on my retina. I have to be able to see it. If I can see it, I can create it.

In this, the trick is to pursue simplicity, give the client a warm feeling that the problem is understood, receive good advice, facilitated and carefully guided to the solution. Trust, connect and unburden.

The feeling when a guest arrives at your hotel after a long tiring journey, can sit in front of the fireplace, be handed a good glass of wine and stare carefree at the fire. My guest knows it will be okay.

This piece was written by Ernst Vegter, working as a Business Consultant at Pegamento.

Gunisch-AI developer Pegamento

Gunish Alag

AI Developer

A picture is worth a thousand words, is an expression most of us have heard. We see a lot of things around us on a daily basis and subconciously have the ability to recognize and understand them. This ability of humans to me seems bizarre.

As a computer vision developer at Pegamento that is what I do, break down complex problems and turn them into solutions using images by meticulously extracting useful data.
With the world moving forward and new technologies emerging, complicated problems which were difficult to solve a decade earlier suddenly seem possible and viable. The future is full of new challenges and I look forward to them.

This story is written by Gunish, working as an AI developer at Pegamento.

Ewold Jansen-Service engineer Pegamento

Ewold Jansen

Service & Support Engineer

Hearing the wishes a customer has or the problems a customer is facing is important in order to then be able to help them properly. In both cases, I help find the right solution.

When the customer comes to us with a desire, they don’t know what all the options are. In this I advise them to make the right choices. When problems arise, listening to them is important. For example, a problem arises from a wrong action. By communicating well in this, many problems can be solved quickly by explaining it well. Through poor communication, a small problem can become very big.

This piece was written by Ewold Jansen, working as a Service & Support Engineer at Pegamento.

Andre Glasbergen-Scrum master Pegamento

Andre Glasbergen

Scrum Master

After completing my studies, I started working as a developer at a young Pegamento with a lot of ambition and enthusiasm. In the first years I learned all about process automation, now better known as RPA. I often had to rack my brains to convert the work instruction into a logical function, with not too many If-statements, so that the robot could perform the work.

I developed further and went to work as a consultant. Listening well to the customer and supporting in the pre-sales phase of projects. Executing projects and listening suited me very well. It was a small, but logical, step to now work as a Scrum Master and Project Manager. I have been supervising projects for a few years now. Such as RPA, Cloud applications and AI, according to the Human lead agile approach, We build this with a large team of specialists.

This piece was written by André Glasbergen, working as a Scrum Master at Pegamento.

Ensar Ari-IT engineer Pegamento

Ensar Ari

IT Engineer

Good communication between customer and organization is very important. As an organization, you naturally want to be easily accessible to your customers. Either via social media channels or via the old familiar telephone. Often organizations do not know exactly how they want their telephone line set up. That is why I like to help them think along and give them ideas. I believe there is a solution to every problem. But sometimes you just need someone who looks at the situation a little differently.

This piece was written by Ensar Ari, working as an IT Engineer at Pegamento.

Nini Heerings-Chief Happiness Officer Pegamento

Nini Heerings

Chief Happiness Officer

“You get to know someone better by playing for an hour than by talking for a year.”

This quote from Plato is totally hitting home for me. That’s why I like to connect people through play. Because while playing, you are totally on, all your senses at work.
In my great role as Chief Happiness Officer, I want to do that by connecting colleagues with each other and with the organization. In a creative and playful way that suits Pegamento.

When I’m not at work, I also enjoy connecting people. I do this by organizing The Playground, where adults play games you used to play in the schoolyard, gymnasium or neighborhood playground. The pure feeling of fun, total relaxation and no thoughts of anything but playing. That feeling is the goal.

This piece was written by Nini, working as Chief Happiness Officer at Pegamento.

Ger Koedam-Communication & Marketing Pegamento

Ger Koedam

Marketing & Communications

How can I help you? That’s pretty much the first question I ask when talking to people who are curious about our services. In such a conversation, the use of senses is very important. Because not everyone is the same. One person thinks in images, while for another words are important or how something feels. For me, sight and hearing are the most beautiful senses, because both eyes and ears absorb information and can convey or process emotions.

Why hearing? Because listening is essential in contact. And it’s the key to unlocking valuable insights.

I developed this skill early on. As a child, I enjoyed radio plays on the radio, bringing the stories to life in my head.

Pim Ritmijer-Software developer Pegamento

Pim Ritmeijer

Software Developer

Programming is more than just “code knocking. For me, listening to what the customer wants and visualizing that is an important part of software development.

Actively listening to a customer to understand the customer’s full story is crucial before building a solution. When you understand a customer’s story, you can think together about a solution that truly helps the customer.

Visualizing solutions is the next step for me. What will be the route we will climb to get to a solution? What challenges are we going to face to get to the top?

Like climbing, good preparation is valuable. Even though you can’t prepare for everything, preparation helps make the application fit the client’s needs as well as possible.

What a beautiful and fascinating profession programming is.

This piece was written by Pim Ritmeijer, working as a Software Developer at Pegamento.

Denise Verhoef-Software developer Pegamento

Denise Verhoef

Software Developer

Hearing is something you do a lot of as a programmer but also thinking, for example, when you are tasked with putting together a customer need. If the customer wants a function for his application, it is important that as a programmer you think carefully about which functions are functional and which functions are not. In this way, you will put together the most functional application possible and the customer will have a good end product. Turning needs into code into functionality is something I find interesting.

I am currently doing an internship at Pegamento and studying Software Developer. I get a lot of information that you have to process and apply. The nice thing about this is that you can learn new things but also that you can experience how it works in real business. I started this training last year and knew nothing about programming beforehand. Now I can find my own way with programming and I enjoy working with it. That you can get from a blank page to a functional application through code is cool!

This piece was written by Denise Verhoef, working as a Software Developer intern at Pegamento.

Remco Pabst-Business consultant Pegamento

Remco Pabst

Computer Vision & AI Lead

Using innovative software technology for people or business to make “things” easier and smarter is really a driving force. That’s why the connection between the senses appeals to me the most. Our brains connect the senses just like a business process connects people, systems (data) and logic. They register and trigger an action, exactly how it should be in an optimal workflow. Very cool what is already possible today when we add a lot of computational power to that as well.

Hearing also means a lot. Not because I like to listen to Jazz, Soul, Deep House or Focus-like music every day AND have to be able to listen well to interpret a wish or pain point, but more because not everyone can have all the senses at their disposal. Think of him or her with a visual impairment. The fact that in close cooperation we were able to apply AI, TTS/STT technology (which is still in development) for this often underserved group of people in today’s digital world and to improve the interaction and experience with it gives me a lot of energy and meaning to what I try to do with technology; create value.

This piece was written by Remco, working as a Business Consultant at Pegamento.

Thomas de Wolf-Vision Engineer Pegamento

Thomas de Wolf

R&D Director

Once when I had to choose which study I was going to do, I had a hard time making that choice. I was interested in engineering, but what I most wanted to do was just work with a team toward a common goal.

To this day, that is still what I love doing most. The technology has become image recognition and the team the computer vision department of Pegamento. So it’s logical that in terms of sense, I end up with “seeing. By using our image recognition solutions to see things in the real world, our entire team solves relevant problems for our customers. And because of the variation in customers, the places where our solutions end up are never the same. For example, one moment I am in the control room of a bridge and the next day I am on a production line for sandwiches or between the fences of a TBS clinic.

This piece was written by Thomas de Wolf, working as a Computer Vision & AI Lead at Pegamento.

Rob Roode-Research Development

Rob Roode

Research & Development

Recognizing and automating patterns. Tasks we are constantly working on when implementing our robots at Pegamento. My 2 Drentsche Patrijshonden are hunting dogs and certainly not robots. The hunting instinct and intuition is basically in their genes. Continuing to offer new forms of training has taught them to recognize and act independently in hunting situations. Even “unsupervised,” even if I’m not around.

But when you try to teach a brain something, it also starts to see things you don’t expect. Dogs pick up on the slightest deviation in your voice or directions. To start recognizing that and correcting it again is perhaps the most complex challenge. But in our work, for the wonderful clients for whom we get to work, it often yields the most beautiful new insights!

This piece was written by Rob, founder of Pegamento and in charge of Marketing and R&D.

Serge Poppes-CEO Pegamento

Serge Poppes

CEO

Feeling. That’s the best thing Pegamento stands for. Feeling for technology in the broadest sense of the word. Not only feeling for the exciting stuff like AI, but also for the basics of communication.

The very best part of my job is selling, listening, translating and thinking about what really matters. We bring the digital transformation with a great team!
The diversity of our team, how sharp we are, but especially the wonderful things we get to make makes me feel extremely good. Hence, I intuitively chose the sense of “feeling.

Feeling gives life and differentiation!