How Hair Salon Owners Use Claude Code for Booking Replies, Review Responses, and Style Captions

It’s 10 p.m. I just waved off the last client of the day and finally sat down. I open my phone and there it is: three new Google reviews, two appointment changes that came in through DMs, one Instagram message asking for style advice. And I still haven’t ordered tomorrow’s color.

The thing I hear over and over from salon owners is this: “I love the work behind the chair, but the writing around it eats my whole day.” You want to reply to that review, but starting from a blank box takes ten minutes every single time. The day a one-star lands, you can burn half an hour just trying to write something that doesn’t sound defensive. And the style captions end up sounding the same: “Soft, effortless finish” on repeat.

This post is about handing that pile of writing to Claude Code for a first pass, so it stops jamming up your night. The goal is simple: get that hour after you lock up back, and spend it with your family instead of your phone.

Key takeaways

• Three of a salon’s writing jobs (booking replies, review responses, and style captions) can be cut to less than half the time once Claude Code drafts them for you.
• Let the AI handle the drafting and the multiple options. You always decide the send button and the tone of any apology to an unhappy client.
• Never paste a client’s real name, phone number, or chart notes. Swap them for initials or placeholders before you hand anything to the AI.
• A review reply that took ten minutes drops to two or three. At 100 reviews a month, that’s roughly ten-plus hours saved.
• Below you’ll find copy-paste prompt templates and a check script that flags whether personal info is hiding in your text before you send it to the AI.

Who this is for, first

I’m writing for owners of salons with one to ten people, and for the stylist who’s also the manager. No dedicated admin person. Social media and the blog are “I have to do it myself” jobs. And you’ve never written a line of code. That’s the reader I have in mind.

Claude Code sounds like an engineering tool, but the core move is just “ask in plain English, get a draft in plain English.” You can start without writing any code at all. If touching a terminal makes you nervous, read Claude Code for non-engineers first, then come back here.

The writing workflow in a salon

Let’s map where the time actually goes. The writing side of getting and serving clients usually runs like this:

1. A booking comes in (phone, DM, a booking portal, Instagram).
2. You write the confirmation, the change, or the cancellation reply.
3. The client comes in, you do the work, they pay.
4. A few days later a review shows up (glowing or harsh) and you reply.
5. You post a photo of the result and write a style caption.
6. You send a rebook nudge or a come-back-soon message.

Steps 2, 4, and 5 are the “writing that never ends.” Each one only takes a few minutes, but they stack up. On a normal weekday that’s one to two hours; after a busy weekend it all hits at once.

The places people get stuck

Here are the snags I actually get asked about, honestly:

• The one-star reply freezes you. Write it hot and it backfires; write it too polite and other clients read it as “something went wrong at that place.” You lose half an hour over the dial.
• The tone is all over the map. Every stylist writes differently, so the salon’s personality never comes through.
• Style captions are one note. “Beautiful soft finish” every time, and it never turns into a request for that stylist by name.
• You put it off and it piles up. A review reply lands best within 48 hours, yet two weeks slip by before you notice.

What to hand the AI vs. what you decide yourself

This is the most important part, so here it is as a table. Settle one rule up front: the AI is the draft writer, but you carry the final responsibility.

Task	Hand to Claude Code	You always decide
Booking reply	Template draft, a couple of phrasing options	Whether the slot is actually open, the send button
Review reply (positive)	Thank-you draft, name-insertion option	Fact-check, anything misleading
Review reply (negative)	Apology + improvement copy in 3 tones	Whether to apologize, how much to concede, the final wording
Style caption	Several caption / pitch options	The actual result, any overstatement
Personal info	Don’t let it touch this	Anonymize before handing anything over

The negative review is the one place you keep the AI’s output as a rough draft only. An apology is a business decision. If the AI decides on its own to write “we’ll give you a full refund,” that’s an accident waiting to happen.

Use case 1: Drafting booking and inquiry replies

