100 Best Claude Online Review Response Prompts for Airbnb Hosts

Direct Answer

The best Claude prompts for online review response for Airbnb hosts are practical, outcome-focused prompts that generate courteous, professional replies tailored to guest feedback, highlight actions taken, and invite future stays. They help maintain reputation while addressing concerns promptly.

Introduction

This page is a practical prompt library for online review response prompts specifically for Airbnb hosts. Use these Claude prompts to craft consistent, high-quality replies to guest feedback, whether praise or concerns.

The prompts are designed to be copyable and actionable, so you can paste them into Claude and customize placeholders to fit your listings and guest situations.

How to Use These Claude Prompts

• Replace placeholders with your guest and stay details before running the prompt.
• Add any necessary constraints such as tone, length, and format to ensure consistency across replies.
• Request outputs in a specific format if you need a structured response (for example, two-sentence reply followed by a call to action).
• Verify the generated reply for accuracy and tone before posting, adapting it to your brand voice as needed.
• If responding to multiple reviews, reuse the template with personalized data for each guest.

100 Best Claude Online Review Response Prompts for Airbnb Hosts

1. Polite thank you reply: Act as a hospitality specialist. Your task is to craft a polite, personalized thank you reply to an Airbnb guest review. Context: guest name is [guestName], rating is [rating], feedback is [feedback], stay dates [dates], property [property]. Output format: short paragraph plus 2 optional sentences inviting future stays. Constraints: maintain a warm, professional tone, avoid excuses, no private details disclosed.
2. Addressing minor issue: Role: guest relations manager. Task: respond to a review noting a minor issue. Context: issue [issue], impact [impact], guestName [guestName], stay [dates], property [property]. Output: a concise apology, explanation if needed, corrective action and timeline, and an invitation for future stay. Tone: empathetic and proactive.
3. Handling a late check-in delay: Position: operations lead. Task: answer a review praising overall stay but mentioning late check‑in. Context: delayReason [reason], remedy [remedy], guestName [guestName], dates [dates], property [property]. Output: acknowledge, apologize, outline steps taken to prevent recurrence, invite next booking with a small incentive. Format: single paragraph.
4. Resolving overpricing concern: Role: pricing and guest experience analyst. Task: respond to a review that cites perceived high price. Context: season [season], comparison [comparison], guestName [guestName], dates [dates], property [property]. Output: explain value, highlight features, offer future discount code if applicable, and invite direct-booking questions. Tone: transparent.
5. Promoting repeat bookings: Position: community manager. Task: craft a response that encourages repeat bookings after a positive review. Context: guestName [guestName], preferred dates [dates], property [property], loyalty program status [status]. Output: a warm thank you, mention rewards, and propose a tailored stay plan for next visit in 2 sentences.
6. Respond to neutral review: Role: guest experience advocate. Task: respond to a neutral review [rating], focusing on improvement. Context: elements [elements], guestName [guestName], dates [dates], property [property]. Output: acknowledge positives, address negatives, outline concrete change, invite future feedback. Output format: two short sentences.
7. Appreciation for host communication: Role: communications specialist. Task: reply to a review praising host responsiveness. Context: response timing [timing], guestName [guestName], property [property]. Output: reinforce value of timely communication, mention ongoing commitment, invite another stay. Tone: friendly and confident.
8. Reassuring safety concerns: Role: safety coordinator. Task: respond to a review mentioning safety concerns. Context: concern [concern], safety steps [steps], guestName [guestName], property [property]. Output: outline safety measures taken, provide contact for follow-up, invite future stay. Format: short paragraph.
9. Clarifying listing accuracy: Role: listing accuracy reviewer. Task: address a review claiming mismatch between listing and reality. Context: mismatch [mismatch], evidence [evidence], guestName [guestName], dates [dates], property [property]. Output: acknowledge, verify facts, outline corrective action, invite direct questions. Tone: factual and calm.
10. Thank you with local tips: Role: concierge. Task: provide a friendly thank you with value-added local tips after a positive review. Context: guestName [guestName], location [location], property [property], dates [dates]. Output: two actionable tips, one custom recommendation, and a warm closing.
11. Handling guest dietary needs: Role: hospitality trainer. Task: respond to a review mentioning dietary needs. Context: needs [needs], accommodations made [accommodations], guestName [guestName], dates [dates], property [property]. Output: acknowledge, confirm options, and invite future stays with dietary accommodations noted. Output format: two sentences.
12. Resolving noise complaints: Role: operations manager. Task: respond to a noise-related review. Context: noise level [level], time [time], actions taken [actions], guestName [guestName], property [property]. Output: summarize mitigation steps, apologize if appropriate, and provide future scheduling tips. Tone: constructive.
13. Communicating improvements after feedback: Role: quality assurance lead. Task: respond to a review with constructive feedback. Context: feedback [feedback], improvements planned [plans], deadline [deadline], guestName [guestName], property [property]. Output: acknowledge, outline plan, offer to update listing, invite future feedback.
14. Special occasion acknowledgment: Role: guest relations. Task: reply to a review noting a special occasion. Context: occasion [occasion], guestName [guestName], dates [dates], property [property]. Output: celebrate, offer small gesture if appropriate, invite return visit.
15. Handling negative experience: Role: customer recovery lead. Task: respond to a negative experience while attempting recovery. Context: issue [issue], impact [impact], remedy [remedy], guestName [guestName], property [property]. Output: concise apology, corrective action, and invitation for future stays; avoid defensiveness.
16. Emergency situation response: Role: safety and service coordinator. Task: respond to review mentioning emergency incident. Context: incident [incident], actions taken [actions], guestName [guestName], property [property]. Output: factual summary, safety reassurance, and offer follow-up assistance.
17. Highlighting property features: Role: marketing writer. Task: respond to positive review by emphasizing unique features. Context: features [features], dates [dates], guestName [guestName], property [property]. Output: two-feature highlight sentences and an invitation to return.
18. Addressing accessibility concerns: Role: accessibility advocate. Task: respond to a review noting accessibility issues. Context: issue [issue], accessibility fixes [fixes], guestName [guestName], property [property]. Output: confirm fixes, provide timeline, invite follow-up visits.
19. Professional tone for business guests: Role: professional host. Task: craft a reply to a business traveler review. Context: company [company], traveler [traveler], stay dates [dates], guestName [guestName], property [property]. Output: concise, business-ready language, mention amenities suited for work, invitation for future trips.
20. Bilingual or multilingual reply: Role: multilingual support. Task: respond in [language] to a review from a non-English speaker. Context: language [language], review [review], guestName [guestName], property [property]. Output: respectful translation and native tone, offer additional language support, invite future stays.
21. Dispute avoidance approach: Role: conflict resolution lead. Task: respond to a review with disputed claims. Context: claims [claims], evidence [evidence], guestName [guestName], dates [dates], property [property]. Output: acknowledge, present facts calmly, propose resolution path, invite ongoing dialogue.
22. Encouraging direct booking: Role: growth marketer. Task: reply to a positive review and nudge toward direct booking. Context: guestName [guestName], dates [dates], property [property], incentive [incentive]. Output: two sentences encouraging direct inquiry, provide direct-booking benefits.
23. Sustainable practices highlight: Role: sustainability advocate. Task: respond to a review praising eco-friendly choices. Context: practices [practices], guestName [guestName], property [property]. Output: summarize eco efforts and invite future stays highlighting green features.
24. Handling party-related feedback: Role: guest services supervisor. Task: respond to a review mentioning a party. Context: party [party], impact [impact], guestName [guestName], dates [dates], property [property]. Output: set expectations, outline noise controls, invite further discussion.
25. Response with local attraction tips: Role: guest experience designer. Task: respond with recommended local attractions after a positive review. Context: attractions [attractions], guestName [guestName], location [location], property [property]. Output: two attractions with quick tips, invite rebooking.
26. Addressing pet-friendly requests: Role: pet-friendly host. Task: respond to a review mentioning pets. Context: petPolicy [policy], guestName [guestName], pet [pet], dates [dates], property [property]. Output: confirm policy, share pet amenities, invite future stays.
27. Handling refund discussions: Role: finance and guest relations. Task: respond to a review requesting a refund. Context: refundRequest [request], reason [reason], guestName [guestName], dates [dates], property [property]. Output: clarify policy, offer goodwill gesture if appropriate, invite direct contact.
28. Thank you after booking confirmation: Role: welcome coordinator. Task: reply after booking is confirmed following a positive review. Context: booking [booking], guestName [guestName], property [property]. Output: warm acknowledgment, highlight prep steps, invite questions.
29. Cultural sensitivity reminder: Role: cultural liaison. Task: respond to a review with a cultural sensitivity note. Context: note [note], guestName [guestName], dates [dates], property [property]. Output: respectful acknowledgement, outline inclusive practices, invite continued stay.
30. Rapid response template: Role: automation engineer. Task: generate a rapid response template for all-new reviews. Context: review [review], guestName [guestName], property [property]. Output: snapshot template with placeholders for personalization.
31. Handling miscommunication risk: Role: guest services lead. Task: respond to a review noting miscommunication. Context: miscommunication [mis], steps [steps], guestName [guestName], dates [dates], property [property]. Output: apologize, clarify, and provide updated contact path for queries.
32. Seasonal welcome note: Role: guest liaison. Task: respond to seasonal review with a welcome note. Context: season [season], guestName [guestName], dates [dates], property [property]. Output: warm seasonal greeting, highlight seasonal amenities, invite return visit.
33. Time zone and checkout clarity: Role: operations lead. Task: respond to a review asking about checkout timing. Context: time [time], guestName [guestName], dates [dates], property [property]. Output: provide clear checkout instructions, any late checkout options, and invitation for future stays.
34. Incentive-based appreciation: Role: loyalty programs manager. Task: craft a reply that offers a small incentive after a positive review. Context: incentive [incentive], guestName [guestName], property [property]. Output: two sentences: appreciation plus incentive details.
35. Non-English guest gratitude: Role: language specialist. Task: respond to a review in another language with a courtesy English translation. Context: language [language], translationNeeded [true], guestName [guestName], property [property]. Output: brief bilingual reply.
36. Complying with house rules: Role: compliance trainer. Task: respond to a review citing house rules. Context: rules [rules], guestName [guestName], dates [dates], property [property]. Output: concise reassurance, reference relevant rule, and invite future stays.
37. Handling counterfeit claims: Role: risk manager. Task: respond to a review alleging false claims. Context: claims [claims], evidence [evidence], guestName [guestName], dates [dates], property [property]. Output: neutral, fact-based response, offer to discuss privately, invite future stays.
38. Highlighting host availability: Role: guest relations. Task: respond to a review praising host availability. Context: availability [availability], guestName [guestName], property [property]. Output: thank, confirm ongoing availability, invite another visit.
39. Promoting local partnerships: Role: partnerships coordinator. Task: respond to a review by mentioning local partnerships. Context: partners [partners], guestName [guestName], property [property]. Output: mention benefits, invite follow-up inquiries, invite future stays.
40. Technical issue acknowledgment: Role: tech support liaison. Task: respond to a review mentioning a technical issue (Wi-Fi, smart TV). Context: issue [issue], fix [fix], guestName [guestName], dates [dates], property [property]. Output: acknowledge, summarize fix, ensure reliability, invite future stays.
41. Family-friendly messaging: Role: family-host coordinator. Task: respond to a family-friendly review. Context: family [family], kids [kids], guestName [guestName], property [property]. Output: emphasize family amenities, safety, and invite future family stays.
42. Wedding or event hosting note: Role: event host. Task: respond to a review mentioning a wedding or event. Context: event [event], guestName [guestName], dates [dates], property [property]. Output: celebrate, outline event support services, invite future events.
43. Concise professional reply: Role: executive assistant. Task: craft a concise professional reply to a positive review. Context: guestName [guestName], property [property], dates [dates]. Output: two sentences max, professional tone, clear invitation for future stays.
44. Environmental impact acknowledgment: Role: sustainability manager. Task: respond to a review noting environmental impact. Context: impact [impact], actions [actions], guestName [guestName], property [property]. Output: acknowledge, summarize green actions, invite future stays.
45. Accessibility feature highlight: Role: accessibility coordinator. Task: respond to a review praising accessible features. Context: features [features], guestName [guestName], property [property]. Output: confirm features, offer upgrades, invite future stays.
46. Pet guest appreciation: Role: pet-friendly host. Task: respond to a pet owner review. Context: pet [pet], policy [policy], guestName [guestName], dates [dates], property [property]. Output: acknowledge pet-friendly setup, invite future pet visits.
47. Crisis communication ready: Role: crisis comms lead. Task: draft a safe, calm response to a negative incident review. Context: incident [incident], actions [actions], guestName [guestName], property [property]. Output: concise, transparent update, offer private follow-up, invite future stays.
48. Amenities spotlight: Role: product marketing. Task: respond to a review by highlighting amenities. Context: amenities [amenities], guestName [guestName], property [property]. Output: two benefit-led sentences, invite return visits.
49. Cultural vacation tips: Role: cultural liaison. Task: respond with tips for culturally rich experience after a positive review. Context: culture [culture], guestName [guestName], location [location], property [property]. Output: two actionable tips and invitation for future stays.
50. Clear checkout guidance: Role: operations coordinator. Task: respond to a review asking about checkout. Context: checkoutTime [time], lateOption [lateOption], guestName [guestName], dates [dates], property [property]. Output: precise checkout details, any fees, invite future stays.
51. First-time guest welcome: Role: onboarding specialist. Task: reply to a first-time guest review with a welcome and onboarding tips. Context: guestName [guestName], property [property], dates [dates]. Output: warm welcome, core house rules, and how to reach help.
52. Highlighting safety drills: Role: safety trainer. Task: respond to review by mentioning safety drills. Context: drills [drills], guestName [guestName], property [property]. Output: brief summary of drills, reassurance, invite future stays.
53. Clear listing corrections: Role: listing moderator. Task: respond to a review suggesting corrections to listing. Context: corrections [corrections], guestName [guestName], dates [dates], property [property]. Output: acknowledge, note update plan, invite questions.
54. Guest privacy pledge: Role: privacy advocate. Task: respond to a review emphasizing privacy. Context: privacy measures [measures], guestName [guestName], property [property]. Output: outline privacy safeguards, encourage future stays.
55. Language-neutral response: Role: neutral tone specialist. Task: respond to a multilingual review with a language-neutral version. Context: review [review], languages [languages], guestName [guestName], property [property]. Output: neutral English version plus placeholder for translation.
56. Promote loyalty benefits: Role: loyalty program manager. Task: respond to a positive review by highlighting loyalty benefits. Context: benefits [benefits], guestName [guestName], property [property]. Output: two sentences, invite joining loyalty program, and direct booking advantage.
57. Time-saving recap: Role: assistant editor. Task: summarize a long review into a concise recap. Context: review [review], guestName [guestName], property [property]. Output: 3 sentences max, capture key points.
58. Guest milestone acknowledgment: Role: guest relations. Task: acknowledge a review referencing a milestone stay. Context: milestone [milestone], guestName [guestName], dates [dates], property [property]. Output: congratulations, recap preferences, invite return.
59. Detailed amenity list: Role: content strategist. Task: respond with a structured amenity list after a positive review. Context: amenities [amenities], guestName [guestName], property [property]. Output: bullet-point style list in prose without HTML.
60. Guest follow-up invitation: Role: guest services lead. Task: invite reviewer to share next-trip plans. Context: upcoming [upcoming], guestName [guestName], property [property]. Output: two sentences encouraging direct booking and feedback.
61. Nudging for high-tech reviews: Role: product marketer. Task: encourage reviews that mention technology features. Context: techFeatures [features], guestName [guestName], property [property]. Output: two sentences highlighting tech and invite future stays.
62. Post-stay feedback channel: Role: community manager. Task: provide a channel for ongoing feedback after stay. Context: channel [channel], guestName [guestName], property [property]. Output: share contact path, encourage future stays.
63. Explain listing pricing: Role: pricing analyst. Task: respond to a review about pricing by explaining value. Context: price [price], value [value], guestName [guestName], dates [dates], property [property]. Output: transparent value explanation, invite questions.
64. Non-confrontational tone: Role: conflict coach. Task: respond to a heated review without escalating. Context: tone [tone], issue [issue], guestName [guestName], property [property]. Output: de-escalation, problem-solving steps, invitation for future stays.
65. Celebrating repeat guests: Role: guest relations lead. Task: reply to a returning guest review. Context: guestName [guestName], repeatStatus [status], property [property]. Output: welcome back, summarize improvements, invite next stay.
66. Transparency about schedules: Role: operations supervisor. Task: respond to review citing scheduling changes. Context: schedule [schedule], guestName [guestName], property [property]. Output: clear schedule update, apology if needed, invite future stays.
67. In-room welcome note: Role: host concierge. Task: respond to a review with an in-room welcome note. Context: welcomeNote [note], guestName [guestName], property [property]. Output: warm, concise note.
68. Immediate corrective action: Role: repair coordinator. Task: respond to a review calling out a broken item. Context: item [item], fixTime [time], guestName [guestName], property [property]. Output: acknowledge, share repair plan and ETA, invite future stays.
69. Bathroom and cleanliness focus: Role: housekeeping supervisor. Task: respond to a cleanliness-related review. Context: cleanliness [cleanliness], guestName [guestName], property [property]. Output: describe cleaning standards, corrective steps, invite future stays.
70. Guest request pipeline: Role: front desk lead. Task: respond to a guest request noted in review. Context: request [request], status [status], guestName [guestName], property [property]. Output: confirm receipt, expected timeline, ask for confirmation.
71. Check-in experience improvement: Role: guest experience designer. Task: respond to review about check-in. Context: checkin [checkin], guestName [guestName], property [property]. Output: summarize process, upcoming changes, invite future stays.
72. Respectful disagreement: Role: mediator. Task: respond to a review with a respectful disagreement. Context: dispute [dispute], guestName [guestName], property [property]. Output: acknowledge, present alternative view, invite continued conversation.
73. Transport tips: Role: travel assistant. Task: provide transport tips in reply to a review. Context: transport [transport], guestName [guestName], location [location], property [property]. Output: two practical tips, invite future stays.
74. Hosting metrics update: Role: analytics lead. Task: respond with a quick metrics update after a positive review. Context: metrics [metrics], guestName [guestName], property [property]. Output: one sentence on improvement and invitation for return stays.
75. Guest safety follow-up: Role: safety officer. Task: follow up after a safety-related review. Context: safetyUpdate [update], guestName [guestName], property [property]. Output: reassurance, further safety steps, invitation for future stays.
76. Neighborhood respect note: Role: community liaison. Task: respond to a review requesting neighborhood respect. Context: neighborhood [neighborhood], guestName [guestName], property [property]. Output: outline respectful practices, invite future stays.
77. Culinary recommendations: Role: local chef host. Task: respond to a review by sharing two local dining suggestions. Context: cuisine [cuisine], guestName [guestName], location [location], property [property]. Output: two concise recommendations and invite future stays.
78. Post-stay survey prompt: Role: insights lead. Task: prompt guest to complete a post-stay survey after a positive review. Context: survey [survey], guestName [guestName], property [property]. Output: one-sentence call to action plus reassurance.
79. Handling misbookings: Role: operations manager. Task: respond to a review mentioning misbooking. Context: misbooking [misbooking], guestName [guestName], dates [dates], property [property]. Output: clarify, correct if needed, invite future stays.
80. Feature request acknowledgment: Role: product owner. Task: respond to a review that requests a new feature. Context: feature [feature], guestName [guestName], property [property]. Output: acknowledge, share feasibility, invite additional ideas.
81. Crisis prep update: Role: resilience planner. Task: respond to a review about a recent disruption. Context: disruption [disruption], actions taken [actions], guestName [guestName], property [property]. Output: concise update, safety assurance, invite future stays.
82. Garden or outdoor space pride: Role: landscape coordinator. Task: respond to a review highlighting outdoor space. Context: space [space], guestName [guestName], property [property]. Output: describe features, maintenance schedule, invite return visits.
83. Disability access reassurance: Role: accessibility advocate. Task: respond to a review about disability access. Context: access [access], accommodations [accommodations], guestName [guestName], property [property]. Output: confirm accessibility details, invite future stays.
84. Quiet hours reminder: Role: concierge supervisor. Task: respond to a review requesting quiet hours enforcement. Context: hours [hours], guestName [guestName], property [property]. Output: reaffirm policy, describe steps to ensure quiet, invite future stays.
85. Hosting anniversary note: Role: host community manager. Task: respond to a review mentioning hosting anniversary. Context: anniversary [anniversary], guestName [guestName], property [property]. Output: celebrate milestone, highlight progress, invite return visits.
86. Midweek stay encouragement: Role: demand creator. Task: respond to a midweek positive review. Context: days [days], guestName [guestName], property [property]. Output: promote off-peak incentives, invite weekdays stays.
87. Reaffirm listing accuracy: Role: listing steward. Task: respond to a review asserting accuracy. Context: accuracy [accuracy], guestName [guestName], property [property]. Output: confirm features, invite questions, update listing if needed.
88. Check-in personal welcome: Role: host assistant. Task: create a personal welcome message for check-in in response to a review. Context: guestName [guestName], property [property]. Output: two-sentence welcome.
89. Handling payment clarifications: Role: payments coordinator. Task: respond to a review asking about charges. Context: charges [charges], guestName [guestName], property [property]. Output: explain charges, rationale, invite future stays.
90. Community impact note: Role: community liaison. Task: respond to a review discussing local impact. Context: impact [impact], guestName [guestName], property [property]. Output: summarize benefits to neighborhood and invite future stays.
91. Tailored welcome for repeats: Role: guest experience lead. Task: create a tailored welcome for a returning guest after a positive review. Context: guestName [guestName], repeatStatus [status], property [property]. Output: personalized welcome and suggested tweaks for next stay.
92. Public safety reminder: Role: safety officer. Task: respond to a review with safety reminder. Context: reminder [reminder], guestName [guestName], property [property]. Output: brief reminder, offer safety resources, invite future stays.
93. Concise apology and fix: Role: guest relations. Task: respond to a review with apology and clear fix steps. Context: issue [issue], fix [fix], guestName [guestName], property [property]. Output: apology, fix timeline, invite future stays.
94. Curbside check-in option: Role: operations manager. Task: respond to a review about curbside check-in. Context: curbside [curbside], guestName [guestName], property [property]. Output: confirm option, benefits, invite future stays.
95. Handling last-minute booking praise: Role: growth hacker. Task: respond to praise for last-minute booking. Context: booking [booking], guestName [guestName], property [property]. Output: acknowledge, highlight flexibility, invite future stays.
96. Guest resource library invite: Role: content strategist. Task: invite reviewer to join guest resource library after positive review. Context: library [library], guestName [guestName], property [property]. Output: brief invite and benefits.
97. Illustrative how-to tips: Role: educator. Task: respond with two practical how-to tips related to the stay. Context: tips [tips], guestName [guestName], property [property]. Output: two actionable tips.
98. Negative review turn-around: Role: customer success. Task: outline turnaround steps after a negative review in response. Context: timeline [timeline], guestName [guestName], property [property]. Output: steps, timeline, invite future stays.
99. Transparent cancellation note: Role: policy manager. Task: respond to a review mentioning cancellation. Context: policy [policy], guestName [guestName], dates [dates], property [property]. Output: explain policy, exception if applicable, invite future stays.
100. Final thank you and invitation: Role: host ambassador. Task: end with a warm thank you and invitation to book again directly. Context: guestName [guestName], property [property], dates [dates]. Output: two sentences: gratitude and direct-booking invitation.

