Use case 52 · Retail
Hershey guest engagement
Connect guest questions, service knowledge, and frontline action across the experience journey.
Hershey Entertainment & Resorts
Published by Google Cloud
Hershey Entertainment & Resorts: Gifting all guests with a sweet time using Customer Engagement Suite
The published Google Cloud customer story documents Hershey Entertainment & Resorts's use of connected data, AI, and workflow design in this domain.
- The customer story documents a customer-engagement deployment designed to support guest experiences.
- The example is treated as evidence of a design pattern, not a promise that every deployment will reproduce the same result.
Workflow at a glance
See the orchestration path before exploring the operating detail.
This domain view shows where AI accelerates the work and where accountable human judgment remains in command.
The business problem
Orchestration redesigns the whole operating loop.
Guest-facing teams need fast, consistent answers while demand moves across channels, venues, and operating teams.
Hershey Entertainment & Resorts is a public proof point for the pattern. The transferable lesson is the operating design: a service orchestration layer can assemble context and guide the frontline without replacing hospitality judgment.
Orchestration corridor
How the work moves from signal to accountable outcome.
Every step has a defined input, intelligence task, action, and handoff. This is what separates an operating system from an isolated prompt.
-
01
Frame the demand
Define the business signal, Guest questions, reservations, feedback, and service requests, and the outcome that matters.
-
02
Assemble context
Connect approved records, knowledge, and guest profiles, venue information, schedules, and approved policies before the model acts.
-
03
Coordinate the work
Use AI to retrieve answers, summarize requests, and route the right service action, then route uncertainty to the accountable owner.
-
04
Execute with limits
Move the permitted task through existing systems while preserving guest privacy and frontline escalation.
-
05
Measure the result
Track time to guest-ready answer, quality, exceptions, and the effect on the wider ecosystem.
Ecosystem command map
The capability lives between systems, not inside one model.
The four quadrants show the assets that must be coordinated. Select any quadrant to emphasize its role in the operating system.
Signals
What enters the system
- Guest questions, reservations, feedback, and service requests
- guest profiles, venue information, schedules, and approved policies
- Outcome, urgency, and exception signals
Intelligence
What AI organizes
- retrieve answers, summarize requests, and route the right service action
- Evidence retrieval and prioritization
- Pattern, risk, and confidence analysis
Actions
What the workflow moves
- Prepare the next best action
- Route, draft, or update the authorized system
- Escalate the consequential exception
Human command
Where authority remains
- Business owner sets the objective
- Subject-matter expert validates the decision
- Risk and data owners monitor the boundary
Value and control instrument panel
Measure the business result and the integrity of the route.
The bars are not performance claims. They show the measurement sequence: establish the current baseline, agree a pilot threshold, and verify the observed result.
time to guest-ready answer
Baseline the current time to guest-ready answer and compare the assisted path with the existing process.
Establish baseline → set pilot threshold → verify outcomeQuality at handoff
Measure whether the human owner receives complete, relevant, and traceable context.
Establish baseline → set pilot threshold → verify outcomeException rate
Track uncertainty, rework, escalation, and failure by workflow segment.
Establish baseline → set pilot threshold → verify outcomeBusiness outcome
Connect the workflow change to more consistent guest service across high-volume moments, not just model activity.
Establish baseline → set pilot threshold → verify outcome90-day implementation route
Move from reconnaissance to controlled scale.
Select a phase to inspect its executive decision gate.
Phase 1
Recon
Map the current hershey guest engagement workflow, owners, evidence, systems, and failure modes.
- Executive owner
- Chief Digital Officer
- Decision gate
- Problem and baseline confirmed
Phase 2
Pilot
Run one bounded workflow with the current process as a comparison and make time to guest-ready answer visible.
- Executive owner
- Chief Digital Officer
- Decision gate
- Value and control thresholds met
Phase 3
Scale
Expand only after quality, control, adoption, and ecosystem effects are accepted by the operating owner.
- Executive owner
- Chief Digital Officer
- Decision gate
- Operating owner accepts scale
Source and governance discipline
Evidence first. Claims qualified. Accountability designed in.
This operating play is an independent synthesis by Dr. Alejandro Canonero, DBA. It translates a documented implementation into a vendor-neutral business design and applies the War of the Ecosystems perspective. It does not imply endorsement by the source organization.
Executive working session
Apply this pattern to your retail workflow.
A focused diagnosis will map the current work, quantify the opportunity, define human command, and shape the first controlled pilot.