Warning: Constant WP_CACHE_KEY_SALT already defined in /home/staging_interaction/www/wp-config.php on line 64

Deprecated: WP_Rocket_Mobile_Detect::__construct(): Implicitly marking parameter $headers as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/classes/dependencies/mobiledetect/mobiledetectlib/Mobile_Detect.php on line 888

Deprecated: MwpWorkerResponder::callback(): Implicitly marking parameter $response as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/worker/init.php on line 165

Deprecated: MWP_WordPress_Context::__construct(): Implicitly marking parameter $globals as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/worker/src/MWP/WordPress/Context.php on line 28

Deprecated: MWP_WordPress_Context::__construct(): Implicitly marking parameter $constants as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/worker/src/MWP/WordPress/Context.php on line 28

Deprecated: Symfony_EventDispatcher_EventDispatcher::dispatch(): Implicitly marking parameter $event as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/worker/src/Symfony/EventDispatcher/EventDispatcher.php on line 40

Deprecated: Symfony_EventDispatcher_EventDispatcherInterface::dispatch(): Implicitly marking parameter $event as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/worker/src/Symfony/EventDispatcher/EventDispatcherInterface.php on line 36

Deprecated: MWP_Extension_HitCounter::increment(): Implicitly marking parameter $dateTime as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/worker/src/MWP/Extension/HitCounter.php on line 37

Deprecated: Jaybizzle\CrawlerDetect\CrawlerDetect::__construct(): Implicitly marking parameter $headers as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/pixelyoursite/vendor/jaybizzle/crawler-detect/src/CrawlerDetect.php on line 79

Deprecated: YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container::__construct(): Implicitly marking parameter $parameterBag as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60

Deprecated: WP_Rocket\Dependencies\League\Container\Container::__construct(): Implicitly marking parameter $definitions as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Container.php on line 42

Deprecated: WP_Rocket\Dependencies\League\Container\Container::__construct(): Implicitly marking parameter $providers as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Container.php on line 42

Deprecated: WP_Rocket\Dependencies\League\Container\Container::__construct(): Implicitly marking parameter $inflectors as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Container.php on line 42

