Guest Experience Survey Template (Free) + KPI and Action Guide
Launch a guest experience survey you can run every week without overthinking the setup. Start with a stable core (overall CSAT + NPS + one driver open-text question), then add touchpoint modules only where you need detail. Use the action guide below to set timing, avoid biased samples, and follow up fast on low scores.
Trusted by 5000+ Brands
Choose your KPI setup: CSAT vs NPS vs CES (and the default combo)
| Goal: pick the KPI bundle that fits your property and touchpoints. Default: Overall CSAT (satisfaction) + NPS (recommend) + one driver open-text question; add CES (effort) for check-in and issue resolution. Do this now: choose your default bundle, then lock the exact question wording and scales before you add any optional modules. | |||
|---|---|---|---|
| KPI | Standard question + scale | Best for in hospitality | Tradeoffs + operator notes |
| CSAT (satisfaction) | "Overall, how satisfied were you with your stay/visit?" 5-point: Very dissatisfied (1) -- Very satisfied (5) | Touchpoint performance and frontline coaching. Use for: room/cleanliness, staff helpfulness, F&B, amenities. | Easy to act on, but you need consistent timing and a stable core to trend. Add one driver question so you know what to fix, not just that a score moved. |
| NPS (recommend) | "How likely are you to recommend [Property] to a friend or colleague?" 0 (Not at all likely) -- 10 (Extremely likely) | Loyalty/advocacy tracking across properties and seasons. Good for: brand-level reporting, owner updates, competitive benchmarks. | Not diagnostic by itself (two hotels can share an NPS for different reasons). Pair with CSAT and a driver question. Evidence on NPS and growth is mixed; treat it as a trend KPI, not a single-number truth (see Keiningham et al. on Net Promoter and revenue growth). |
| CES (effort) | "How easy was it to [check in / change a reservation / get your issue resolved]?" 5-point: Very difficult (1) -- Very easy (5) | Process friction. Best for: booking flow, mobile key, check-in queues, billing/checkout, service recovery. | Narrow by design (that is the point). You must tie it to one process per question. Use it where you can realistically change the process in your normal improvement cycle. |
| Default bundle (recommended) | 1) Overall CSAT 2) NPS 3) Open-text driver: "What is the main reason for your score?" | End-to-end guest experience tracking with a simple action loop. | Keeps the survey short while still telling you what to fix. If you only do one thing today, lock these 3 questions and keep them stable over time. |
| Add CES (effort) when... | Add 1 CES question in the relevant module. | You see repeat complaints about queues, confusion, handoffs, or "I had to ask twice." | Do this now: add CES to check-in and to issue-resolution follow-ups so you can measure friction after you change the workflow. |
| 2-minute decision guide | If you need touchpoint fixes -- use CSAT. If you need an exec-friendly loyalty trend -- add NPS. If you need to remove friction in a process -- add CES. | Keep one overall KPI set across all properties so you can compare like-for-like. | Default setup: Overall CSAT (5-point) + NPS (0-10) + one driver open-text question; add CES for check-in and resolved-issue follow-ups. |
Customize the template for your property and guest journey (without breaking trends)
- Lock your core first: Keep 3 items stable across every run (Overall CSAT + NPS + "What is the main reason for your score?") so you can trend month to month.
- Swap in your language: Replace "stay" with "visit," "dining," "treatment," or "event". Use one term consistently (guest/visitor/diner) and include your property or venue name in the NPS question.
- Choose touchpoint modules you can act on: Add only the sections you will review weekly (room + cleanliness; staff; F&B; spa; events). Do this now: remove any module you cannot assign an owner to.
- Route guests who report an issue: Add a yes/no: "Did anything go wrong that we should address?" If yes, show: "Which area?" (checkboxes) and "May we contact you to follow up?" (Yes/No).
- Keep scales consistent: Pick one satisfaction scale and keep the labels unchanged. Use the same direction (low-to-high) everywhere, and reference Likert scale options (and when to use 5-point vs 7-point) when you are standardizing across properties.
- Use fewer points on touchpoints: For most hospitality touchpoints, 5-point ratings are a good default and often easier for guests than long numeric scales (see evidence comparing 5-point vs 10-point item scales).
- Write one idea per question: Avoid double-barreled items like "The room was clean and quiet." Split into two questions so you know what to fix.
- Stay neutral and skimmable: Use simple wording and avoid leading phrases like "How amazing was..." If you need a refresher on question wording and burden control, use AAPOR's best practices for survey research as your checklist.
- Use a copy-ready privacy blurb: Add one sentence in the invite like "We use your feedback to improve service and may follow up if you request it." Keep personal data to the minimum you need; privacy and data handling basics has copy you can paste.
- Make open-text optional: Keep "main reason" open-text strongly encouraged but not required, especially on mobile. Starter rule (adjust after baseline): keep open-text required questions to 1 max, placed right after the overall score.
Who should take this survey (and how to keep your sample unbiased)
Goal: get feedback from the right guests (not just the happiest and angriest) so your scores reflect operations.
Default: invite recent guests after a completed stay/visit; add a separate follow-up for guests who had a service recovery case.
Do this now: define your invite rules in one sentence (who, when, and how often) before you send the first wave.
Who to invite
- Primary: guests who completed a stay/visit (post-checkout or post-visit).
- Secondary: guests who contacted guest services/support and had an issue resolved (send a short recovery follow-up).
- Exclude: no-shows/canceled bookings (unless you are specifically measuring booking or cancellation friction with CES (effort)).
How to sample without skewing results
- Low volume: run a census (invite everyone) and use a contact-frequency cap (starter cap, adjust after baseline: no more than 1 invite per guest every 30 days).
- Higher volume: sample by day and shift (weekday/weekend; AM/PM), and keep a steady mix by channel (direct vs OTA) so your trend line does not swing just because your guest mix changed.
- Frequent guests: avoid repeatedly surveying the same loyalty members; rotate invites so you do not turn your survey into a "regulars only" view.
If only extreme experiences reply, your average will bounce around. Fix it by sampling across days/shifts and capping invites for frequent guests. If your channel mix shifts (more OTA one month), report results by channel and use how response bias can skew guest feedback to spot patterns before you treat a score change as a true operations change.
Default setup: invite all completed stays if volume is low; otherwise sample evenly by day/shift/channel and use a starter invite cap (adjust after baseline) of 1 invite per guest per 30 days.
Timing, channels, and sample size plan (for usable response rates)
Quick setup
Goal: set timing, channel, and a response target you can hit consistently. Starter setup (adjust after baseline): post-stay invite 24-72 hours after checkout via email; add SMS for a short mobile-first version. Do this now: choose your send window and keep it stable for a starter field-test period (adjust after baseline), such as 8-12 weeks.
Send timing by touchpoint
Post-stay: starter window (adjust after baseline): send 24-72 hours after checkout (fresh memory, less on-property noise). Restaurant/spa/venue: starter window (adjust after baseline): send the same day, ideally within 2-6 hours. Service recovery: send after the issue is resolved so CES (effort) reflects the full fix.
Match the channel to the moment
Email: best when you want detail (modules + open text) and can personalize by stay dates. SMS: best for a short core (starter length, adjust after baseline: 3-8 questions) and fast turnaround. QR: best on-site for single touchpoints (breakfast, shuttle, spa checkout) when you can keep it short (starter target, adjust after baseline: 60-90 seconds).
Set a simple response target (and keep quotas stable)
Pick a weekly or monthly target per property and key segment (direct vs OTA, room type, purpose of trip). Use sample size guidance for surveys to set starting targets, then keep the same targets each month so trends stay comparable. Low response rates do not automatically make results unusable; consistency and bias control matter (see Pew's overview of what low response rates mean for surveys).
Cap contact frequency for repeat guests
Do this now: add a starter cap (adjust after baseline) like "no more than 1 invite per guest every 30 days" (or 60 days for loyalty members). Keep the cap the same across channels so you do not over-survey guests who book direct and also get SMS offers.
Default setup
Starter setup (adjust after baseline): post-stay email 24-72 hours after checkout + optional SMS core; on-site QR only for single touchpoints; monthly targets by property and channel; invite cap per guest.
How to analyze guest feedback and turn it into action (closed-loop workflow)
- Step 1: Lock your weekly scorecardGoal: see trend changes early without drowning in comments. Default: track Overall CSAT (satisfaction), NPS (recommend), and any CES (effort) you added for check-in or issue resolution. Do this now: build a one-page view that shows this week vs a starter rolling baseline (adjust after baseline), such as the prior 4 weeks, for each property.
- Step 2: Segment results the same way every timeStart with cuts you can act on: property/location, room type, direct vs OTA, purpose of trip (business/leisure), length of stay, and shift or day of week. Do this now: choose a small, stable set of cuts (starter set, adjust after baseline: 3) you will report every week so you do not chase random movement.
- Step 3: Prioritize drivers using a simple hotspot rulePair low scores with high mention frequency by touchpoint, then confirm in verbatims. Micro-example (illustrative, not a benchmark): if cleanliness CSAT is down and "bathroom" shows up frequently in comments, make that the first fix. This aligns with standard customer satisfaction monitoring guidance like ISO 10004 guidelines for monitoring and measuring customer satisfaction.
- Step 4: Turn low scores into a closed-loop taskSet one alert rule and one owner rule. Example starter thresholds (adjust after baseline): if Overall CSAT is 1-2 (on a 5-point scale) or NPS is 0-6, trigger an alert to the property lead; if the guest selected "staff" or "billing," route to the department owner. Do this now: write your response SLA (starter SLA, adjust after baseline: first response within 24-48 hours) and log outcomes (resolved, refunded/comped, coaching, process change needed).
- Step 5: Run three cadences so fixes actually happenWeekly ops huddle: top hotspots (starter focus, adjust after baseline: top 3) and the one fix you will complete by next week. Monthly management review: trend lines by segment, plus whether last month's fixes moved CSAT/CES. Quarterly: bigger changes (staffing model, vendor change, training, capital items). Default setup: weekly hotspot list + low-score follow-up alerts, with monthly trend review by property and channel.
Frequently Asked Questions
Which metric should I use for guest experience: CSAT, NPS, or CES?
Use CSAT (satisfaction) to manage touchpoints like room, cleanliness, staff, and F&B. Use NPS (recommend) when you need a loyalty/advocacy trend across properties. Add CES (effort) when you are fixing friction in processes like booking, check-in, or issue resolution; default bundle: Overall CSAT + NPS + one driver open-text question, with CES added to check-in and service recovery.
How long should a post-stay guest experience survey be?
Keep the core short so it is easy to finish on mobile (starter length, adjust after baseline: about 8-12 questions). Use 1-2 optional open-text prompts (do not make them required) and only add modules (F&B, spa, events) when you will review and act on them weekly.
When should I send the survey after checkout or after an on-site visit?
Send post-stay surveys using a consistent starter window (adjust after baseline), such as 24-72 hours after checkout, so results stay comparable. For restaurant, spa, and venue experiences, send the same day (starter window, adjust after baseline: within 2-6 hours). For service recovery, send after the issue is resolved so guests can rate the full outcome.
Should the guest experience survey be anonymous?
Use anonymous feedback when you want maximum candor and you are focused on trends, not individual follow-up. If you need service recovery, do not make it fully anonymous; use a hybrid by asking "May we contact you to follow up?" and only collecting contact details when guests say yes.
How many responses do I need for each property or segment?
Set a practical monthly target per property and key segment (like direct vs OTA) and keep that target steady so you can trend changes. Use the built-in sample size guidance for surveys to pick starting targets; consistency and bias control usually matter more than chasing a perfect number.
How do I follow up on low scores without annoying guests?
Follow up only when a guest gives a low score (starter thresholds, adjust after baseline: CSAT 1-2 or NPS 0-6) or reports a specific issue, and respond within a clear SLA (starter SLA, adjust after baseline: 24-48 hours). Set a contact-frequency cap (starter cap, adjust after baseline: 30 days) and say in the invite that you may follow up if they request it, then log outcomes so you can prove what changed next month.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED