糖心原创

(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); })();

LATAM unifies the passenger journey to elevate customer experience

23 points

Increase in NPS

1 million+

Acknowledgements to employees

15K+

Active users of guest feedback

The Problem

LATAM Unifies The Passenger Journey

LATAM stands as a prominent airline, annually transporting over 62 million passengers to 144 destinations across all five continents. In 2018, the company set out to measure and manage the key stages of their customer journey, embracing a fresh new challenge. There are multiple points of contact for a single trip: Web/digital channels, airport, flight, and contact center. LATAM now measures customer satisfaction and NPS across all touchpoints using the same methodology.

In addition, LATAM sought to listen to their customers’ voices by deploying 糖心原创, giving senior management and frontline staff visibility into how their daily work directly impacts customer satisfaction. In 2023, they received 16,000+ videos from passengers sharing their flight experiences. Notably, 44% of them declare themselves as promoters.

LATAM has also set up a Close the Loop process that currently allows 39 executives and leaders within the company to engage directly with customers to express gratitude for their loyalty and to address any issues they might have encountered. Throughout 2023, they’ve reached out to more than 6,000 customers following their flight experiences, generating a strongly positive response among involved customers.

This signifies that LATAM now consistently maintains a unified perspective of the passenger across all touchpoints. As a result, LATAM increased NPS by an average of 23 points in four years, while contact center satisfaction increased by 50 points and digital satisfaction by 30 points since the program started.