This is the move for the “Are you free Sunday afternoon?” and “How long for color plus a cut?” messages that land in your DMs, so you stop typing them from scratch every time.

Teach Claude Code your basics once (hours, standard service durations, cancellation policy), then just hand it the key facts and let it draft. Before you send, check the open slot with your own eyes. That alone turns one to two minutes per reply into a few seconds.

Here’s a copy-paste template:

You are the front desk for the hair salon "(salon name)". Write a reply using these rules.

# Salon facts
- Hours: Tue-Sun 10:00-20:00, closed Mondays
- Rough durations: cut 60 min / color + cut 150 min / keratin 180 min
- Cancellation: free up to the day before, 50% for same-day cancellations

# Tone
- Polite but not stiff. One emoji per message, max.
- Always end by suggesting two specific date/time options.

# Client's message
"I'd love to come in Sunday afternoon for color and a cut."

Following the facts above, give me one ready-to-send reply, plus one more
that's a bit more casual, so two options total.

The trick is asking for “two options.” With one, you’re still left tweaking it; with two, you can use one of them almost as-is.

Use case 2: Drafting review replies in 3 tones at once

Reviews come in volume and the negative ones wear you down. So attack this with “three tones generated at once.”

A glowing review gets a genuine thank-you; a so-so three-star gets a “we’ll do better”; a harsh one gets an apology, each in a different tone, and you pick. Picking is a two-to-three-minute job.

Here’s the template for a negative review. Always strip the client’s name before you hand it over.

I'm replying to a hair salon review. Follow this policy.

# Rules
- Open by thanking them for coming in.
- Don't deny the point raised. If it's true, own it and promise to improve.
- Do not promise refunds, discounts, or any money.
- Don't write anything that could identify the person.

# Review text (name removed)
"Client A: The cut was good, but I waited 30 minutes and the wait was long.
There wasn't much explanation either."

Give me three reply options in different tones:
1) Sincere apology
2) Specific improvement steps
3) Short and clean

Compare the three, pick the one that fits your salon’s vibe, and add the proper nouns back by hand. That turns “agonize for 30 minutes” into “choose from three drafts.” If you want finer control over the tone, advanced prompt engineering for Claude Code helps.

Use case 3: Style captions and social posts

This is how you stop your photo captions all sounding alike. Hand over just three things (who, what, how you changed it) and ask for several caption options.

Giving the AI a checklist of elements you want in the caption sharpens the result:

• Target (e.g., 30s, thick hair, wavy)
• The problem (frizz, takes forever to style in the morning)
• The service you did and the finish
• How easy it is to recreate at home
• A line inviting them in (request you by name, rebook)

The prompt looks like this:

I'm writing an Instagram caption. Give me 3 options using this info.

- Client profile: late 30s, thick hair, mornings take forever to style
- What we did: layered cut + a volume-reducing treatment
- The finish: falls into place with just a blow-dry at home
- Please end the post with "Book through the link in our bio"
- Add 5 hashtags aimed at salons in (city name)

Don't use hype words (always, guaranteed, the best).

Locking out hype words up front quietly pays off. From an advertising-standards angle, not overpromising is the safer move anyway.

What changes, before and after

Here are rough numbers. They’re estimates, but they help you decide.

Item	Before	After
Replying to one review	~10 min	~2-3 min
Stewing over one bad review	~30 min	~5 min (pick from 3)
One style caption	~8 min	~2 min
100 review replies a month	~16 hours	~4-5 hours

If you free up ten hours a month, that goes into prepping a new service or posting more often. “Writing gets faster” matters less than “what you do with the time you got back” and that’s the part that actually moves revenue.

Security and personal-info notes

Don’t skip this part. A salon is a business built on handling people’s personal information.

• Never paste real names, phone numbers, addresses, or booking numbers. Anonymize first: “Client A,” “Client B.”
• Don’t hand over chart notes like allergies, medical history, or treatment records. If a style question needs it, generalize to “wavy, thick hair” and nothing more.
• Before you publish a review reply, check that the AI didn’t invent a name or a date. AIs will sometimes fabricate “plausible-looking” proper nouns.
• Before you put personal info into any free tool, check it against your salon’s privacy policy. Stay within what you could comfortably explain to a client (“we use AI to help draft replies”).

