You rated the stay a 6. What would have made it a 10?
Post-Stay Survey
Evaluator agent · 1.9K uses
A platform rating blends your kitchen with a courier you do not employ. Off-premise orders fail in three different places and the rating blames all of them equally: food that does not travel, an order missing an item, and a courier who took too long. Each has a different owner. This conversation attributes the failure correctly.
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 whether the order was complete and correct
Always compare actual timing against what was promised
Follow-ups that change based on what people say.
If the food arrived cold or damaged, ask about the packaging specifically
If the order was incomplete, ask what was missing and whether anyone resolved it
Different paths for different answers.
Send packaging failures to the operations team with the item named
Route courier problems to the platform relationship owner
Actions that fire the moment a response comes in.
Alert #off-premise in Slack when one location repeats order errors
Create a Zendesk ticket for unresolved incomplete orders
Update the location record in HubSpot with the failure mix
The conversation asks about a recent takeaway or delivery order: how well the food arrived, whether it was hot, intact and packaged properly, whether the order was complete and correct, and how the actual timing compared with the promise. It separates food quality from packaging from courier performance and closes on whether they would order from that restaurant again.
Trigger after the order is marked delivered, on your own channel or via the platform
Decide how results split between your kitchen, your packaging, and the courier
Capture the promised time so timing can be compared honestly
Route each failure type to the team that owns it
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 feedback on an off-premise order covering how the food traveled, whether the order was right and how the timing compared with the promise. It exists because delivery platform ratings blend several independent causes into a single number that the restaurant cannot decompose and is nonetheless judged on.
More hospitality templates for drive-thru, menu testing 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 restaurants separate their own failures from the delivery platform's.

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