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
Are You Begging for a Thank You with Your Email Surveys?

Every day, everywhere, companies send email surveys, smiley face surveys, or call to request our customer feedback. It’s overwhelming. However, as we enter the holiday season, let’s acknowledge that when an associate is incredibly helpful, it’s nice to be able to say “thanks!”

Consider when an associate goes the extra mile: it feels good to reciprocate with a “sure, I’d recommend” or a 5-star rating that the associate’s boss might see.

What I’m talking about here is a social contract.

Social Contracts are Mostly Good!

A social contract is an implicit agreement among the members of a society to cooperate in exchange for benefits. It’s basic reciprocity.

In this case, if the associate does what the customer wants in terms of providing a good answer or helping with a refund, many customers, including me, will say thank you by giving a top rating on the email survey.

And there’s nothing wrong with fulfilling social contracts. Our society is built on them and they generally make our lives easier and better.

Giving is Good

In the case of email surveys and other feedback prompts, this kind of reciprocity gives the associate what they need to bolster their case for a raise or a promotion, and I get to feel like I helped.

Adam Grant, renowned psychologist and author of Give and Take goes further and says that being asked to help is really an opportunity to help ourselves and advance our own careers. So, give and then give more!

However…

While it feels good to reciprocate, let’s be clear: a Thank You Survey isn’t capturing objective facts about the customer experience. Read on to find out what all Thank You Surveys have in common.

1) The Associate Decides Who Gets the Survey

If your associates email the survey or, at the end of a call, take customers to a screen to provide feedback, you’re doing a Thank You Survey. Or, perhaps there’s a survey link in the associate’s signature. But the point is, associates at least appear to elect who takes the survey. And this appearance alone is enough to influence the resulting data.

Microsoft provides an egregious example of the associate playing a heavy hand. At the end of each tech support call, the associate stays on the phone while they take me to my portal where I’m asked to rate the support I received. I imagine that if that tech support call went poorly, they may not take me to this screen.

And certainly, if the support went poorly, I am apt to put my foot down and just bail out of the call and not give the associate what they want. Giving associates control over which customers take the survey is a sure-fire way to get skewed data.

2) It’s Phrased as a Favor!

If your associate’s feedback questions are built directly into the exchange, they are simply asking for a favor. In the picture below cropped from the end of a customer support incident, it’s clear my response will go directly back to the associate. This transactional exchange makes it extremely unlikely that if I answer it would be with anything other than “Great!”

Email-Survey-Ex-Interaction-Metrics

If I didn’t have a good experience, the most socially comfortable thing to do is just avoid taking the survey altogether. Often it may feel like a small gripe isn’t worth the damage it might have on an associate’s performance review.

But if the associate was especially kind or generous, I’m inclined to say “great” to return the favor. Skewed, transactional exchanges don’t give companies any real sense of how their associates are doing.

3) The Questions are Leading

In the picture below, there is nothing objective about the associate’s request. “Let me know if I was helpful” is simply a request for good feedback. It limits customer feedback to the topic of helpfulness and assumes that the associate was, indeed, helpful.

Email-Survey-Pic-Interaction-Metrics

Thank You Surveys can be Awkward 

Sometimes Thank You Surveys are just plain awkward. For example, recently I had a recall on my car and while my car was in the shop, the dealership gave me a loaner from Enterprise. Upon returning the car, with tablet in hand the associate asked, “how would you rate our customer service?” Put on the spot, I said “everything was perfect!”.

However, the day before, the associate said they’d pick me up in 10 minutes. Instead, I waited more than an hour for them to show up. I was mad. But there’s no way I would discuss that with an employee who was about to shuttle me back to the dealership.

There’s a lot of social pressure that comes from an associate asking you to rate them. I discuss this in “Answering NPR: Why 5 Star Rating Systems Don’t Work”, but, bottom line, just like the Microsoft example, my “everything was perfect” summation fails to help Enterprise collect facts about its customer service.

Fact Surveys Uphold the Pillars of Objectivity  

Unlike Thank You Surveys, Fact Surveys uphold the pillars of objectivity by: offering the option of anonymity, removing subjectivity, and ensuring even response representation.

For example, when we’re running Customer Surveys and using gifts to boost completion rates, we allow customers to remain anonymous while still getting their gift!

Fact Surveys also work hard to remove leading statements, skewed scales, double-barreled questions, and other subjective constructs.

For example, instead of asking me “how satisfied were you with tech support” (a question that suggests I was at least somewhat satisfied) a Fact Survey asks me to “rate the engineer’s expertise”. The latter question is specific and asked in a neutral way.

With Thank You Surveys, respondent populations tend to be highly skewed by who the associate chooses to ask for feedback and/or more enthusiastic customers who are simply more likely to respond.

In contrast, Fact Surveys strive for statistical validity and aim to collect data that are representative of the actual customer base.

Know the Difference 

There is value to Thank You Surveys. It feels good to thank an associate for their effort and help them do well in their job. But let’s not mistake this with scientific metrics and objective customer experience fact-finding.

By understanding the difference between the two, you can decide which to use and when. While there will always be a place for a well-served thank you, if you want to make real improvement, using Thank You Email Surveys should not be your sole outlet for feedback.

Toward using the right surveys at the right time for the best information!

Categories: Customer Satisfaction Surveys