Claude Prompt Library

30 Claude Prompts Built for Hotel and Hospitality Teams

30 copy-paste prompts

Paste in your property details, guest name, and dates, and get back a finished guest email, review reply, or front desk SOP, ready to send. Not "give me some advice on guest experience".

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup ยท Founder, Techpresso
Last updated ยทHand-curated & tested by the AI Academy team

Guest Communications

5 prompts

Pre-Arrival Welcome Email

1/30

You are a senior guest experience manager at a boutique hotel. <context> A reservation has been confirmed and the stay begins in 5 days. You need to send a warm, useful pre-arrival email that reduces front desk questions at check-in. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Guest name: [e.g. Sarah Chen] - Check-in date and time: [e.g. Aug 14, 3:00 PM] - Room type booked: [e.g. King Suite with balcony] - Trip occasion, if known: [e.g. anniversary] - Parking and check-in details: [e.g. free self-parking, lot B] - Local weather or events during the stay: [e.g. farmers market Saturday] </inputs> <task> Write a pre-arrival email that confirms the booking details, answers the 3 questions guests ask most (parking, check-in time, what to pack), and offers one relevant paid add-on tied to the trip occasion. </task> <constraints> - Keep it under 200 words. - Warm but not overfamiliar tone. - Offer only one add-on, do not stack multiple upsells. - Include a clear subject line. </constraints> <format> Return the subject line, then the full email body ready to paste into the property's email system. </format>

Drafts a pre-arrival email that answers common questions and offers one relevant upsell.

๐Ÿ’ก

Pro tip: Feed it your actual property FAQ so the answers match your real parking and check-in policy.

Post-Stay Thank-You and Review Request

2/30

You are a guest relations manager at a hotel. <context> A guest checked out yesterday. You want to thank them for a specific part of their stay and ask for a review without sounding pushy. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Guest name: [e.g. Marcus Lee] - Stay dates: [e.g. Aug 3 to Aug 6] - Specific highlight staff noticed: [e.g. requested extra pillows, celebrated a birthday] - Review platform and link: [e.g. Google, g.page/cedar-ridge-inn/review] - Loyalty program name, if any: [e.g. Cedar Rewards] </inputs> <task> Write a short thank-you email that references the specific highlight, then asks for a review on the named platform, mentioning the loyalty program only if one is given. </task> <constraints> - Keep it under 150 words. - Ask for the review only once, not twice in different words. - No guilt-tripping or exaggerated language. - Include one clear call-to-action button label. </constraints> <format> Return the subject line, the email body, and the CTA button label as a separate line. </format>

Drafts a personalized post-stay thank-you email with a single, clear review ask.

๐Ÿ’ก

Pro tip: Pull the highlight detail straight from the housekeeping or front desk notes for that guest so it reads as genuine, not templated.

Room Upgrade Upsell Email

3/30

You are a revenue and guest experience manager at a hotel. <context> A guest has booked a standard room and upgrade inventory is available before arrival. You want to offer the upgrade by email in a way that sells the benefit, not just the price. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Guest name: [e.g. Priya Nair] - Current room booked: [e.g. Standard Queen] - Upgrade room type and price difference: [e.g. King Suite with balcony, +$45/night] - Upgrade perks: [e.g. private balcony, mini fridge, better view] - Reply-by window: [e.g. within 48 hours] </inputs> <task> Write an upsell email that leads with the specific benefit of the upgrade (space, view, or occasion fit), states the price difference once clearly, and gives one simple way to accept. </task> <constraints> - Offer only the one upgrade given, no additional add-ons. - State the price difference exactly once. - No fake urgency, state the reply-by window honestly. - Keep it under 180 words. </constraints> <format> Return the subject line and the full email body. </format>

Drafts a benefit-led room upgrade offer email with a single clear price and reply window.

๐Ÿ’ก

Pro tip: Name the exact view or feature the guest gets (harbor view, corner room) instead of a generic 'nicer room' line, it converts better.

Group Booking Confirmation Packet

4/30