Doing the anonymizing by hand every time means you’ll eventually slip. So I put together a script that machine-checks whether personal info is still sitting in your text before it goes to the AI.

Copy-paste and run: a PII check script

If you have Node.js, this runs. Before you paste a review or a message, it flags whether phone numbers, emails, or long ID-like number strings are still in there. If something’s flagged, you mask it by hand before handing it to the AI.

Save it as check-pii.mjs:

import { readFile } from "node:fs/promises";

// Paste the text you're about to send to the AI into input.txt
const text = await readFile(new URL("./input.txt", import.meta.url), "utf8");

// Patterns that tend to be personal info (phone, email, long digit runs)
const checks = [
  { name: "Phone number", re: /(\+?\d[\d\s().-]{7,}\d)/g },
  { name: "Email address", re: /[\w.+-]+@[\w-]+\.[\w.-]+/g },
  { name: "ID / booking-number-like digits", re: /\b\d{6,}\b/g },
];

let hit = false;
for (const c of checks) {
  const found = text.match(c.re);
  if (found) {
    hit = true;
    console.log(`[CHECK] ${c.name}: ${[...new Set(found)].join(", ")}`);
  }
}

if (!hit) {
  console.log("OK: no obvious personal-info strings found.");
} else {
  console.log("\nMask the strings above before sending to the AI.");
}

Running it is just this:

node check-pii.mjs

If you see OK, the text is in good shape to hand to the AI. If something’s flagged, swap that part for “Client A” or “(phone number)” before you go ahead. It’s not perfect detection, so always pair it with one final read-through of your own.

That “make the AI follow the salon’s rules every time” setup is more stable when you put the rules in a config file. I cover how in CLAUDE.md best practices.

FAQ

Q. Can I use this if I’m not good with computers? A. The first way you use it is just “ask in plain English, get a draft.” Code can wait. If the setup worries you, walk through the Claude Code getting started guide once.

Q. Can I send an AI-written review reply as-is? A. For a positive review, fix the proper nouns and it’s basically ready. For a negative one, a person always makes the final call. The scope of an apology is a business decision, not something to hand to the AI.

Q. Won’t the reply be worse if I don’t include the client’s name? A. It won’t. Hand the AI “Client A” to draft with, then swap in the real name right before you send. Masking the name doesn’t drop the quality.

Q. Can I match the writing to my salon’s personality? A. Yes. Show it two or three replies that went over well in the past and say “use this tone,” and it leans into your voice. For daily small wins, see Claude Code productivity tips.

Q. Can I start for free? A. You can test the drafting use cases plenty for free. Once you’re baking it into the actual workflow, it’s safer to set your operating rules first.

What I confirmed when I actually tried it

I sat down with a salon-owner friend and ran a week’s worth of review replies through this exact process. I wanted to confirm two things: does it actually save time, and does any personal info leak through.

We took 20 reviews, masked them all to “Client A,” “Client B,” ran them through check-pii.mjs, then sent them to the three-tone generation. The replies that had been averaging about ten minutes each dropped to the two-to-three minutes of choosing and lightly editing. The biggest win was the negative reviews: being able to decide “do we apologize, and how much do we own” while looking at three drafts killed the drain of hunting for words from scratch.

On the flip side, there was one case where the AI invented a visit date that wasn’t in the review. We caught it before publishing and deleted it. It confirmed, again, that the “the send button belongs to a human” line can’t be crossed.

If you want to try it on your own first, the fastest start is the free PDF and learning materials. If you want to align every stylist’s reply tone and tidy up the whole operating setup as a company, I take those consultations at training and consulting. For now, just take one review at your own salon, mask the names, and let it draft. That one step is plenty.

For the official setup and the latest specs, also check the official Anthropic Claude Code docs.