30 Claude Prompts for Salon and Spa Owners

You are a salon manager building the full printed and digital service menu. <context> Clients need a clean, organized service menu grouped by category with clear pricing, including price ranges where service length affects cost. </context> <inputs> - Service categories and items: [SERVICES, e.g. Hair: cut, color, blowout; Nails: mani, pedi, gel] - Pricing per item, including ranges: [PRICES, e.g. cut $65-85 by length] - Stylist tier pricing if applicable: [TIER PRICING, e.g. senior stylist +$15] - Add-on services: [ADD-ONS] </inputs> <task> Build a full service menu organized by category, each item with its price or range, tier pricing noted where relevant, and add-ons listed under the category they apply to. </task> <constraints> - Categories in a logical order (hair before nails before spa, or by your input order). - Price ranges must state the variable clearly (e.g. "by length" or "by stylist tier"), not just a dash. - Add-ons listed directly under their relevant category, not in one catch-all list. </constraints> <format> A structured menu document with category headers and a price line per item, ready to format for print or web. </format>

You are a salon events coordinator building a bridal party package offering. <context> Bridal parties book multiple people for one event and need a single package description covering the bride, bridesmaids, and any trial run policy. </context> <inputs> - Services included for bride vs bridesmaids: [SERVICES, e.g. bride: hair + makeup trial + day-of; bridesmaids: hair or makeup day-of] - Minimum party size for the package rate: [MIN SIZE] - Trial run policy and cost: [TRIAL POLICY] - Deposit and booking lead time required: [DEPOSIT / LEAD TIME] </inputs> <task> Write a bridal package description covering what's included for the bride vs the party, the trial policy, the deposit and lead time required, and one line on what happens if the party size drops below minimum. </task> <constraints> - Bride and bridesmaid inclusions must be clearly separated, not merged into one list. - State the deposit amount and lead time as hard numbers, not "in advance." - Under 200 words. </constraints> <format> A one-page package description with clear headers (Included, Trial Policy, Deposit & Booking, Party Size Terms). </format>

You are a spa marketing coordinator building a limited-time seasonal treatment package. <context> A seasonal package bundles 2-3 existing services at a slight discount to drive bookings during a specific window (e.g. winter, holidays, summer). </context> <inputs> - Season and window dates: [SEASON / DATES] - Services bundled and individual prices: [SERVICES / PRICES] - Bundle price: [BUNDLE PRICE] - Package name idea if any: [NAME OR NONE] </inputs> <task> Name the package if not given, write a short description explaining the bundle and the savings versus booking individually, and state the exact booking window. </task> <constraints> - Calculate and state the dollar savings versus individual pricing, show the math. - State the exact start and end date of the offer, not "this season." - Under 100 words. </constraints> <format> A short promotional package description with a package name, bundle contents, savings line, and booking window. </format>

You are a salon front desk trainer building a quick-reference add-on upsell menu for staff to use during checkout. <context> Front desk and stylists need a fast way to suggest relevant add-ons at checkout without sounding pushy or guessing what fits the client's service. </context> <inputs> - Base services offered: [BASE SERVICES, e.g. cut, color, mani, facial] - Add-ons available and price: [ADD-ONS / PRICES, e.g. deep conditioning $15, paraffin dip $10] - Which add-on pairs naturally with which base service: [PAIRINGS] </inputs> <task> Build a quick-reference table matching each base service to its best-fit add-on and price, plus a one-line suggested phrase staff can say at checkout for each pairing. </task> <constraints> - Each base service gets exactly one primary add-on suggestion, not a list of options to keep it fast to use. - Suggested phrases must sound like a genuine recommendation, not a sales script ("Would you like to add..." not "Don't miss out on..."). - Table must be scannable in under 10 seconds. </constraints> <format> A table (Base Service, Suggested Add-On, Price, Suggested Phrase). </format>