You are a group sales coordinator at a hotel. <context> A wedding block of 12 rooms has been reserved and the group organizer needs a single confirmation packet to share with their guests. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Group organizer name: [e.g. Jamie Torres] - Event name and type: [e.g. Torres-Kim Wedding] - Room block: [e.g. 8 King Rooms, 4 Double Queens] - Group rate and booking cutoff date: [e.g. $189/night, cutoff Sept 20] - Included amenities: [e.g. free shuttle to venue, group breakfast] - Property contact for the group: [e.g. Dana, [email protected]] </inputs> <task> Produce a confirmation packet with a booking summary, a room block table, the rate and cutoff date, included amenities, and next steps for individual guests to book their own room. </task> <constraints> - Present the room block as a table. - State the cutoff date prominently near the top. - Keep the tone factual and informational, no sales language. </constraints> <format> A structured document with clear section headers and one table, ready to export as a PDF for the organizer to forward. </format>

Builds a group room block confirmation packet the organizer can forward to their guests.

๐Ÿ’ก

Pro tip: Ask the organizer for their guests' typical booking window so you can set a cutoff date with enough buffer before the event.

In-Stay Complaint Recovery Email

5/30

You are a duty manager at a hotel. <context> A guest emailed mid-stay unhappy about a specific issue and needs a fast, concrete written response before they check out. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Guest name: [e.g. Alan Weiss] - Room number: [e.g. 214] - Issue described by the guest: [e.g. air conditioning not cooling the room] - Resolution being offered: [e.g. room move to 310, one night comped] - Manager name and direct contact: [e.g. Dana Reyes, [email protected]] </inputs> <task> Write an empathetic response that names the specific issue in the first two sentences, states the resolution clearly, and invites the guest to reply if it's still not resolved. </task> <constraints> - No generic corporate apology language. - State the resolution within the first two sentences. - Keep it under 130 words. - Sign with the manager's name and direct contact. </constraints> <format> Return the ready-to-send email body only. </format>

Drafts a fast, specific service recovery email that states the fix up front.

๐Ÿ’ก

Pro tip: Send this within the hour if possible, a same-day resolution offer lands far better than a next-day one.

Review and Reputation Management

5 prompts

Negative Review Response Set

6/30

You are a general manager at a hotel handling online reputation. <context> The property received a 2-star review citing slow check-in and a dirty bathroom. You need a public response and an internal note for the team. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Review platform and star rating: [e.g. Google, 2 stars] - Full review text: [paste the review] - What's been fixed or is being fixed: [e.g. added a mid-shift housekeeping inspection] - Manager name: [e.g. Dana Reyes] </inputs> <task> Write a public response that names the specific complaints, states what was done or will be done, and invites the guest to return. Also write a short internal note listing the operational fix needed. </task> <constraints> - No defensiveness and no blaming the guest. - Public reply under 120 words. - Keep the internal note in a clearly separate, labeled section. </constraints> <format> Two labeled sections: "Public Response" and "Internal Follow-Up Note". </format>

Drafts a non-defensive public reply to a negative review plus an internal fix note.

๐Ÿ’ก

Pro tip: Always name the specific complaint in your first sentence, generic 'we're sorry for your experience' replies read as insincere to future readers.

Five-Star Review Reply Bank

7/30

You are a guest relations manager at a hotel. <context> The property receives many 5-star reviews and wants varied replies so responses don't look copy-pasted across the listing. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Review excerpt 1: [paste] - Review excerpt 2: [paste] - Review excerpt 3: [paste] - Staff members named in the reviews, if any: [e.g. front desk agent Maria] </inputs> <task> Write one tailored reply per excerpt that references a specific detail from that review, plus one generic fallback reply for reviews with no specific detail to reference. </task> <constraints> - Each reply under 60 words. - Vary the sentence structure and opening line across all 4 replies. - Name any staff member mentioned in the review. </constraints> <format> A numbered list of 4 replies matching the 3 excerpts plus the fallback. </format>

Generates 4 distinct, non-repetitive replies to positive reviews.

๐Ÿ’ก

Pro tip: Rotate through this bank rather than reusing one reply verbatim, OTA algorithms and readers both notice repeated phrasing.

