100 Best Claude Employee Handbook Prompts for Airbnb Hosts

Direct Answer

The best Claude prompts for employee handbook for Airbnb hosts are a curated set of practical instructions that help hosts define responsibilities, safety, compliance, and guest experience in a consistent, scalable way. This collection focuses on onboarding, incident response, check-in and check-out, communication, and local regulations, all tailored for Airbnb host teams.

Introduction

This page delivers a practical Claude prompt library for creating and maintaining an employee handbook for Airbnb hosts. It is designed for property managers, host teams, and co-hosts who operate multiple listings.

Use these prompts to standardize host roles, guest policies, safety procedures, and operations across all properties, ensuring consistent guest experiences and compliant practices.

How to Use These Claude Prompts

• Replace placeholders like [listing], [location], [host], and [guest] with your real names or codes for each property. Add or adjust constraints to fit local laws and your brand voice. Request outputs in clear formats such as bullet lists, checklists, or templates that can be pasted into your handbook. Validate outputs by cross-checking with your existing policies and local regulations. If outputs are long, ask for a condensed version suitable for the handbook’s printed section.

100 Best Claude Employee Handbook Prompts for Airbnb Hosts

1. Onboarding responsibilities: Role: HR coordinator for Airbnb hosts. Task: Draft onboarding responsibilities for new hosts. Context: Company operates multiple listings; use a standardized handbook template. Output: bullet list for onboarding steps with ownership and due dates. Constraints: keep to six bullets; no vendor-specific tools; include safety briefing.
2. Guest safety overview: Role: Safety trainer for Airbnb hosts. Task: Create guest safety overview for the handbook. Context: Include emergency contacts, local regulations, and basic safety procedures. Output: a concise section with 8 bullet points and a one-paragraph summary. Constraints: exclude legal advice; cite internal policy numbers.
3. Check-in protocol map: Role: Operations manager. Task: Define check-in protocol by listing steps from booking to arrival. Context: Multiple properties with different access methods. Output: step-by-step checklist for hosts and co-hosts. Constraints: include timing windows and required data collection.
4. Host code of conduct: Role: HR policy author. Task: Write a host code of conduct for all listings. Context: Align with brand values and legal compliance. Output: short paragraph plus five bullet rules. Constraints: emphasize respect, privacy, and non-discrimination.
5. Communication templates: Role: Communications lead. Task: Provide templates for guest messages pre-check-in, post-stay, and issue reporting. Context: Maintain friendly tone and clear escalation steps. Output: three templates with placeholders for names, dates, and issue codes. Constraints: include a call to action in each.
6. Service standards: Role: Quality assurance lead. Task: Define service standards for host responses and cleaning times. Context: Cover check-in to check-out interactions. Output: table-like list with expected response times, cleanliness levels, and guest feedback handling. Constraints: avoid industry jargon; provide measurable targets.
7. Incident escalation flow: Role: Incident manager. Task: Create an escalation flow for incidents during a guest stay. Context: Varying severity levels; include contact methods for guests and hosts. Output: flowchart-like steps described in text. Constraints: specify response windows and handoff points.
8. Cleaning and turnover policy: Role: Operations policy writer. Task: Document cleaning standards and turnover routines. Context: Multiple properties with different schedules. Output: checklist with required tasks, responsible person, and verification method. Constraints: include safety and waste disposal guidelines.
9. Pet and amenity policy: Role: Policy author. Task: Draft pet policy and amenity usage guidelines for hosts. Context: Some listings are pet-friendly. Output: policy section plus a FAQ. Constraints: define fee structure and exception process.
10. Guest privacy guidelines: Role: Compliance officer. Task: Write guest privacy and data handling guidelines for hosts. Context: Data collected during booking and stays. Output: policy with data-minimization rules and retention periods. Constraints: reference local privacy laws where applicable.
11. Room setup standards: Role: Property manager. Task: Define minimum room setup standards for new listings. Context: Include bed configuration, amenities, and branding. Output: bullet list plus photos checklist. Constraints: ensure accessibility features are covered.
12. Check-out process: Role: Front desk coordinator. Task: Create a standardized check-out script and tasks. Context: Quick turnover to next guest. Output: step-by-step script and verification checklist. Constraints: include lost-and-found protocol.
13. Guest complaint handling: Role: Guest relations lead. Task: Provide a formal process for handling complaints. Context: Tiered escalation to owner or platform support. Output: flow with response times and templates. Constraints: prioritize empathy and resolution clarity.
14. Local regulations compliance: Role: Compliance analyst. Task: Compile a list of local hosting regulations for listings. Context: Multiple jurisdictions. Output: summarized requirements by location with owner responsibilities. Constraints: avoid legal advice; cite official sources.
15. Host onboarding checklist: Role: Onboarding coordinator. Task: Build a host onboarding checklist for new hires and co-hosts. Context: Standardized across properties. Output: checklist with owners, check items, and due dates. Constraints: include training assessments.
16. Emergency contact sheet: Role: Safety officer. Task: Create an emergency contact sheet for each listing. Context: Include fire, medical, and security contacts. Output: one-page sheet per listing in plain text. Constraints: include language notes for guests.
17. Guest review handling: Role: Reputation manager. Task: Outline how hosts should respond to guest reviews. Context: Positive and negative reviews. Output: response templates and a sentiment guide. Constraints: avoid defensive language.
18. Property maintenance log: Role: Facilities manager. Task: Define a maintenance logging policy. Context: Regular tasks and incident repairs. Output: log fields, turnaround times, and verification method. Constraints: include privacy considerations for service providers.
19. Safety drill schedule: Role: Safety trainer. Task: Plan periodic safety drills for listings. Context: Fire, evacuation, and medical emergencies. Output: schedule with drill objectives and participant roles. Constraints: require post-drill debrief.
20. Service language guidelines: Role: Brand manager. Task: Create a language guideline for all host communications. Context: Consistent tone across channels. Output: tone matrix and example phrases. Constraints: avoid jargon; promote clarity.
21. Guest data retention: Role: Privacy officer. Task: Define data retention periods for booking data. Context: Vary by listing type. Output: retention schedule with deletion triggers. Constraints: minimize data collection.
22. Check-in verification: Role: Security lead. Task: Outline check-in verification steps for guests. Context: Different access methods. Output: list of verification actions and acceptable proofs. Constraints: include privacy-respecting alternatives.
23. Inventory management: Role: Operations analyst. Task: Create an inventory control policy for essential supplies. Context: Multiple listings. Output: stock levels, reorder points, and supplier contact info. Constraints: include seasonal adjustments.
24. Guest welcome packet: Role: Guest experience designer. Task: Design a digital welcome packet for guests. Context: Provide essential info and tips. Output: structured sections with hyperlinks placeholders. Constraints: tailor by listing.
25. Accessibility guidelines: Role: Inclusion officer. Task: Draft accessibility requirements for listings. Context: Variants across properties. Output: accessible features checklist and accommodation process. Constraints: include contact method for accessibility requests.
26. Crisis communication plan: Role: Communications lead. Task: Prepare a crisis communication guide for hosts. Context: Natural disasters or platform outages. Output: messaging templates and escalation paths. Constraints: provide a do-not-use list.
27. Guest refund policy: Role: Finance policy writer. Task: Develop a guest refund policy aligned with platform terms. Context: Various scenarios. Output: refund rules, timelines, and approval routes. Constraints: require supervisor sign-off for exceptions.
28. House rules customization: Role: Policy designer. Task: Create house rules templates per listing type. Context: Different property types. Output: modular rules with placeholders for room types. Constraints: align with brand voice.
29. Brand voice guidelines: Role: Brand strategist. Task: Document brand voice for host communications. Context: Consistent across listings and guests. Output: voice examples and do/don'ts. Constraints: include conflict-resolution phrases.
30. Guest accessibility requests: Role: Support coordinator. Task: Define process for handling accessibility requests. Context: Before and during stay. Output: request intake form and response templates. Constraints: track request status.
31. Guest check-in timing policy: Role: Scheduling lead. Task: Set host expectations for check-in timing windows. Context: Different time zones and listings. Output: policy with examples. Constraints: include penalty-free flexibility guidance.
32. Waste and recycling policy: Role: Sustainability officer. Task: Document waste and recycling guidelines for hosts. Context: Local regulations vary. Output: guidelines per listing with disposal steps. Constraints: include hazardous material notes.
33. Drop-off and pickup procedures: Role: Operations supervisor. Task: Create procedures for guest arrival and checkout logistics. Context: Shared spaces or key drop points. Output: sequence of steps with verification points. Constraints: ensure privacy and security.
34. Noise and mutual respect: Role: Community manager. Task: Draft noise policy and dispute resolution. Context: Shared walls and neighborhood rules. Output: guidelines and escalation process. Constraints: include quiet hours.
35. Service failure protocol: Role: Incident responder. Task: Create a protocol for service outages or issues. Context: Platform, internet, or utility failures. Output: incident log, host actions, and guest communication templates. Constraints: document recovery steps.
36. Payment and refunds overview: Role: Finance manager. Task: Outline payment flows and refund handling. Context: Booking platform integration. Output: flow diagram in text and sample calculations. Constraints: ensure compliance.
37. Checklist for new listings: Role: Listing coordinator. Task: Provide a startup checklist for new hosts. Context: From contract signing to first guest. Output: task list with owners and due dates. Constraints: include photo and policy setup steps.
38. Emergency drill debrief: Role: Safety lead. Task: Create debrief templates after drills. Context: Evaluate performance and improvements. Output: structured questions and action items. Constraints: assign owners.
39. Guest cancellation policy: Role: Policy author. Task: Draft cancellation terms for hosts. Context: Various scenarios and timing. Output: policy section with examples. Constraints: align with platform terms.
40. Local emergency numbers: Role: Compliance analyst. Task: List local emergency numbers per listing location. Context: Listings in different regions. Output: directory by location with notes. Constraints: include non-emergency contacts.
41. Lost and found procedure: Role: Operations manager. Task: Define lost and found handling. Context: Multiple listings. Output: step-by-step process and record-keeping. Constraints: privacy-preserving notes.
42. Guest loyalty program: Role: Marketing lead. Task: Outline a simple guest loyalty rewards program. Context: Applicable to some listings. Output: program rules, eligibility, and redemption steps. Constraints: track metrics.
43. Staff training modules: Role: Training coordinator. Task: Create core training modules for hosts and co-hosts. Context: Roles vary by listing. Output: module outlines with objectives and assessments. Constraints: include practical exercises.
44. Handling illegal activity: Role: Compliance officer. Task: Provide a zero-tolerance policy and response plan. Context: Potential illegal activity incidents. Output: policy, escalation paths, and reporting templates. Constraints: avoid accusations without evidence.
45. Guest feedback loop: Role: Experience analyst. Task: Establish a feedback loop to improve listings. Context: Regular surveys and reviews. Output: workflow with data capture and action items. Constraints: ensure guest anonymity where appropriate.
46. Self-service support guides: Role: Support lead. Task: Create self-service prompts for common guest questions. Context: Quick responses to reduce workload. Output: FAQ-style prompts with structured answers. Constraints: avoid long responses.
47. Inventory restock policy: Role: Operations planner. Task: Define restock triggers for amenities. Context: Multiple listings. Output: reorder points, preferred vendors, approval steps. Constraints: budget limits.
48. Sustainability commitments: Role: Brand and policy lead. Task: Document sustainability practices hosts must follow. Context: Energy, water, waste. Output: policy with measurable targets. Constraints: report progress quarterly.
49. Guest profile handling: Role: Data privacy officer. Task: Define how host handles guest profiles. Context: Booking history and preferences. Output: privacy-first handling rules and access controls. Constraints: limits on data sharing.
50. Guest arrival checklists: Role: Front desk supervisor. Task: Provide arrival checklists for hosts. Context: Early check-ins and multi-listing. Output: form with required verifications and notes. Constraints: digital or printed formats.
51. Safety equipment inventory: Role: Facilities manager. Task: Create an inventory policy for safety equipment. Context: Fire extinguishers, first aid kits. Output: stock log, inspection schedule, and replacement plan. Constraints: labeling and accessibility.
52. After-stay cleaning guide: Role: Cleaning supervisor. Task: Document post-stay cleaning steps. Context: Turnover efficiency. Output: task list with quality checks. Constraints: include odor control and sanitization notes.
53. Guest etiquette guide: Role: Guest experience lead. Task: Compile etiquette expectations for hosts and guests. Context: Culture and safety. Output: concise guide with examples. Constraints: avoid judgmental language.
54. Incident reporting templates: Role: Compliance administrator. Task: Provide standardized incident report templates. Context: Various incident types. Output: forms with data fields and submission flow. Constraints: ensure accuracy.
55. Co-host coordination: Role: Operations supervisor. Task: Define co-host roles and handoffs. Context: Multiple listings managed by teams. Output: coordination protocol and checklist. Constraints: clarify authority.
56. Noise complaint protocol: Role: Community liaison. Task: Create a noise complaint response protocol. Context: Night-time disturbances. Output: escalation path and host response templates. Constraints: respect residents.
57. Check-out refunds: Role: Finance officer. Task: Outline when refunds apply at check-out. Context: Cleanliness or amenity issues. Output: refund criteria and approval steps. Constraints: tie to guest satisfaction.
58. Guest data access policy: Role: Privacy officer. Task: Define who can access guest data. Context: Roles across teams. Output: access control matrix and approval workflow. Constraints: minimize access.
59. Staff schedule policy: Role: HR planner. Task: Establish scheduling guidelines for hosts. Context: Part-time and full-time helpers. Output: schedule norms and approval process. Constraints: avoid conflicts.
60. Property branding guidelines: Role: Brand manager. Task: Document listing-by-listing branding. Context: Visuals, language, and tone. Output: style guide with examples. Constraints: ensure consistency.
61. Host termination policy: Role: Legal and HR. Task: Draft termination guidelines for hosts and co-hosts. Context: Performance or policy violations. Output: process with notice and appeals. Constraints: protect both sides.
62. Welcome message templates: Role: Guest relations lead. Task: Provide welcome message templates for new guests. Context: Different listing types. Output: a set of five templates with placeholders. Constraints: include a local tip.
63. Policy compliance checks: Role: Audit lead. Task: Create a quarterly policy compliance checklist. Context: All listings. Output: audit items and scoring. Constraints: assign owners.
64. Guest problem solving: Role: Support agent. Task: Provide a problem-solving prompt for common issues. Context: Booking glitches, utilities. Output: stepwise resolution prompts with options. Constraints: include escalation cues.
65. Local partnerships: Role: Partnerships manager. Task: Outline policy for listing partnerships with local businesses. Context: Discounts or perks for guests. Output: protocol and approval steps. Constraints: avoid conflict.
66. Host performance metrics: Role: Analytics lead. Task: Define host performance metrics for handbook. Context: Response times, guest satisfaction. Output: KPI definitions and data sources. Constraints: include targets.
67. Guest contact preferences: Role: CRM lead. Task: Document how to collect and honor guest contact preferences. Context: Communication channels. Output: policy with consent steps. Constraints: respect opt-out.
68. Equipment usage rules: Role: Facilities supervisor. Task: Provide rules for using shared equipment. Context: Safety and liability. Output: usage guidelines and checklists. Constraints: include maintenance notes.
69. Service recovery steps: Role: Customer experience lead. Task: Establish service recovery flow after a negative experience. Context: Feedback loop with compensation. Output: templates and thresholds. Constraints: prioritize guest partiality.
70. Rooms and amenities inventory: Role: Inventory manager. Task: Create an inventory catalog for rooms and amenities. Context: Listings with variants. Output: catalog with counts and condition notes. Constraints: update quarterly.
71. Guest safety training: Role: Training supervisor. Task: Develop safety training modules for hosts. Context: Fire, first aid, evacuation. Output: module outlines and assessments. Constraints: include hands-on drills.
72. Cultural sensitivity guidelines: Role: Inclusion lead. Task: Document cultural sensitivity in host communications. Context: International guests. Output: guidelines and example phrases. Constraints: avoid stereotypes.
73. Sanitation standards: Role: Sanitation officer. Task: Outline sanitation procedures for listings. Context: Cleaning products and techniques. Output: step-by-step guide with verification points. Constraints: include safety data references.
74. Guest consent forms: Role: Compliance administrator. Task: Create guest consent prompts for data use. Context: Booking and follow-ups. Output: consent templates with opt-in boxes. Constraints: store records securely.
75. Workflow automation prompts: Role: Automation engineer. Task: Propose prompts to automate handbook updates. Context: Version control and approvals. Output: automation prompts and triggers. Constraints: avoid over-automation.
76. Guest check-in accessibility: Role: Accessibility coordinator. Task: Ensure check-in is accessible to all guests. Context: Listings with varying access. Output: accessibility tweaks and template messages. Constraints: document accommodations.
77. Host recall policy: Role: Risk manager. Task: Outline recall procedures for safety issues. Context: Listings with recall risks. Output: plan with communication steps. Constraints: include regulatory alignment.
78. Guest loyalty survey: Role: Research lead. Task: Design guest loyalty survey within handbook. Context: Measure satisfaction and improvements. Output: survey questions and scoring. Constraints: keep concise.
79. Policy update cadence: Role: Policy owner. Task: Set cadence for handbook updates. Context: Regulatory changes and guest feedback. Output: update schedule and approval steps. Constraints: publish change log.
80. Vendor management: Role: Procurement lead. Task: Document vendor selection and hosting agreements. Context: Cleaning, maintenance, supplies. Output: evaluation criteria and contract basics. Constraints: include performance metrics.
81. Guest language preferences: Role: Communications lead. Task: Capture and honor guest language preferences. Context: Multilingual listings. Output: language-tagged templates and translation tips. Constraints: offer fallback options.
82. Property-specific SOPs: Role: SOP developer. Task: Create standard operating procedures per listing. Context: Unique layouts and rules. Output: SOPs with steps and owners. Constraints: include review dates.
83. Escalation contact list: Role: Ops coordinator. Task: Compile escalation contact list by property. Context: Urgent issues. Output: contact details with response times. Constraints: include backup contacts.
84. Guest stay tips: Role: Guest experience planner. Task: Provide host tips to improve stays. Context: Listings with differing guest types. Output: tips and example phrases. Constraints: focus on hospitality.
85. Data minimization policy: Role: Privacy officer. Task: Limit data collection to essential data. Context: Booking and stays. Output: minimization rules and examples. Constraints: audit readiness.
86. Environment and energy: Role: Sustainability lead. Task: Define energy-saving hosting practices. Context: Utilities usage per listing. Output: guidelines and monitoring steps. Constraints: set targets.
87. Guest screening policy: Role: Compliance analyst. Task: Outline screening criteria for guests. Context: Local laws and platform rules. Output: policy with approval workflow. Constraints: respect privacy.
88. Checklist for disruption: Role: Operations manager. Task: Prepare disruption response checklist for hosts. Context: Power outages, water outages. Output: response steps and communication templates. Constraints: safety first.
89. Guest support hours: Role: Support manager. Task: Define support hours and coverage. Context: Global listings. Output: policy with on-call procedures. Constraints: ensure timely responses.
90. Guest check-in tech: Role: IT admin. Task: Recommend tech setup for smooth check-in. Context: Locks, apps, wifi. Output: recommended devices and configurations. Constraints: privacy-safe defaults.
91. Listing safety checklist: Role: Safety officer. Task: Create per-listing safety checklists. Context: Fire, carbon monoxide, exits. Output: checklist with verification fields. Constraints: include remediation steps.
92. Brand incident templates: Role: Brand manager. Task: Provide templates for public incident response. Context: Negative publicity or safety concerns. Output: ready-to-use statements. Constraints: avoid blaming guests.
93. Safety equipment maintenance: Role: Facilities technician. Task: Schedule maintenance for safety gear. Context: Periodic inspections. Output: calendar and log entries. Constraints: replacement thresholds.
94. Property access policy: Role: Security lead. Task: Document access control for listings. Context: Who can enter, when, and why. Output: access policy with visitor logs. Constraints: respect privacy.
95. Guest Wi-Fi usage: Role: IT and safety lead. Task: Create policy for wifi usage and security. Context: Public networks and private data. Output: guidelines and troubleshooting tips. Constraints: avoid legal risk.
96. House manual structure: Role: Content architect. Task: Define structure of house manual per listing. Context: Essential info and tips. Output: outline with sections and templates. Constraints: include safety notices.
97. Local vendor escalation: Role: Operations supervisor. Task: Provide escalation path for vendor failures. Context: Cleaning and maintenance. Output: contact tree and SLA expectations. Constraints: document back-ups.
98. Guest privacy breach plan: Role: Privacy officer. Task: Prepare breach response plan. Context: Data exposure risk. Output: steps, notifications, and remediation actions. Constraints: align with regulations.
99. Co-host handbook section: Role: HR writer. Task: Draft a co-host handbook section. Context: Role responsibilities and collaboration. Output: structured section with examples. Constraints: consistency with main handbook.
100. Final handbook update: Role: Policy editor. Task: Compile final handbook update draft. Context: All previous prompts integrated. Output: cohesive handbook chapter with sections and cross-references. Constraints: ensure consistency and accuracy.

Best Practices

• Keep prompts modular so you can reuse sections across listings.
• Ask for outputs in structured formats that map directly to handbook sections.
• Test prompts with a pilot group of hosts and revise based on feedback.
• Regularly update prompts to reflect regulatory changes and evolving guest expectations.

Common Mistakes to Avoid

• Using generic prompts that lack property-specific context.
• Overloading prompts with too many constraints, causing incomplete outputs.
• Neglecting to include local laws or platform terms.
• Assuming uniform requirements across all listings without listing-specific prompts.

FAQ

How should I customize prompts for different listing types?

Use listing-type placeholders like [listing type] and request a modular output that can be assembled per listing.

Can I reuse prompts for multiple hosts and locations?

Yes, keep prompts generic with clear placeholders and refer to listing-specific data in the handbook sections.

What output formats are best for handbooks?

Bulleted lists, checklists, templates, and short policy paragraphs are easiest to paste into handbooks.

How often should the handbook prompts be updated?

Update prompts quarterly or when local regulations or brand policies change.

How do I ensure compliance across different jurisdictions?

Incorporate jurisdiction-specific sections, reference official sources, and add an escalation path for non-compliance.