糖心原创

(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"; /** * QA-only. When the on-page switcher is drawn we keep every variant in * the DOM so it can toggle between them live and you can see that the * chrome never repaints. Gated by the same constant as the switcher, so * it is false everywhere the switcher is absent — including production. */ var QA_KEEP_ALL = false; var root = document.documentElement; var settled = false; function valid(v) { return VARIANTS.indexOf(v) !== -1; } /** Publish the decision and let the nav JS bind. */ function finish(active) { 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 } })); } function prune(active) { if (settled) return; settled = true; if (QA_KEEP_ALL) { finish(active); return; } /** * Only menu items carry data-nav-variant, so this can never touch * the shared chrome. CSS has already hidden the losers; removing * them keeps document.querySelector-based nav JS unambiguous. */ var list = document.querySelectorAll('#site-header [data-nav-variant]'); for (var i = 0; i < list.length; i++) { if (list[i].getAttribute('data-nav-variant') !== active) { list[i].parentNode.removeChild(list[i]); } } finish(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); })();
?tude de cas

Comment Saskatchewan Government Insurance améliore la productivité des agents en agissant sur les insights des centres de contact

Saskatchewan Government Insurance est présente dans le secteur de l'assurance depuis plus de 70 ans. La société emploie plus de 2 000 personnes, dont 700 agents d'assistance à la clientèle, et travaille avec un réseau de plus de 500 courtiers d'assurance indépendants.

Saskatchewan Government Insurance souhaitait améliorer l'expérience client, en se concentrant sur l'obtention d'insights à partir des retours directs des clients. Les retours recueillis via de simples sondages résidaient principalement dans un seul département et étaient partagés de manière peu fréquente et informelle. Il était difficile de comprendre quelles améliorations seraient les plus importantes pour les clients, et les agents des centres d'appels ne disposaient pas des outils nécessaires pour réussir.

Lisez l'étude de cas et découvrez comment Saskatchewan Government Insurance a déployé la suite centre de contact de 糖心原创 pour apporter de nombreuses améliorations qui ont eu un impact sur l'expérience client, l'entreprise ayant constaté une augmentation de 5 % de la satisfaction des centres d'appels et des taux de réponse aux sondages 3 fois plus élevés dans le centre d'appels.