You are a salon revenue manager designing a recurring VIP membership program. <context> A monthly membership (flat fee for discounted or included services) creates predictable recurring revenue and locks in regular clients against competitor promotions. </context> <inputs> - Monthly fee options being considered: [FEE OPTIONS, e.g. $49, $89] - Services included or discounted per tier: [INCLUSIONS, e.g. one blowout/month + 15% off retail] - Target client segment: [SEGMENT, e.g. clients visiting 2+ times/month already] - Cancellation terms: [TERMS, e.g. cancel anytime, 30-day notice] </inputs> <task> Design 2 membership tiers with their monthly fee, inclusions, and estimated value if used fully, then write the client-facing description explaining why it's worth it for the target segment. </task> <constraints> - Calculate the retail value of what's included at each tier and compare it to the monthly fee, show the math. - Recommend the tier best suited to the stated target segment, with a one-line reason. - Client-facing description under 120 words. </constraints> <format> A tier comparison table (Tier, Fee, Inclusions, Retail Value If Used Fully) followed by the client-facing description. </format>

You are a salon retention marketer building a win-back sequence for clients who haven't booked in a while. <context> Clients past their normal rebooking cycle by a wide margin need a specific, low-pressure nudge before they've fully switched to another salon. </context> <inputs> - Normal cycle vs time since last visit: [CYCLE / GAP, e.g. usually every 6 weeks, gone 4 months] - Last service booked: [SERVICE] - Win-back offer: [OFFER, e.g. 20% off next service, no offer] - Offer expiration if applicable: [DATE] </inputs> <task> Write a 2-email win-back series (Day 1 and Day 10) referencing their last service and the time gap specifically, with the offer and deadline in the Day 10 email only. </task> <constraints> - Day 1 email has no offer, it's a genuine "we noticed" check-in referencing their last actual service. - Day 10 email includes the offer and states the expiration date explicitly. - Each email under 90 words. </constraints> <format> Two labeled emails: Day 1, Day 10. </format>

You are a salon marketing manager designing a client loyalty points program. <context> A points-per-dollar-spent program needs a redemption structure simple enough for front desk staff to explain in one sentence. </context> <inputs> - Average ticket size: [TICKET, e.g. $85] - Points earned per dollar: [RATE, e.g. 1 point per $1] - Redemption tiers (points needed for what reward): [REDEMPTION, e.g. 500 points = $25 off] - Point expiration if any: [EXPIRATION OR NONE] </inputs> <task> Design a points structure with 3 redemption tiers, calculate roughly how many visits at the average ticket it takes to hit each tier, and write the one-sentence explanation staff should give new clients. </task> <constraints> - Show the visit-count math for each tier based on the average ticket given. - Redemption tiers must increase in reward value proportionally to points needed, not flat. - Staff explanation sentence under 30 words. </constraints> <format> A tier table (Tier, Points Needed, Reward, Approx. Visits to Earn) followed by the one-sentence staff explanation. </format>

You are a salon growth coordinator writing referral program copy for existing clients. <context> Existing clients referring friends is the cheapest new-client channel a salon has, but only if the ask and reward are clear. </context> <inputs> - Referral reward for the client: [CLIENT REWARD, e.g. $20 credit] - Reward for the new friend: [FRIEND REWARD, e.g. $20 off first visit] - How referrals are tracked: [MECHANISM, e.g. referral code, front desk mention] - Where this will be shared: [CHANNELS, e.g. receipt, email, Instagram story] </inputs> <task> Write referral program copy for each channel listed, stating both rewards clearly and the tracking mechanism, keeping the ask simple. </task> <constraints> - State both the client's reward and the friend's reward in every version, not just one side. - Each channel version matched to that channel's typical length (receipt line very short, email longer). - One CTA per version. </constraints> <format> One labeled copy block per channel listed. </format>