Deprecated: WP_Rocket\Dependencies\League\Container\Container::inflector(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Container.php on line 156

Deprecated: WP_Rocket\Dependencies\League\Container\DefinitionContainerInterface::inflector(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/DefinitionContainerInterface.php on line 19

Deprecated: WP_Rocket\Dependencies\League\Container\Inflector\InflectorAggregate::add(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Inflector/InflectorAggregate.php on line 19

Deprecated: WP_Rocket\Dependencies\League\Container\Inflector\InflectorAggregateInterface::add(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Inflector/InflectorAggregateInterface.php on line 12

Deprecated: WP_Rocket\Dependencies\League\Container\Argument\LiteralArgument::__construct(): Implicitly marking parameter $type as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Argument/LiteralArgument.php on line 27

Deprecated: WP_Rocket\Dependencies\League\Container\Inflector\Inflector::__construct(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Inflector/Inflector.php on line 36

Deprecated: array_first(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/helpers.php on line 112

Deprecated: array_last(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/helpers.php on line 184

Deprecated: optional(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/helpers.php on line 722

Deprecated: with(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/helpers.php on line 1175

Deprecated: App\sage(): Implicitly marking parameter $container as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/app/helpers.php on line 15

Deprecated: Illuminate\Support\Collection::times(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 117

Deprecated: Illuminate\Support\Collection::filter(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 468

Deprecated: Illuminate\Support\Collection::when(): Implicitly marking parameter $default as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 485

Deprecated: Illuminate\Support\Collection::unless(): Implicitly marking parameter $default as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 504

Deprecated: Illuminate\Support\Collection::first(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 655

Deprecated: Illuminate\Support\Collection::last(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 905

Deprecated: Illuminate\Support\Collection::sort(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1444

Deprecated: Return type of Illuminate\Support\Collection::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1789

Deprecated: Return type of Illuminate\Support\Collection::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1800

Deprecated: Return type of Illuminate\Support\Collection::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1812

Deprecated: Return type of Illuminate\Support\Collection::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1827

Deprecated: Return type of Illuminate\Support\Collection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1768

Deprecated: Return type of Illuminate\Support\Collection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1747

Deprecated: Return type of Illuminate\Support\Collection::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1716

Deprecated: Illuminate\Container\Container::resolving(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 958

Deprecated: Illuminate\Container\Container::afterResolving(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 978

Deprecated: Illuminate\Container\Container::setInstance(): Implicitly marking parameter $container as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 1186

Deprecated: Illuminate\Contracts\Container\Container::resolving(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/contracts/Container/Container.php on line 143

Deprecated: Illuminate\Contracts\Container\Container::afterResolving(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/contracts/Container/Container.php on line 152

Deprecated: Return type of Illuminate\Container\Container::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 1197

Deprecated: Return type of Illuminate\Container\Container::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 1208

Deprecated: Return type of Illuminate\Container\Container::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 1220

Deprecated: Return type of Illuminate\Container\Container::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 1233

Deprecated: Return type of Illuminate\Config\Repository::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/config/Repository.php on line 141

Deprecated: Return type of Illuminate\Config\Repository::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/config/Repository.php on line 152

Deprecated: Return type of Illuminate\Config\Repository::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/config/Repository.php on line 164

Deprecated: Return type of Illuminate\Config\Repository::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/config/Repository.php on line 175

Deprecated: Illuminate\Support\Arr::first(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Arr.php on line 162

Deprecated: Illuminate\Support\Arr::last(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Arr.php on line 191

Deprecated: Roots\Sage\Template\BladeProvider::__construct(): Implicitly marking parameter $container as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/roots/sage-lib/Template/BladeProvider.php on line 21

Deprecated: Illuminate\View\FileViewFinder::__construct(): Implicitly marking parameter $extensions as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/view/FileViewFinder.php on line 53

Deprecated: Illuminate\Events\Dispatcher::__construct(): Implicitly marking parameter $container as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/events/Dispatcher.php on line 59

Deprecated: Method ReflectionParameter::getClass() is deprecated since 8.0, use ReflectionParameter::getType() instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 826

Deprecated: Method ReflectionParameter::getClass() is deprecated since 8.0, use ReflectionParameter::getType() instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 900

Deprecated: Brain\Hierarchy\Hierarchy::getHierarchy(): Implicitly marking parameter $query as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/brain/hierarchy/src/Hierarchy.php on line 66

Deprecated: Brain\Hierarchy\Hierarchy::getTemplates(): Implicitly marking parameter $query as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/brain/hierarchy/src/Hierarchy.php on line 78

Deprecated: Brain\Hierarchy\Hierarchy::parse(): Implicitly marking parameter $query as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/brain/hierarchy/src/Hierarchy.php on line 90

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 111

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 135

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 167

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 180

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 220

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 260

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 281

Deprecated: Brain\Hierarchy\Branch\BranchSingle::__construct(): Implicitly marking parameter $postTemplates as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/brain/hierarchy/src/Branch/BranchSingle.php on line 29

Deprecated: Brain\Hierarchy\Branch\BranchPage::__construct(): Implicitly marking parameter $postTemplates as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/brain/hierarchy/src/Branch/BranchPage.php on line 30

Deprecated: Illuminate\View\View::render(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/view/View.php on line 87

Deprecated: Return type of Illuminate\View\View::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/view/View.php on line 308

Deprecated: Return type of Illuminate\View\View::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/view/View.php on line 319

Deprecated: Return type of Illuminate\View\View::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/view/View.php on line 331

Deprecated: Return type of Illuminate\View\View::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/view/View.php on line 342

Notice: file_get_contents(): Read of 12288 bytes failed with errno=21 Is a directory in /home/staging_interaction/www/wp-includes/functions.php on line 4666

Notice: wp_json_file_decode(): Error when decoding a JSON file at path /home/staging_interaction/www/wp-content/themes/interaction-metrics/resources: Syntax error in /home/staging_interaction/www/wp-includes/functions.php on line 6114

Notice: file_get_contents(): Read of 12288 bytes failed with errno=21 Is a directory in /home/staging_interaction/www/wp-includes/functions.php on line 4666

Notice: wp_json_file_decode(): Error when decoding a JSON file at path /home/staging_interaction/www/wp-content/themes/interaction-metrics/resources: Syntax error in /home/staging_interaction/www/wp-includes/functions.php on line 6114
Net Promoter Score (NPS): Pros & Cons - Interaction Metrics

The Net Promoter Score (NPS) is the most well-known customer satisfaction metric used by two-thirds of the Fortune 1000 companies. But it’s also easy to misunderstand and misuse.

Created in 2003 by Fred Reichheld of Bain & Company, the Net Promoter Score (NPS) asks: “How likely are you to recommend us to a friend or colleague?�? Customers answer on a 0-10 scale. Then, the Net Promoter Score (NPS) is the percent of promoters (9-10) minus the percent of detractors (0-6). That means if everyone rated you a 9 or a 10, your NPS Score would be 100! However, the average NPS Score is a far cry from 100; in fact, according to Survey Monkey, it’s 32 and varies widely by industry.

 

net promoter score (nps) calculation

Net Promoter Score (NPS) has the advantage of being straightforward to calculate and comprehend. Also, it’s potentially relevant for some companies because the question emphasizes the customer’s social orientation by framing their likelihood to recommend in the context of their friends.

But the Net Promotor Score (NPS) has its drawbacks too. Here are a few:

  1. Given the popularity of the Net Promoter Score (NPS), companies can appear insincere when they ask the NPS question. Customers are so used to answering the NPS question that they may assume a company is not genuinely interested in what they have to say.
  2. The NPS categorizes all scores between a 0 and a 6 into a single category of detractors, but that’s a wide range in customer sentiment that’s worth breaking down.
  3. The Net Promoter question may not be a great fit for every company or every situation. For example, specialty manufacturers can provide an excellent customer experience, and yet it’s unlikely customers would recommend these kinds of companies to their friends or even necessarily their colleagues.
  4. The Net Promoter question does not work for all customer experience touchpoints, like website navigation or product packaging. Nevertheless, these touchpoints are critical to the customer’s experience.
  5. Finally, the Net Promoter Score (NPS) does not include a weighting factor to reflect the relative importance of various aspects of the customer experience.

With these considerations in mind, it’s critical to ask whether the NPS question is the right fit for your company. Does the metric match your company’s objectives?

In certain industries, customers aren’t likely to recommend companies to their peers at all, no matter what their satisfaction level might be. That’s why we generally recommend the Net Promoter Score (NPS) is best for companies in industries where customers are likely to recommend them, such as luxury hotels or spendy restaurants.

More broadly, it’s never enough to simply send an NPS survey. Instead, you need to optimize the Net Promoter question with a follow-up strategy to ensure customers feel heard and you have the insights you need to move your company forward.

Deploying Net Promoter Score (NPS)

Whether you conduct NPS Surveys monthly, quarterly, or annually, aim to gauge customer sentiment toward your company as a whole. Periodic assessments will help you monitor your customer health and establish a benchmark for your company’s success.

While some companies use NPS after transactions like product delivery or customer service interactions, the question isn’t suited to that. After all, customers don’t recommend you based on one event. Instead, your customers will recommend you (or not) because of their overall experience from start to finish and over time.

Segmenting NPS is Critical

Segmenting your NPS scores by demographics, customer categories, or product groupings is necessary to glean actionable customer insights. Without these segmentations, you will probably be at a loss for what actions to prioritize and which next steps to take. So, while you might report one aggregate score, practically speaking, you will work with several NPS scores.

Are you considering using Net Promoter Score (NPS)? If so, get in touch.

Categories: Customer Satisfaction Surveys