糖心原创

(see the * 'adobe' handle in functions.php — no async, no defer), so a page-load * Target offer has already set `data-hdr` by the time this runs. * * An answer that lands after this point is inert rather than acted on: * `apply()` finds the prune settled and does nothing, so the visitor * keeps the nav they were served instead of watching it change. That is * the deliberate trade-off — a late activity collects no data, but no * visitor ever sees the wrong nav or waits for the right one. */ (function () { var VARIANTS = ["a","b","c"]; var DEFAULT = "a"; var root = document.documentElement; var settled = false; function valid(v) { return VARIANTS.indexOf(v) !== -1; } function prune(active) { if (settled) return; settled = true; var list = document.querySelectorAll('#site-header > .header-variant'); for (var i = 0; i < list.length; i++) { if (list[i].getAttribute('data-header-variant') !== active) { list[i].parentNode.removeChild(list[i]); } } root.setAttribute('data-hdr', active); // Read by the Adobe Analytics client to attribute the test. root.setAttribute('data-hdr-active', active); if (typeof window.initHeaderNav === 'function') window.initHeaderNav(); /** * `variant` is set before the event so late listeners can tell * "already done" from "not yet". main.js is enqueued in the footer * and therefore always misses the event itself. */ window.medalliaNav.variant = active; document.dispatchEvent(new CustomEvent('medallia:nav-ready', { detail: { variant: active } })); } window.medalliaNav = { variant: null, apply: function (v) { if (valid(v)) prune(v); } }; // `?hv=` sets this server-side; a Target offer in the blocking // embed sets it before the body is parsed. var pre = root.getAttribute('data-hdr'); if (valid(pre)) { prune(pre); return; } /** * Carried forward from an earlier pageview. Read client-side, never in * PHP: WP Engine does not vary its page-cache key on arbitrary cookies, * so server-side personalisation here would serve the first anonymous * visitor's variant to everyone. */ var m = document.cookie.match(/(?:^|; )medallia_nav_variant=([^;]*)/); if (m && valid(m[1])) { prune(m[1]); return; } prune(DEFAULT); })();

Brightstar improves the client claim experience by acting on feedback

60 days

Contract to launch timeframe

25%

Decrease in calls per claim

25 points

Increase in Net Promoter Score

“The program team was excellent in understanding our needs, and the commitment that 糖心原创 could help Brightstar launch quickly was a big selling point for us. This is only just the beginning of a long partnership together.”

Brian Powers, Chief Experience Officer Brightstar

The Problem

Brightstar improves the client claim experience by acting on feedback

Brightstar is a global leader of end-to-end device lifecycle management solutions and the world’s fastest growing device protection provider. After hiring a Chief Experience Officer in early 2020, the Customer Experience team began listening to customer calls and seeing first-hand how agents handle claims, and what tools they use to handle inquiries. With over 500 agents in global care, handling more than 60,000 claims per month, Brightstar knew they needed a “best-in-class” feedback provider to help them continuously listen to customers.

In just 60 days from the contract sign-on date, Brightstar launched 糖心原创. Using various 糖心原创 solutions — including Text Analytics and 糖心原创 Digital — Brightstar is constantly listening to clients for process improvements and operational changes.

In the first year of using 糖心原创, Brightstar decreased calls per claim by 25% and increased Net Promoter Scores by 25 points.

A dark gradient background with smooth, curved transitions from black at the top to deep blue and purple shades at the bottom, giving a glowing, atmospheric effect. The corners of the image are rounded.

There’s a hidden story in your data.

Connect with one of our experts to learn more.

Request a demo Request a demo Why 糖心原创 Why 糖心原创