Post-Checkout Review Request Sequence

8/30

You are a marketing manager at a hotel. <context> You want a 2-touch sequence, email then SMS, sent after checkout to increase review volume without annoying guests. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Timing: [e.g. email on day 1, SMS on day 4 if no review yet] - Review platform link: [e.g. g.page/cedar-ridge-inn/review] - Guest first name field: [e.g. {{first_name}}] - Brand tone: [e.g. warm, concise] </inputs> <task> Write both messages in the sequence: the email sent on day 1 and the short SMS sent later, only intended for guests who haven't reviewed yet. </task> <constraints> - SMS under 300 characters. - Email under 100 words. - Do not repeat the same phrasing between the two messages. - Include only one review link per message. </constraints> <format> Two labeled messages: "Email (Day 1)" and "SMS (Day 4)". </format>

Writes a two-touch email plus SMS sequence to lift review response rates.

๐Ÿ’ก

Pro tip: Suppress the SMS automatically for anyone who already left a review after the email, most booking or CRM tools can filter on that.

Monthly Guest Sentiment Report

9/30

You are a general manager preparing an ownership report. <context> Ownership wants a one-page monthly summary of review trends across all platforms. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Month: [e.g. July 2026] - Total reviews received and average rating: [e.g. 34 reviews, 4.3 average] - Prior month's average rating: [e.g. 4.1] - 5 paraphrased review comments, mixed themes: [paste] </inputs> <task> Produce a one-page report covering the rating trend versus last month, the top 3 praised themes, the top 3 complaint themes, and 2 recommended operational actions. </task> <constraints> - Use only the numbers provided, do not invent statistics. - Keep recommendations specific and tied to the themes surfaced. </constraints> <format> A structured one-page report with clear headers, ready to paste into a slide or email to ownership. </format>

Turns raw review data into a one-page trend report with concrete recommendations.

๐Ÿ’ก

Pro tip: Track the same 3 to 5 theme categories every month so ownership can see trend lines, not just a fresh list of complaints each time.

OTA Listing Description Refresh

10/30

You are a revenue manager updating third-party listings. <context> The Booking.com and Expedia listing description is outdated and doesn't reflect current amenities or target the right guest type. </context> <inputs> - Property name and type: [e.g. Cedar Ridge Inn, boutique hotel] - Number of rooms: [e.g. 42] - Key amenities: [e.g. rooftop bar, free parking, pet-friendly, EV chargers] - Nearby landmarks: [e.g. 5 min walk to the river walk] - Target guest type: [e.g. couples and business travelers] - Current description, if available: [paste] </inputs> <task> Rewrite the OTA listing description to lead with the strongest amenity for the target guest type, then list the remaining amenities in scannable groups. </task> <constraints> - 150 to 200 words. - No unverifiable superlatives such as "best in town". - Only mention amenities actually listed in the inputs. </constraints> <format> A single ready-to-paste OTA description block. </format>

Rewrites a stale OTA listing to lead with the amenity that matters most to the target guest.

๐Ÿ’ก

Pro tip: Update this every time you add or remove an amenity, an out-of-date listing description drives disputes and refund requests.

Front Desk and Concierge SOPs

5 prompts

Front Desk Check-In Script

11/30

You are a front office manager training new hires. <context> New front desk hires need a consistent check-in script covering ID verification, payment, and room orientation. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Required check-in documents: [e.g. photo ID, credit card matching name on reservation] - Payment or deposit policy: [e.g. $50 incidental hold] - Standard amenities to mention: [e.g. wifi password, breakfast 7 to 10 AM, pool hours] - Upsell to offer at check-in, if any: [e.g. room upgrade if available] </inputs> <task> Write a step-by-step check-in script with the exact lines to say at each step, from greeting through handing over the room key. </task> <constraints> - Explicitly cover the ID and payment verification steps. - Include one natural upsell line, not a hard sell. - Keep the language conversational, not robotic. </constraints> <format> A numbered script with step labels: Greeting, Verification, Payment, Orientation, Close. </format>

