The Pattern
The Voice of the Guest industry has a naming problem. What it sells is not the voice of anyone. It is a survey program. A dashboard. A composite score. A prescription engine that generates recommended moves against variables the vendor’s own instruments defined.
The Guest is nowhere in it.
The Guest left a rating. The rating became a number. The number became a bar chart. The bar chart became a trendline. The trendline became a prescription. Somewhere between the rating and the prescription, the actual Guest — the specific person, at the specific table, on the specific shift, in the specific contract state — was thrown away.
What the operator receives is the exhaust. The industry sells it back as the Voice.
The Frame
The industry’s [VoC] class — SMG, Medallia, Qualtrics, Toast Feedback, Yelp for Business, the whole survey-and-review platform stratum — has built a category on a single sleight of hand. They collect Guest input at the moment of the transaction. They strip out the register, the specificity, the relationship history, and the contract state. They output a number the operator can be sold prescriptions against.
Then they call it listening.
It is not listening. It is [Voice Removal] dressed in listening’s clothes. And the operator, running the vendor’s system, believes they are running a [VoC] program because the vendor said so and the dashboard renders a chart. The chart is not the Voice. The chart is what remains after the Voice has been removed.
The Specimen — Pizza Hut And SMG’s Action Xcellence
SMG published a case study on Pizza Hut’s global CX program. The case study frames SMG’s Action Xcellence platform as the infrastructure powering Pizza Hut’s Guest experience improvement. The specimen is public. The specimen is exactly what you would expect.
Pizza Hut collects Guest feedback across surveys, reviews, and case management. SMG’s platform ingests all of it, runs text analytics, produces a composite score, feeds the score into location-level dashboards, and triggers case-management workflows for negative feedback. Locations respond to cases. Regions review scores. Corporate reviews aggregates. Prescriptions cascade downward: retrain the cast, coach the shift managers, run the LTO, address the drive-thru speed, respond to the review within twenty-four hours.
Somewhere in that architecture, an actual Guest sat at an actual Pizza Hut on an actual Tuesday evening, waited too long for their pizza, watched the shift manager screaming at the driver, and drove home wondering why they kept coming back. That Guest left a two-star rating. The rating became a case. The case was closed with a coupon.
The Guest Contract broke that Tuesday. The dashboard did not know. The prescription engine did not know. The composite score moved from 4.1 to 4.0 the next quarter. The vendor billed for the quarter. Pizza Hut renewed the platform.
That is [VoC] as the industry sells it. The specimen is the mechanism.
The Second Specimen — Field Intel
SMG published a second solution brief. It admits, in its own headline, the failure mode of the first product. “CX data shows what’s happening. Field Intel explains why.”
Read that headline again. That is the vendor telling you, out loud, that the product they have sold Pizza Hut for a decade does not answer why. And so they built a second product — Field Intel — to sell them the why.
Field Intel is a private community platform. It captures input from frontline teams. Managers, franchisees, cast members. The vendor asks the community targeted questions about LTOs, promotions, drive-thru throughput, digital order flow, execution consistency. The community responds with photos, videos, in-the-moment feedback. Vendor AI processes the responses and connects field input back to CX and operational decisions.
The vendor calls it “the other witness.”
Read the second product carefully. It is not the Guest’s voice. It is the frontline’s opinion about the operation. Different variable entirely. A cast member’s opinion about why service was slow on Tuesday is not the same signal as the Guest who left because service was slow on Tuesday. The Guest is still absent. The vendor has added a second product that collects a different party’s testimony about the Guest’s absence, and calls the pair “the complete picture.”
The Architecture Of The Arbitrage
Stack the two products together and the mechanism is visible. This is not incompetence. This is a designed multi-product arbitrage.
Product one — Action Xcellence. Sells the dashboard. Produces composite scores. Cannot answer why. Charges by seat, by location, by module.
Product two — Field Intel. Sells the “why” the first product cannot provide. Produces field-community reports. Charges as a second recurring subscription.
Product three — implied. Sells “know what to do next.” Because neither the dashboard nor the field community actually delivers a Design decision — both produce inputs that require operator judgment or vendor consulting to become moves. Consulting engagement, professional services, or the client operators guessing on their own time.
Three products. One Road 2 problem. Each product admits the prior product’s incompleteness. Each product deepens operator dependency on the vendor stack. None of them touch the Guest Contract, the Cast Contract, or the operator’s Perspective at the framework level.
The category has a name in my framework. This is [Edison Trust Arbitrage] at the CX-platform stratum, running the specific mechanism I’ll name here as [Gap-As-Product] — the sales move where a vendor names the gap in their own instrument set and sells a second product to fill it, permanently coupling the operator to two products where one designed Read would suffice.
The Deeper Mechanism — Why Road 1 [VoC] Cannot Ever Answer Why
The industry keeps promising the why. It cannot deliver. Not because vendors are lazy or the technology is immature. Because the instrument set structurally cannot accept the variables that produce why.
One — the instrument records residue, not voice. Surveys ask closed-form questions. “How likely are you to recommend?” produces a zero-to-ten. “How was your visit?” produces a one-to-five. The instrument records the Guest’s emotional residue as a number and discards the Guest’s actual voice. Even open-text fields get processed through sentiment analysis that reduces “the manager didn’t recognize me and I’ve been coming here for four years” to “negative sentiment, staff-related.” The why was in the sentence. The instrument threw it away.
Two — the dashboard aggregates away the individual Guest. Road 1 [VoC] reports averages, medians, distributions, trends. It cannot report “this Guest, on this shift, in this contract state, produced this signal.” By the time the dashboard renders, the individual Guest is gone. The why lives at the individual-Guest level. The dashboard operates at the population level. Different resolution entirely. Individual why cannot be recovered from aggregate what.
Three — the Read is severed from the Design. In a designed listening system, the operator hears the Guest voice at the resolution where a design decision can be made. “Table 12 said the pace felt rushed on Saturday at 7:15” is actionable — you can walk the stage Saturday at 7 next week and see what the pace looks like. “NPS dropped 4 points in Q3” is not actionable at the design level. It is a number that generates vendor-recommended moves. The dashboard has severed Read from Design. The vendor sells you Field Intel as the “why” that reconnects them. Except Field Intel connects frontline gossip about operations to the dashboard, not the actual Guest voice to your Design decisions.
Three architectural reasons. None are fixable by adding more products. All three are load-bearing to the vendor’s business model. If any one of them were closed, the arbitrage would collapse.
Which is why the industry will never close them.
The Diagnostic
Five tests. Run them against any [VoC] platform the industry has sold you. The tests are yes or no. Score honestly.
Test One — the Guest-resolution test. Given the platform’s output, can you name which Guest, on which shift, in which contract state, produced the signal? If no, the platform is not listening to Guests. It is producing statistics about Guest exhaust.
Test Two — the vendor-removal test. If every vendor product were removed tomorrow, could you still run the listening discipline? If no, the operator does not own the listening. The vendor owns it. The operator rents access.
Test Three — the register test. Does the platform preserve the difference between a relational Guest (returning, Road 2) and a transactional customer (transient, Road 1)? If no, the platform is averaging two different populations into one number, which destroys both signals.
Test Four — the Design-authority test. Does the platform feed your Design decisions, or does it feed a vendor’s prescription engine? If prescription, the vendor is running your operating architecture through their business model.
Test Five — the cast-legibility test. Is the platform’s output readable by the cast, the Lead Family, and the operator without vendor training or vendor-owned interpretation? If no, the platform has inserted itself as a required translator between the Guest and the people who serve them.
Score five yeses — you are running a designed listening system, and you don’t need this piece.
Score three or four yeses — you have some listening discipline in place, but a vendor stack has captured pieces of it.
Score two or fewer yeses — you are not running a [VoC] program. You are running a vendor’s subscription against your Guest data. What you thought was listening is [Voice Removal] dressed in listening’s clothes.
What The Industry Cannot Admit
A designed listening system does not need a platform vendor. It needs an operator running the discipline through a trained Lead Family, with the cast as the primary listening surface, aggregated at the Lead layer, Read into the operating architecture, calibrated to the contracts the operation holds with its Guests, its cast, and itself.
That system does not generate recurring platform revenue.
It generates operator sovereignty over Guest intelligence. It generates cast members who are load-bearing at the listening layer, not survey-form completion targets. It generates a Lead Family that owns the Read authority the vendor has been renting the operator for a decade.
The entire industry’s [VoC] class is aligned against this answer. Because the answer is not a product they can sell. It is a discipline the operator runs. And a discipline the operator runs cannot be subscribed to.
Which is why the industry will keep selling you dashboards. And keep admitting the dashboards do not answer why. And keep selling you a second product to explain the first product’s silence. And keep charging you for the coherence claim while the actual Guest — the person at the table, on the shift, in the contract state, telling your cast something in real words — remains as absent from your operation as they were the day you signed the contract.
What You Do Monday Morning
Pull your [VoC] platform’s most recent quarterly report. Pick one shift last week that produced negative sentiment in the report. Walk that shift’s cast — server, kitchen manager, Lead — in person, before the next shift starts. Ask them what they remember about that shift. Which Guests. Which tables. What they heard. What they saw. What they did.
Compare what they tell you to what the platform reported.
If the cast can tell you more, with more resolution, more register, and more contract signal than the platform delivered, you have your answer. The platform is not the Voice. The Voice was on the stage with your cast, and the cast has been holding it while you paid a vendor to tell you it was somewhere else.
Fire the platform. Train the Lead Family. Build the discipline. That is the move.
The Close
The [VoC] industry sells you the silence of your Guests. It captures their input, removes their voice, aggregates their residue, and returns you a dashboard that renders the silence as a chart. The chart trends upward or downward across quarters. The vendor renews the contract. The Guest keeps not coming back.
Somewhere on your stage last Tuesday, an actual Guest told your actual cast something in actual words. The vendor did not capture it. The vendor cannot capture it. The vendor’s business model requires that it cannot capture it.
The listening was on the stage. The listening has always been on the stage. The industry sold you a subscription to look somewhere else.
To understand the ideal state, go to Restaurant Physics.
Digging Deeper
Positions on the record:
The Trade That Made Your Restaurant Look Profitable — https://hacksterism.jeffreysummers.com/the-trade-that-made-your-restaurant-look-profitable
The Five Trades An Operator Runs — https://hacksterism.jeffreysummers.com/the-five-trades-an-operator-runs
The Chipotle Of X Is Framework Arbitrage — https://hacksterism.jeffreysummers.com/the-chipotle-of-x-is-framework-arbitrage
Every Loyalty Program Redesign In QSR Is A Guest Contract Violation — https://hacksterism.jeffreysummers.com/every-loyalty-program-redesign-in-qsr-is-a-guest-contract-violation
The Case Study Is A Hack — https://hacksterism.jeffreysummers.com/the-case-study-is-a-hack
The Automation Industry Just Got Its Edison Trust — https://hacksterism.jeffreysummers.com/the-automation-industry-just-got-its-edison-trust
The Class That Cannot Defend What It Sells — https://hacksterism.jeffreysummers.com/the-class-that-cannot-defend-what-it-sells
What A Designed [VoC] Actually Looks Like — https://physics.jeffreysummers.com/what-a-designed-voc-actually-looks-like
Term definitions from the Knowledge Base:
[VoC] — https://kb.jeffreysummers.com/voc
[Voice Systems] — https://kb.jeffreysummers.com/voice-systems
[Edison Trust Arbitrage] — https://kb.jeffreysummers.com/edison-trust-arbitrage
[Substituted Read] — https://kb.jeffreysummers.com/substituted-read
[Gap-As-Product] — https://kb.jeffreysummers.com/gap-as-product
[Composite Metric Capture] — https://kb.jeffreysummers.com/composite-metric-capture
[Guest Contract] — https://kb.jeffreysummers.com/guest-contract
[Cast Contract] — https://kb.jeffreysummers.com/cast-contract
[Two Roads] — https://kb.jeffreysummers.com/two-roads
[Operating Helix] — https://kb.jeffreysummers.com/operating-helix
[The Lead Family] — https://kb.jeffreysummers.com/lead-family
[The Read] — https://kb.jeffreysummers.com/the-read
The post The [VoC] Industry Sells You The Silence Of Your Guests appeared first on Hacksterism.