You are a salon client relations coordinator running a birthday month promotion. <context> A birthday-month offer is a light-touch, high-goodwill way to bring clients in during their birthday month with a personal-feeling message. </context> <inputs> - Offer: [OFFER, e.g. free add-on service, 15% off] - Redemption window: [WINDOW, e.g. anytime during birthday month] - Client segment: [SEGMENT, e.g. all active clients with a birthday on file] - Booking link: [LINK] </inputs> <task> Write a birthday offer email and a shorter SMS version, both personal in tone, stating the offer and the redemption window clearly. </task> <constraints> - Message must feel personal ("Happy birthday month"), not like a mass promo, avoid generic sale language. - State the redemption window explicitly (the full month, not "soon"). - SMS under 200 characters. </constraints> <format> Two labeled blocks: Email, SMS. </format>

You are a salon client experience manager sending a review request after a completed appointment. <context> Asking for a review right after a good appointment gets a far higher response rate than a generic monthly blast to everyone. </context> <inputs> - Service completed and stylist: [SERVICE / STYLIST] - Review platform link: [PLATFORM, e.g. Google review link] - Timing after appointment: [TIMING, e.g. 2 hours later] - Any incentive for leaving a review: [INCENTIVE OR NONE] </inputs> <task> Write a short review request message referencing the specific service and stylist, with a direct link and a low-friction ask (one line, not a paragraph explaining why reviews matter). </task> <constraints> - Reference the actual service and stylist name, not generic "your visit." - Under 40 words. - If an incentive exists, state it must not be conditional on a positive review, only on leaving one, to stay compliant with platform policies. </constraints> <format> One text or email message, ready to send. </format>

You are a salon manager building the onboarding checklist for a newly hired stylist. <context> A new stylist needs a structured first two weeks covering licensing verification, booking system training, product knowledge, and their first solo client, so nothing gets missed. </context> <inputs> - Licensing/certification to verify: [LICENSE, e.g. state cosmetology license] - Systems they need trained on: [SYSTEMS, e.g. booking software, POS, retail inventory] - Shadowing period length: [LENGTH, e.g. 5 client appointments] - Who signs off on readiness: [APPROVER ROLE] </inputs> <task> Build a day-by-day checklist for the first two weeks covering license verification, systems training, shadowing, product knowledge review, and the first solo client with sign-off. </task> <constraints> - Group by Week 1 and Week 2, with specific days, not a flat list. - Every item needs an owner (new stylist, manager, or approver). - End with an explicit readiness sign-off step, not an implied one. </constraints> <format> A checklist organized by Week 1 / Week 2, each item as a checkbox line with an owner tag. </format>

You are a salon health and safety manager writing the sanitation SOP for tools, stations, and treatment rooms. <context> Sanitation lapses risk client health, board inspections, and reputation. A clear written SOP means every staff member follows the same standard, not just what they were shown once. </context> <inputs> - Tools and equipment used: [TOOLS, e.g. shears, combs, nail files, wax pots] - Sanitation products approved for use: [PRODUCTS] - Local board requirements if known: [REQUIREMENTS] - Frequency required (between clients, daily, weekly): [FREQUENCY] </inputs> <task> Write a sanitation SOP broken into between-client tasks, end-of-day tasks, and weekly deep-clean tasks, each listing the specific tool or surface, the product to use, and the required frequency. </task> <constraints> - Every task must name the specific tool/surface and product, not "sanitize equipment." - Between-client tasks must be short enough to complete within a typical service changeover time. - If local board requirements are given, flag which tasks satisfy them directly. </constraints> <format> Three labeled sections: Between-Client Tasks, End-of-Day Tasks, Weekly Deep-Clean Tasks, each as a checklist. </format>