Produces a step-by-step check-in script new front desk hires can follow word for word.

๐Ÿ’ก

Pro tip: Have a trainer roleplay this script with a new hire before their first solo shift, not just hand them the document to read.

Neighborhood Concierge Guide

12/30

You are a concierge at a hotel building a guest handout. <context> Guests ask the same 10 questions about the neighborhood. You want a one-page guide staff can hand out or send digitally. </context> <inputs> - Property name and neighborhood: [e.g. Cedar Ridge Inn, Riverside District] - 5 to 8 nearby restaurants or attractions with walk or drive time: [list] - Best coffee spot: [e.g. Blue Kettle Coffee, 3 min walk] - Nearest pharmacy: [e.g. Riverside Pharmacy, 5 min walk] - One insider tip only locals would know: [e.g. the farmers market moves indoors after October] </inputs> <task> Produce a one-page neighborhood guide organized by category: Eat, See and Do, Essentials, and one Insider Tip. </task> <constraints> - Use only the four category headers listed. - Keep each entry to a single line with the walk or drive time included. - No filler descriptions, just the practical facts. </constraints> <format> A one-page guide with clear section headers, ready to print or convert to a PDF. </format>

Builds a scannable one-page neighborhood guide for guests, organized by category.

๐Ÿ’ก

Pro tip: Refresh this guide seasonally, closures and hour changes make an outdated version worse than no guide at all.

VIP Guest Arrival SOP

13/30

You are a front office director documenting a service standard. <context> The property wants a documented SOP for handling top-tier loyalty guest arrivals consistently across every shift. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Loyalty tier defined as VIP: [e.g. Platinum members] - Standard VIP amenities: [e.g. room upgrade if available, welcome amenity, expedited check-in] - Who to notify on arrival: [e.g. front office manager and housekeeping supervisor] </inputs> <task> Write a step-by-step SOP covering pre-arrival flagging, the amenities to prepare, who greets the guest, and how to log the interaction afterward. </task> <constraints> - Present it as a numbered checklist usable by any shift. - Name the specific role responsible for each step. - Keep each step to a single line. </constraints> <format> A numbered SOP checklist with a role column. </format>

Documents a repeatable SOP for VIP guest arrivals with named role owners.

๐Ÿ’ก

Pro tip: Tie the pre-arrival flag directly to your PMS loyalty tier field so this triggers automatically instead of relying on someone remembering to check.

Guest Walk (Overbook) Script

14/30

You are a front office manager handling an overbooked night. <context> The property is overbooked tonight and must relocate ("walk") a guest to a partner hotel. Front desk needs a script and a way to log it. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Partner hotel name and distance: [e.g. Riverside Suites, 0.4 miles] - Compensation being offered: [e.g. paid taxi, rate difference covered, one night comped at return, loyalty points] - Guest's original room type: [e.g. King Suite] </inputs> <task> Write the exact script front desk should use to inform the guest, explain the compensation, and arrange transport, plus a short internal log to record the walk. </task> <constraints> - State the compensation before the guest has to ask for it. - Apologetic tone without over-apologizing. - Internal log limited to 5 fields. </constraints> <format> Two parts: "Guest Script" and "Internal Walk Log Template" (5 fields). </format>

Gives front desk a ready script and log for walking a guest during an overbook, with compensation stated upfront.

๐Ÿ’ก

Pro tip: Confirm the partner hotel has the room actually held before the guest leaves the lobby, not after.

Late Checkout and No-Show Script

15/30

You are a front office supervisor standardizing guest-facing policy language. <context> Front desk needs consistent language for handling late checkout requests and no-show reservations. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Standard checkout time: [e.g. 11:00 AM] - Late checkout fee or policy: [e.g. free until 1 PM if occupancy allows, $25 after] - No-show charge policy: [e.g. one night charged to the card on file] </inputs> <task> Write two short scripts: one for approving or declining a late checkout request depending on occupancy, and one for informing a guest of a no-show charge. </task> <constraints> - Give staff a clear if/then rule for approving late checkout based on occupancy. - No-show script must state the policy plainly and offer one way to dispute it. </constraints> <format> Two labeled scripts: "Late Checkout" and "No-Show Charge". </format>

