You rated the stay a 6. What would have made it a 10?
Post-Stay Survey
Evaluator agent · 1.9K uses
Strong first-week sales can still be a failure if it cannibalized something better. New menu items are judged on units sold in the first weeks, which rewards novelty and hides cannibalization. This conversation asks the three things that actually predict whether an item earns its place: whether it met expectations, whether they would order it again, and what they would otherwise have ordered.
Start from this conversation and adapt it to your team — change any question, add your own logic, and connect the tools you already use.
The core fields every response captures.
Always ask what they expected before asking what they got
Always ask what they would have ordered if this item had not existed
Follow-ups that change based on what people say.
If it missed expectations, ask whether the menu description or the photo set them wrong
If they would not reorder, ask what they will order instead next time
Different paths for different answers.
Send expectation gaps to the menu and content team
Flag cannibalization of higher-margin items to finance before rollout
Actions that fire the moment a response comes in.
Post item-level test results to #culinary in Slack
Update the item record in HubSpot with reorder intent and cannibalization
Alert finance when a test item displaces a higher-margin dish
The conversation asks the diner what they expected when they ordered the new item, based on the menu description and any photo, then what they actually got. It asks directly whether they would order it again or go back to their usual, and what they would have ordered if the new item had not been there. That last question is what turns a sales number into a real menu decision.
Trigger from a receipt link on checks containing the test item
Run it across enough locations and dayparts that the result is not one kitchen
Capture what the item replaced so cannibalization is visible
Feed the results into the menu decision before the full rollout
Static forms force complex situations into rigid dropdowns. Perspective captures structured data and the reasoning behind it — so your team makes better decisions, faster.
No context. No follow-up. No next step.
"Tell me more about the timeline — when did this start, and is there a deadline your team is working against?"
Extracted & structured automatically
Category
High-priority
Urgency
Deadline: 2 weeks
Sentiment
Frustrated but hopeful
Next step
Route to senior team
Right team. Full context. Instant action.
It is structured feedback on a new or trial menu item from guests who actually ordered it in a live service environment. It differs from taste panels, which evaluate food under controlled conditions without the menu context, and from sales tracking, which measures units without explaining them. The purpose is to decide whether an item deserves a permanent listing.
More hospitality templates for upsell, takeout and restaurant win-back.
You rated the stay a 6. What would have made it a 10?
Evaluator agent · 1.9K uses
Did the way they handled it actually fix how you felt?
Evaluator agent · 2K uses
What did those first ten minutes do to the stay?
Evaluator agent · 1.1K uses
Did you mention it to anyone at the time?
Evaluator agent · 1.3K uses
Did the works actually affect your stay?
Evaluator agent · 2.1K uses
Was the order right when you got home?
Evaluator agent · 2K uses
How restaurant brands judge a new item beyond first-week units.

Eight guest experience platforms compared by what they actually capture.
Read article
Why restaurant feedback collapses into stars, and what a conversation recovers.
Read article
How a hospitality platform uses conversations to understand its operators.
Read articleReplace drop-off, poor qualification, and missing context with AI conversations that capture structured data and real understanding. Set up in minutes.
No credit card required • Cancel anytime