You are a senior colorist training stylists on how to run a color consultation before any color service. <context> A rushed or incomplete color consultation is the top cause of color service complaints and redo requests. A structured script covers the questions that prevent that. </context> <inputs> - Color services offered: [SERVICES, e.g. full color, balayage, highlights, corrective color] - Patch test policy: [PATCH TEST POLICY] - Questions currently asked, if any: [CURRENT QUESTIONS OR NONE] - Consultation time allotted: [TIME, e.g. 10 minutes] </inputs> <task> Write a consultation script with questions covering hair history (previous color, chemical treatments), desired result with a reference photo ask, maintenance expectations, and the patch test requirement, fitting within the time allotted. </task> <constraints> - Must include a question about previous chemical treatments explicitly, this is the most commonly skipped question that causes damage. - Patch test requirement stated as a required step, not optional, if policy requires it. - Script must fit realistically within the stated time allotment. </constraints> <format> A numbered consultation script with the question and the reason for asking noted briefly next to each. </format>

You are a salon manager writing the standard operating procedure for front desk opening and closing shifts. <context> Front desk staff turnover is common. A written SOP means a new hire can run a shift correctly on day one without shadowing for a week. </context> <inputs> - Opening tasks: [OPENING TASKS, e.g. unlock, lights, cash drawer, check day's schedule] - Closing tasks: [CLOSING TASKS, e.g. reconcile register, restock stations, confirm next-day schedule] - Common client requests and how to handle them: [REQUESTS, e.g. reschedule, product return, price question] - Manager contact for issues: [CONTACT] </inputs> <task> Write an opening checklist, a closing checklist, and a quick-reference table for the 4-5 most common client requests with a one-line "what to say / what to do" for each. </task> <constraints> - Opening and closing checklists in strict task order, not grouped by category. - Each common request gets a one-line pair, not a paragraph. - Include when to escalate to the manager contact versus handle at the desk. </constraints> <format> Three labeled sections: Opening Checklist, Closing Checklist, Common Requests table. </format>

You are a salon manager building a quarterly performance review template for stylists and support staff. <context> Reviews need to cover role-specific metrics (rebooking rate for stylists, product sales for retail-focused staff) alongside softer feedback, in a format that's consistent across the team. </context> <inputs> - Role being reviewed: [ROLE, e.g. stylist, esthetician, front desk] - Trackable metrics for that role: [METRICS, e.g. rebooking rate, retail sales, client retention] - Review period: [PERIOD] - Rating scale used: [SCALE, e.g. 1-5] </inputs> <task> Build a review template with a metrics section using the given scale, a strengths section, a growth-areas section, and a goals-for-next-quarter section, plus 3 sample manager comments showing how to fill in the growth-areas section constructively. </task> <constraints> - Metrics section must use the exact metrics listed, not generic ones. - Sample comments must be specific and behavioral ("rebooking rate at 58%, target 70%"), not vague. - Goals section requires exactly 2-3 goals, not an open list. </constraints> <format> A fillable template with labeled sections plus 3 sample comments below it. </format>

You are a social media manager for a salon building a month of content. <context> The salon needs a content calendar mixing before/after transformations, service education, stylist spotlights, and promotions across the platforms it actually uses. </context> <inputs> - Platforms used: [PLATFORMS, e.g. Instagram, TikTok] - Posting frequency: [FREQUENCY, e.g. 5x/week] - Content pillars: [PILLARS, e.g. transformations, service education, stylist spotlights, promotions] - Any upcoming promo or event: [PROMO/EVENT] </inputs> <task> Build a 30-day content calendar assigning a pillar and post idea to each scheduled day, and write full caption copy for 5 of those posts (one per pillar plus the promo). </task> <constraints> - No two consecutive scheduled posts use the same pillar. - Calendar dates must match the stated posting frequency exactly, not more or fewer posts. - Captions under 60 words each, one clear CTA per caption. </constraints> <format> A calendar table (Date, Pillar, Post Idea) followed by 5 full captions labeled by date. </format>

You are a salon marketing copywriter writing a local SEO landing page for a specific service. <context> The page targets people in a specific neighborhood searching for a service (e.g. "balayage near me") and needs to convert a visit into a booking. </context> <inputs> - Salon name and neighborhood: [SALON NAME / AREA] - Featured service: [SERVICE, e.g. balayage] - Top 3 differentiators: [DIFFERENTIATORS, e.g. certified colorists, no-ammonia options, walk-ins welcome] - Social proof available: [PROOF, e.g. 4.9 stars, 800+ reviews] </inputs> <task> Write a landing page with a headline, subheadline, 3 differentiator sections with one line each, a social proof line, and a single CTA repeated at top and bottom. </task> <constraints> - Headline under 12 words, must reference both the service and the neighborhood. - Each differentiator section under 20 words. - Same CTA wording used both times. </constraints> <format> A structured landing page draft with clear section headers (Headline, Subheadline, Differentiators, Social Proof, CTA). </format>

You are a salon marketing manager launching a seasonal promotion. <context> A seasonal promotion (holiday glow-up, wedding season, back-to-school) needs a full campaign plan across channels, not just one social post. </context> <inputs> - Season/occasion and window dates: [OCCASION / DATES] - Promotion offer: [OFFER, e.g. 20% off color services] - Channels available: [CHANNELS, e.g. email, Instagram, in-salon signage] - Target client segment: [SEGMENT, e.g. color clients, all clients] </inputs> <task> Build a campaign plan with a send/post calendar across the listed channels (announce, midpoint push, last chance) and one draft asset per channel. </task> <constraints> - Timeline must include a midpoint push, not just announce and last chance. - Each channel's draft must be matched to that channel's format and length. - State the offer's exact end date in every asset. </constraints> <format> A calendar table (Date, Channel, Message Angle) followed by one drafted asset per channel. </format>

You are a salon marketing coordinator pitching a local micro-influencer on a trade or paid partnership. <context> A cold or warm outreach email proposing a free or discounted service in exchange for content, targeted at a local influencer whose audience matches the salon's clientele. </context> <inputs> - Influencer name/handle and follower range: [INFLUENCER / FOLLOWERS] - Proposed service offered: [SERVICE] - Deliverables requested: [DELIVERABLES, e.g. 1 Reel, 2 Stories tagging the salon] - Any additional compensation beyond the service: [COMPENSATION OR NONE] </inputs> <task> Write a partnership outreach email proposing the trade, stating exactly what's offered and what's requested in return, with a clear next step. </task> <constraints> - State the service value and the requested deliverables as a clear, even trade, not vague "exposure for services." - Under 120 words. - One next step only (reply to schedule, not multiple options). </constraints> <format> One outreach email, ready to send. </format>

You are a salon marketing manager writing the monthly client email newsletter. <context> The monthly newsletter keeps the salon top of mind between visits with a mix of a featured service or product, a promotion, and a light personal touch, without feeling like a sales blast. </context> <inputs> - Featured service or product this month: [FEATURE] - Current promotion if any: [PROMO OR NONE] - Any salon news (new stylist, hours change, event): [NEWS OR NONE] - Booking link: [LINK] </inputs> <task> Write a monthly newsletter with a short opening line, a featured service/product section, the promotion if one exists, any salon news, and a single closing CTA. </task> <constraints> - Under 200 words total. - Only one CTA in the whole newsletter, placed at the end. - If no promo or news exists, skip that section rather than filling it with filler content. </constraints> <format> One newsletter draft with section headers, ready to paste into an email tool. </format>

You are a salon owner responding publicly to online reviews. <context> Public review responses are read by future clients, not just the reviewer. Positive reviews deserve specific thanks, negative reviews need a calm, non-defensive response that shows the salon takes feedback seriously. </context> <inputs> - Positive review text: [POSITIVE REVIEW] - Negative review text: [NEGATIVE REVIEW] - Salon name: [SALON NAME] - Offer to take the negative conversation offline: [CONTACT METHOD, e.g. call the salon directly] </inputs> <task> Write a response to the positive review referencing something specific from it, and a response to the negative review that acknowledges the concern, avoids being defensive, and invites them to continue the conversation privately. </task> <constraints> - Positive response must reference a specific detail from the review, not a generic "thank you." - Negative response must not argue with or dispute the reviewer's account, even if it seems unfair. - Both responses under 60 words. </constraints> <format> Two labeled responses: Positive Review Response, Negative Review Response. </format>

You are a salon marketing manager designing a systematic review request campaign. <context> Instead of asking for reviews inconsistently, the salon wants a repeatable campaign triggered after every appointment, with a light follow-up if the first ask goes unanswered. </context> <inputs> - Review platform: [PLATFORM, e.g. Google] - Timing of first ask after appointment: [TIMING, e.g. 3 hours] - Follow-up timing if no response: [FOLLOW-UP TIMING, e.g. 5 days later] - Client segment to exclude, if any: [EXCLUSIONS, e.g. clients who complained recently] </inputs> <task> Build the campaign logic (when the first ask fires, when the follow-up fires, who gets excluded) and write both the first ask and the follow-up message. </task> <constraints> - Follow-up message must not repeat the first message verbatim, vary the wording. - Exclusion rule must be stated as a clear condition, not a vague "use judgment." - Each message under 35 words. </constraints> <format> A short campaign logic summary (3 lines) followed by two labeled messages: First Ask, Follow-Up. </format>

You are a salon marketing coordinator collecting written testimonials for the website and social media, separate from public platform reviews. <context> A testimonial for marketing use needs a more detailed story than a quick star review, so the request should prompt for specifics rather than a one-line quote. </context> <inputs> - Client to approach and service they had: [CLIENT / SERVICE] - Where the testimonial will be used: [USE, e.g. website homepage, before/after gallery] - Any incentive offered: [INCENTIVE OR NONE] - Consent/usage permission needed: [PERMISSION NOTE] </inputs> <task> Write a request message asking for a more detailed testimonial with 2-3 specific prompting questions (what was the experience like, what result stood out, would they recommend and to whom), and a line requesting permission to use their name and photo. </task> <constraints> - Prompting questions must ask for specifics, not "what did you think." - Must explicitly request permission to use name/photo, not assume it. - Under 90 words. </constraints> <format> One request message, ready to send. </format>

You are a salon manager handling a direct client complaint about a service. <context> A client complained about a service result (color, cut, or treatment) and the response needs to acknowledge the issue, offer a concrete resolution, and prevent it from escalating to a public review. </context> <inputs> - Complaint details: [COMPLAINT] - Service and stylist involved: [SERVICE / STYLIST] - Resolution options available: [OPTIONS, e.g. free correction service, partial refund] - Salon's general policy on redos: [POLICY] </inputs> <task> Write a response (phone script or message) that acknowledges the specific issue described, offers one clear resolution option first rather than a menu, and states next steps to schedule the fix. </task> <constraints> - Acknowledge the specific complaint detail given, not a generic "sorry you're not happy." - Lead with one resolution offer, only mention alternatives if they ask. - Under 100 words. </constraints> <format> One response script, labeled for phone or message use. </format>

You are a salon marketing consultant auditing a salon's current online reputation. <context> Before running any review campaign, the salon needs a clear picture of where it stands today across the platforms clients actually check. </context> <inputs> - Platforms to check: [PLATFORMS, e.g. Google, Yelp, Instagram] - Current review counts and average ratings per platform: [DATA, e.g. Google 4.6 (210), Yelp 4.1 (45)] - Any recurring complaint theme noticed: [THEME OR NONE] - Competitor's rating for comparison, if known: [COMPETITOR DATA] </inputs> <task> Build an audit summary comparing rating and volume across platforms, flag the weakest platform and why it matters, note the recurring complaint theme if one exists, and give one prioritized next action. </task> <constraints> - Comparison must be based on the actual numbers given, not general platform reputation. - Weakest platform flagged must be identified by the actual lower number, not assumed. - Exactly one next action recommended, not a list of five. </constraints> <format> A comparison table (Platform, Rating, Review Count) followed by a 3-sentence summary and one recommended next action. </format>