Standardizes front desk language for two common friction moments: late checkout and no-shows.

๐Ÿ’ก

Pro tip: Post the if/then occupancy rule where front desk can see it during a shift, so the decision isn't left to individual judgment.

These prompts give you the what. Tutorials give you the why.

Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.

Try AI Academy Free

Staff Training and Operations

5 prompts

Housekeeping Inspection Checklist

16/30

You are a housekeeping director standardizing quality control. <context> You need a standardized room inspection checklist for housekeeping supervisors to sign off on before a room is marked ready. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Room type being inspected: [e.g. King Suite] - Number of checklist items wanted: [e.g. 15] - Property-specific standards: [e.g. towels folded in thirds, welcome amenity on the desk] </inputs> <task> Produce a room-by-room inspection checklist covering bathroom, bedroom, amenities, and safety items, with a pass/fail column. </task> <constraints> - Group items by room area. - Include a supervisor sign-off line at the bottom. - Keep each item a single checkable action. </constraints> <format> A checklist table with columns: Item, Area, Pass/Fail. </format>

Builds a standardized room inspection checklist grouped by area with a sign-off line.

๐Ÿ’ก

Pro tip: Cap it at 15 to 20 items, longer checklists get skimmed rather than actually checked room to room.

Front Desk Shift Handover Log

17/30

You are a front office manager ensuring shift continuity. <context> Front desk shifts need a consistent handover so the next shift knows about pending issues, VIP arrivals, and open guest requests. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Shift date, outgoing and incoming staff: [e.g. Aug 11, outgoing Maria, incoming Tom] - Open guest issues: [e.g. room 214 AC ticket open, follow up by 6 PM] - VIPs or groups arriving next shift: [e.g. Platinum member arriving 4 PM] - Maintenance or housekeeping flags: [e.g. elevator 2 out of service] </inputs> <task> Produce a filled-out sample shift handover log using the information given, followed by a reusable blank template. </task> <constraints> - Keep sections in a fixed order: Open Issues, Arrivals, Maintenance Flags, Notes. - Sample must use only the data given, no invented guest names. </constraints> <format> A filled sample log followed by a blank reusable template, both in table form. </format>

Creates a filled sample shift handover log plus a reusable blank template.

๐Ÿ’ก

Pro tip: Keep this log in a shared doc rather than paper, so the incoming shift can review it before they even clock in.

Front Desk Onboarding Guide

18/30

You are a front office trainer planning a new hire's first week. <context> A new front desk agent starts Monday and needs a first-week onboarding guide covering systems, policies, and a shadowing schedule. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - PMS or software used: [e.g. Cloudbeds] - Key policies to cover: [e.g. cancellation policy, ID and payment verification, pet policy] - Trainer name and shadowing length: [e.g. Dana Reyes, 3 days] </inputs> <task> Produce a day-by-day first-week onboarding plan covering systems training, policy review, and a shadowing schedule with the named trainer. </task> <constraints> - Structure by day, from Day 1 through the end of shadowing. - Name concrete tasks per day, not vague goals. - Include an end-of-week readiness checklist. </constraints> <format> A day-by-day onboarding plan table plus an end-of-week readiness checklist. </format>

Builds a day-by-day first-week onboarding plan with a readiness checklist.

๐Ÿ’ก

Pro tip: Have the trainee sign off on the readiness checklist themselves before their first solo shift, it surfaces gaps before they hit a live guest.

Service Recovery Roleplay Script

19/30

You are a training manager building a practice scenario. <context> You want a roleplay script trainers can use to practice service recovery with new staff, based on a common complaint scenario. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Complaint scenario: [e.g. guest complains about noise from the room next door] - Trainee's role being trained: [e.g. front desk agent] - Authorized resolution options: [e.g. room move, noise warning to the other room, small credit] </inputs> <task> Write a two-person roleplay script, guest and staff member, that walks through the complaint, the staff response, and the resolution, plus 3 debrief questions for the trainer. </task> <constraints> - The staff character may only offer resolutions from the authorized list. - Keep the roleplay under 300 words. - Debrief questions must be open-ended, not yes/no. </constraints> <format> A labeled roleplay script (Guest / Staff turns) followed by 3 debrief questions. </format>

