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
Customer Experience: Optimize or Improve?

Lately, at Interaction Metrics, we’ve been discussing the difference between striving to optimize and striving to improve. Specifically, should you optimize your customer experience or improve it? I’ve come down on the side of customer experience optimization because improvement is just too vague.

For instance, many of us equate service and manufacturing quality with the Japanese Kaizen principle ‘strive for never-ending improvement’. Never-ending doesn’t feel like the best use of time.

Optimization, on the other hand, is concrete and has a precise target. You know you’re optimized when you’ve reached the point of diminishing returns.

Tech Support & Customer Interfacing Teams

For tech support, customer service, and other customer interfacing teams, customer experience optimization takes what you have in place and extracts its maximum value. But with improving, it’s hard to say where exactly you’re going or when you will arrive.

Investing in optimization makes sense. For example, if you’re already spending on costly staff along with software like CRM, knowledge management, and text analytics you want to know that you’re using those resources wisely.

As a rule of thumb, to ensure that the resources you have in place are being used for your company’s and customers’ greatest gain, invest 1 to 3 pennies on the dollar. For instance, if your tech support budget is $4,000,000 per year, add $40K to $120k per year to optimize.

Want to present the case for customer experience optimization? Learn about Interaction Metrics’ free mini-evaluations.

Customer Experience Optimization Advantages

Once optimized you’ll be able to prove you are:

  • Best in class
  • Serving your customers in ways that align with your unique brand
  • Committed to informing and connecting with customers in measurable ways

Sometimes I get asked, “Will optimized interactions become long and bog us down?” Absolutely not.

In fact, if you are truly optimized, sometimes interactions become shorter. That’s because while customers want a good answer, they also want you to value their time. Your customers don’t want answers laden with gratuitous questions and commentary. Modern people get things done!

However, if your interactions are already concise, optimization is about ensuring that each moment of your interactions serves a purpose. That purpose could be to:

  • Provide explanations that help beyond a single question
  • Create happy customers measured by satisfaction scores
  • Boost sales measured by repurchase rates

Optimization Requires Multiple Perspectives

The best optimization strategies employ multiple perspectives.

For instance, to optimize customer support efficiently, you need to know how you’re performing relative to your own standards for brand congruence, sales, and product information.

You also need to know how you measure against your customers’ perceptions and expectations (external evaluations). And you need to know how you stack up against competitors and comparable companies.

If you don’t have multiple perspectives, it’s easy to get a false read on how you’re actually performing. I’ve seen companies rest on the laurels of a good Net Promoter Score, but when upper management listened in on calls, they were appalled at how often those interactions failed to provide real value.

Setting Expectations for Customer Experience Optimization

At Interaction Metrics, we consider a company’s customer experience optimized when their interactions score at least 91 and customers rate their experience at 85 or above. Sometimes (albeit rarely) we find that a company is fully optimized out of the gate. Or, it just takes a few tweaks and they are optimized!

More often, however, customers rate companies as good but not great. And companies have staff who only sort of answer questions, don’t support the brand, and fail to connect with customers. In these cases, the best approach is measurement, followed by workshops, followed by measurement again—in rapid cadence. But once a company is optimized, interaction measurement only needs to happen often enough to ensure interactions stay optimized in the face of staff turnover, new products, and fresh marketing campaigns.

Surveys are Communication Tools

But even when customer surveys show you are scoring in that 85+ zone, you still want to get daily feedback. That’s because surveys conducted properly gather information about which customers need callbacks, who needs an apology, what needs to be escalated, or who needs more information.

In other words, surveys serve their greatest utility when they are used as communication tools.  Keeping an open channel with customers is central to what it means to be optimized.

Milestones and Measurement

Just because you have CRM does not mean your associates are using customer information effectively. And just because you have staff in chairs taking calls does not mean they are clearly and proactively connecting with customers. Customer experience optimization gives you a clear path forward with milestones and metrics. So, lose the word improve and instead find out how optimized you really are!

Toward wisely used budgets and customer experience optimization!

Categories: Customer Experience Strategy