I Watched a Spacecraft Round the Moon in Real Time and it Changed How I Think About Contact Centers.

I sat on my couch at two in the morning, laptop balanced on one knee, coffee going cold, watching four astronauts loop around the Moon.

Artemis II was the first crewed mission beyond low Earth orbit in over fifty years. Four people strapped into NASA’s Orion capsule, flung out to lunar distance, and brought home again. The mission itself was extraordinary. What made it unforgettable for me, though, was the telemetry.

The Data Was the Experience

From about sixty seconds after liftoff, NASA’s Artemis Real-time Orbit Website (AROW) started streaming continuous sensor data from the spacecraft. Distance from Earth. Distance from the Moon. Velocity. Hull temperature in sunlight and shadow. Cabin temperature. G-forces on the crew. Signal delay caused by the speed of light. All of it, live, for ten days straight.

Independent trackers like artemislivetracker.com went further still, rendering live 3D trajectory maps alongside system status for life support, propulsion, communications, navigation, power, and thermal control. You could watch the heatshield temperature climb as Orion punched back through the atmosphere at thousands of degrees. From your living room.

That last bit is what got me. I wasn’t watching a replay. I wasn’t reading a summary the next morning. I was understanding the mission as it happened. Every data point told a story. Every anomaly was visible. Every milestone landed in context. Real-time telemetry turned me from a passive spectator into an informed participant.

It felt like being in Mission Control, without the headset.

The Black Box Problem

Here’s where my brain went, because apparently I can’t watch anything cool without relating it back to CX.

Most contact centers today operate the way space agencies did before real-time telemetry. You know the mission launched. You know if it crashed. The in-between? Black box.

An agent picks up a call. The customer sounds frustrated. Was there a network glitch that caused a dropout? Is the headset cutting out? Is the CRM lagging? Did the Voice AI misroute them? Nobody knows until someone files a ticket, an engineer starts digging through logs from three different platforms, and by then the customer has already churned.

This is a problem that CX Observability solves. The same principle that made Artemis II so captivating to watch, applied to every customer interaction running through your contact center.

Same Principle, Different Orbit

AROW pulled data from Orion’s onboard sensors across propulsion, life support, thermal systems, and navigation. CX Observability does something remarkably similar across the contact center technology stack: agent desktops, browsers, headsets, networks, VPNs, CCaaS platforms, Voice AI, CRM, telephony, WebRTC. Fifty-plus technologies generating signals, all the time.

Those independent Artemis trackers threaded raw telemetry into something meaningful: a 3D trajectory, a system health dashboard, a story you could follow. In the CX world, that’s what a Customer Journey Trace does. It correlates signals from across the stack into a unified, real-time view of each interaction. Not after the fact. Not in a weekly report. While the conversation is still happening.

When NASA’s Mission Control saw a temperature reading spike, they didn’t wait for the post-flight debrief. They acted because they had the data in the moment.

This is where CX Observability, feels more like Mission Control, it surfaces issues as they happen, so teams can prevent poor experiences rather than apologize for them afterwards.

The Feeling You Can’t Get From a Dashboard

What struck me most about following Artemis II wasn’t any single data point. It was the feeling of situational awareness. I could see the whole picture. I understood why things were happening, not only that they were happening. It’s the difference between checking a scoreboard and actually watching the game.

Contact center leaders have CSAT scores and handle times, sure. Those are lagging indicators, though. The equivalent of knowing the spacecraft landed safely without understanding the voyage.

Artemis II’s telemetry enabled composable actions: course corrections, system adjustments, crew advisories. Real-time CX data does the same. Issues get detected, correlated, and resolved before they cascade into the kind of experience that loses customers.

Better yet, imagine if anyone watching Artemis II could have typed “What was the cabin temperature at lunar closest approach?” and have an instant, sourced answer returned to me. That’s where CX Copilot sits. Contact center leaders querying their environment in plain language, surfacing KPIs, root causes, and performance trends in seconds rather than waiting days for a BI team to pull a report.

Every Interaction Deserves Its Own Mission Control

Artemis II reminded the world what becomes possible when you instrument a complex system and watch it in real time. NASA didn’t send astronauts to the Moon and then wait for them to come back to find out what happened. They gave every one of us a seat in Mission Control.

Contact centers are complex systems too. Millions of interactions, countless variables, fifty-plus technologies all touching a single conversation. The organizations that will lead in customer experience are the ones that stop flying blind and start instrumenting their CX stack the way NASA instruments a spacecraft.

Real-time telemetry changed how we experience space exploration. CX Observability is doing the same for how we deliver customer service.

I reckon every interaction deserves its own Mission Control. If NASA can give that level of visibility to a spacecraft 250,000 miles away, we can give it to the ops manager responsible for the conversations their agents handle each day here on Earth.

Until next time and as always, Hooroo


If your contact center needs a little less "Houston, we have a problem" then tap your combadge and get in touch

‍