Writes a two-person training roleplay plus open-ended debrief questions.

๐Ÿ’ก

Pro tip: Have trainees swap roles and run it twice, playing the guest side builds empathy that improves their real staff response.

Guest Emergency Procedure One-Pager

20/30

You are a hotel operations manager preparing a safety reference. <context> You need a one-page reference staff can keep at the front desk for common emergencies: medical, fire alarm, and severe weather. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Local emergency number: [e.g. 911] - Nearest hospital or urgent care: [e.g. Riverside General, 1.2 miles] - Fire alarm assembly point: [e.g. north parking lot] - Severe weather shelter location: [e.g. lower level conference room] - Manager on-call contact method: [e.g. call the on-call cell listed at the front desk] </inputs> <task> Produce a one-page reference sheet listing what to do first for each emergency type, who to call, and where to direct guests. </task> <constraints> - Organize by emergency type as separate short sections. - The first action listed must always be the immediate safety step. - Keep the language plain and direct. </constraints> <format> A one-page reference sheet with a section per emergency type. </format>

Builds a plain-language emergency reference sheet organized by scenario.

๐Ÿ’ก

Pro tip: Post this at every front desk terminal and review it in every new hire's first shift, not just during initial training.

Upsell and Revenue

5 prompts

Seasonal Package Description Set

21/30

You are a revenue manager building seasonal packages. <context> The property wants 3 seasonal packages described for the website and OTA channels. </context> <inputs> - Property name and season: [e.g. Cedar Ridge Inn, fall] - 3 package themes: [e.g. romance, family, wellness] - What's included in each: [e.g. romance: late checkout, bottle of wine, couples spa credit] - Price point for each: [e.g. romance $259/night] </inputs> <task> Write a short, sellable description for each of the 3 packages, naming the specific inclusions and the price. </task> <constraints> - Each description under 60 words. - Lead with the guest benefit, not the inclusion list. - State the price once per package. </constraints> <format> Three labeled package descriptions, one per theme. </format>

Writes benefit-led descriptions for 3 seasonal packages with prices stated once.

๐Ÿ’ก

Pro tip: Test one package at a time on the booking page so you can tell which theme actually drives conversions before building more.

Loyalty Tier Announcement Copy

22/30

You are a brand marketing manager launching a loyalty update. <context> The property or brand is launching or renaming a loyalty tier and needs announcement copy for email and in-stay signage. </context> <inputs> - Program name: [e.g. Cedar Rewards] - Tier name and benefits: [e.g. Platinum: free breakfast, late checkout, room upgrade when available] - Qualification threshold: [e.g. 10 nights or $2,000 spend per year] - Launch date: [e.g. Sept 1] </inputs> <task> Write an email announcement to current members and a short in-room signage version of the same announcement. </task> <constraints> - Email under 150 words. - Signage version under 40 words. - Both must state the qualification threshold plainly. </constraints> <format> Two labeled outputs: "Member Email" and "In-Room Signage Copy". </format>

Drafts a loyalty tier launch announcement in both email and in-room signage formats.

๐Ÿ’ก

Pro tip: Send the email to members close to qualifying first, with a note on exactly how many nights or how much spend they need, it drives faster tier upgrades.

Rate Change Rationale Memo

23/30

You are a revenue manager justifying a pricing decision. <context> You're raising rates for an upcoming high-demand weekend and need to justify it internally to the GM or ownership. </context> <inputs> - Property name and dates affected: [e.g. Cedar Ridge Inn, Sept 12-14] - Current rate and proposed new rate: [e.g. $189 to $229] - Demand driver: [e.g. citywide marathon, hotel already at 70% booked] - Comp set rates, if known: [e.g. nearby properties at $245-260] </inputs> <task> Write a short internal memo justifying the rate change using the demand data given, with a recommended date to review and reassess. </task> <constraints> - Use only the figures provided, do not invent comp set data. - Keep the memo under 200 words. - State the recommendation in the first line. </constraints> <format> A one-page internal memo with a clear recommendation line at the top. </format>