Best Practices

• Use a calm, empathetic tone and acknowledge guest feedback first.
• Include concrete actions taken or planned to address issues.
• Keep replies concise and easy to read; avoid jargon and defensiveness.
• Tailor responses to reflect your property's unique features and guest expectations.
• Test prompts with a few sample reviews to refine placeholders and tone.

Common Mistakes to Avoid

• Using a defensive tone or blaming guests.
• Overpromising and underdelivering on fixes.
• Posting one-size-fits-all replies that ignore context.
• Including private or sensitive details in public responses.
• Neglecting to personalize replies or reference specific review points.

FAQ

What makes a good Claude response for Airbnb reviews?

A good Claude response is empathetic, specific, and actionable, acknowledges the guest, provides clarity on any fixes, and invites the guest to return.

How can I adapt prompts for different listings?

Fill in the placeholders with property-specific details, adjust tone for the audience, and add constraints to match your brand voice.

Can I use these prompts for automation without losing quality?

Yes, by using placeholders and constraints to generate consistent, high-quality replies that can be reviewed and lightly edited before posting.

What should I do with negative reviews?

Acknowledge the issue, apologize if appropriate, explain steps taken, offer a path to resolution, and invite future stays.

How do I ensure replies stay within brand voice?

Define a concise brand voice guide and apply it consistently in prompts, with templated cues for tone and formality.

Is it okay to suggest future stays in replies?

Yes, when done tactfully, it can convert feedback into a new booking without pressuring the guest.