Writes an internal rate change justification memo grounded in the demand data given.

๐Ÿ’ก

Pro tip: Attach the actual comp set screenshot alongside this memo, a documented rate rationale protects you if ownership questions it later.

Amenity Upsell Script Bank

24/30

You are a front office manager building upsell scripts. <context> Front desk and housekeeping need short, natural upsell lines for paid amenities offered at check-in or during the stay. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Paid amenities with prices: [e.g. breakfast $18, parking $25/night, late checkout $25, spa credit $40] - Moment each is offered: [e.g. breakfast and parking at check-in, late checkout on the in-room card] </inputs> <task> Write one natural upsell line per amenity, tagged with the moment it should be used. </task> <constraints> - Each line under 25 words. - No pressure language. - State the price in every line. </constraints> <format> A table with columns: Amenity, Moment, Upsell Line. </format>

Builds a table of natural, low-pressure upsell lines tied to specific guest touchpoints.

๐Ÿ’ก

Pro tip: Have front desk practice these lines out loud, a script that reads well on paper can still sound stiff when spoken.

Direct Booking Incentive Email Set

25/30

You are a digital marketing manager reducing OTA dependency. <context> The property wants to win guests back from OTAs by incentivizing direct bookings for their next stay. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Incentive being offered: [e.g. 10% off, free breakfast, double loyalty points] - Audience: [e.g. past guests from the last 12 months] - Expiration window: [e.g. book by Sept 30 for stays through Dec 31] </inputs> <task> Write a 2-email series: the first announcing the incentive, the second a reminder shortly before it expires. </task> <constraints> - State the exact incentive and expiration date in both emails. - The reminder must reference the limited time honestly, without fake urgency. - Each email under 120 words. </constraints> <format> Two labeled emails: "Email 1: Announcement" and "Email 2: Reminder". </format>

Writes a two-email direct booking incentive series with a real expiration date.

๐Ÿ’ก

Pro tip: Track how many of these bookings actually skip the OTA next time, it tells you if the incentive size is worth the margin you're giving up.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Marketing and Local Visibility

5 prompts

Google Business Profile Update Pack

26/30

You are a local marketing coordinator for a hotel. <context> The property's Google Business Profile has outdated photos and no recent posts, which is hurting local search visibility against nearby competitors. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Updated amenities or recent renovation: [e.g. new rooftop bar opened in June] - Current hours: [e.g. front desk 24/7, bar 4-11 PM] - One seasonal note: [e.g. pool open through October] - GBP category: [e.g. Hotel] </inputs> <task> Write an updated business description, one weekly GBP post announcing the seasonal note, and one sample Q&A entry answering a common guest question. </task> <constraints> - Business description must stay under 750 characters. - No repeated keyword stuffing. - The post must include exactly one call to action. </constraints> <format> Three labeled blocks: "Business Description", "Weekly Post", and "Sample Q&A Entry". </format>

Refreshes a Google Business Profile description, weekly post, and a sample Q&A entry.

๐Ÿ’ก

Pro tip: Post to GBP at least weekly, listings with recent activity rank higher in local search than static, unchanged profiles.

Instagram Caption Set for Property Highlights

27/30

You are a social media coordinator for a hotel. <context> You're scheduling a week of Instagram posts and need 5 varied captions for 5 different property features already photographed. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - 5 features to caption: [e.g. rooftop bar at sunset, pool, room interior, breakfast spread, pet-friendly policy] - Brand voice: [e.g. warm, a little playful] - Hashtag set: [e.g. #CedarRidgeInn #BoutiqueHotel #CityName] </inputs> <task> Write one caption per feature, matched to the photo it's paired with, each ending with the given hashtag set. </task> <constraints> - Each caption 2 to 3 sentences. - No more than 8 hashtags per caption. - Vary the opening line across all 5, no repeated sentence structure. </constraints> <format> A numbered list of 5 captions, one per feature. </format>

Writes 5 distinct Instagram captions matched to specific property features and hashtags.

๐Ÿ’ก

Pro tip: Schedule these across the week rather than posting all 5 at once, spacing them out keeps engagement steadier.

Local Partnership Outreach Email

28/30

You are a general manager pitching a nearby business for cross-promotion. <context> The property wants to partner with a nearby business to send guests both ways and share marketing costs. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Partner business name and type: [e.g. Riverside Kayak Tours] - Proposed idea: [e.g. guest discount card for tours, joint Instagram giveaway] - Desired next step: [e.g. 15-minute call next week] - Sender name and title: [e.g. Dana Reyes, General Manager] </inputs> <task> Write a short outreach email proposing the specific partnership idea and asking for the named next step. </task> <constraints> - Under 150 words. - One specific ask only, not a vague "let's collaborate" close. - Reference the idea concretely, not just "cross-promotion". </constraints> <format> Subject line plus the full email body. </format>

Drafts a concrete cross-promotion pitch email with one clear ask and next step.

๐Ÿ’ก

Pro tip: Pitch a business whose guests overlap with yours but doesn't compete directly, like a nearby tour operator or spa rather than another hotel.

Seasonal Local Guide Blog Post

29/30

You are a content marketer for a hotel website. <context> You want a short blog post for the property website that helps with local search and gives arriving guests something genuinely useful to plan around. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - Season or month: [e.g. October] - City or neighborhood: [e.g. Riverside District] - 4 to 5 seasonal activities or events with dates: [list] - Target reader: [e.g. weekend visitors] </inputs> <task> Write a blog post with an intro, one short section per activity using only the activities and dates given, and a closing paragraph mentioning the property as a convenient home base. </task> <constraints> - 400 to 600 words. - Do not invent events or dates beyond what's given. - Mention the property by name only in the intro and closing, not in every section. </constraints> <format> A blog post with a title and a subheading per activity. </format>

Writes a seasonal local guide blog post built only from the real activities and dates provided.

๐Ÿ’ก

Pro tip: Link each activity mention to the venue's own website if you have it, outbound links to relevant local sites can help local search relevance too.

New Amenity Announcement Press Release

30/30

You are a marketing manager announcing a new amenity to local media. <context> The property just finished a renovation or added a new amenity and wants a short press release to send to local outlets. </context> <inputs> - Property name: [e.g. Cedar Ridge Inn] - New amenity or renovation: [e.g. new rooftop bar, The Overlook] - Opening date: [e.g. June 15] - Quote source, name and title: [e.g. Dana Reyes, General Manager] - Local media contact info: [e.g. [email protected]] </inputs> <task> Write a press release with a headline, a dateline, a body that includes one direct quote from the named source, and a short boilerplate paragraph about the property. </task> <constraints> - Under 300 words. - Use a standard AP-style dateline. - The quote must be attributed to the named person only. - No unverifiable superlative claims such as "the city's best rooftop bar". </constraints> <format> A press release with headline, dateline, body, boilerplate, and a media contact line. </format>

Drafts a local press release for a new amenity, complete with a quoted GM statement.

๐Ÿ’ก

Pro tip: Send it to local outlets a week before the opening date, not the day of, so a writer has time to plan a visit or feature.

Frequently Asked Questions

Copy the prompt into Claude, replace each bracketed placeholder with your property's real details (name, dates, guest info), and Claude returns a finished email, script, or document you can review before sending.
No, they work on Claude's free tier. A paid plan mainly helps if your front desk or marketing team is running many of these drafts every day and hits the free message limit.
Yes, add a line to the inputs describing your brand voice (formal, casual, playful) and Claude will match it. You can also paste in a past email as a style reference.
Yes, every prompt is written around single-property inputs like your property name and local details rather than chain-level systems, so an independent hotel or bed and breakfast can use them as-is.
No, Claude only drafts the text. You still send guest emails through your property management system or CRM and post review replies directly on the review platform.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

7-day free trial. Cancel anytime.