When My Wife Messaged a Salon... For Me (And Nobody Thought to Ask)

The Text That Started It All

Last week, my wife did me a favor. I was busy with work, so she offered to message a new salon we'd been meaning to try and see about a haircut for me.

Simple enough, right?

She pulled up their WhatsApp and typed:

"Hi! I'd like to ask about booking a haircut for Saturday afternoon if possible."

The reply came quickly:

"Hi! Sure, we have 2 PM or 4 PM available. Which works better for you?"

My wife replied:

"4 PM would be great!"

And then:

"Perfect! We've got you down for 4 PM Saturday. See you then! What style are you thinking, just a trim or something different?"

She didn't think much of it. She confirmed and moved on with her day.

---

Saturday Arrives

I walked into the salon at 3:55 PM, ready for my haircut.

The first thing I noticed: the waiting area was packed. Seven people sitting there, scrolling their phones, clearly waiting.

"Hi, I have a 4 PM appointment."

The receptionist checked the system. "Under what name?"

"Should be under my wife's name, she booked it for me."

Pause. Scroll. Confused look.

"Ah… we have her down for a women's cut and style. Were you… also coming in today?"

I explained the situation. She understood. But then came the real problem:

"I'm so sorry about the confusion. We can try to fit you in, but…" she gestured at the waiting area, "…we have quite a few walk-ins ahead of you. It might be a 2-3 hour wait."

I looked at the seven people. I looked at my watch. I thought about the things I'd planned to do that afternoon.

"You know what? I'll come back another time."

I walked out.

---

What Went Wrong?

Two things.

Problem #1: The Assumption

The person replying to WhatsApp just... assumed.

• A woman messaged about a haircut.
• They assumed it was for her.
• They asked about styles, through the lens of that assumption.
• My wife, not realizing the confusion, just confirmed.

Problem #2: There Was No Structure

The person on the other end of the chat never asked the simplest possible question: "Who's the haircut for, and what kind of service are you looking for?"

They skipped intake entirely, jumped to "here's a time slot," and booked a service that didn't match the customer. There was nothing in their process that required the basic facts before a slot got committed.

---

The Problem With Human Assumptions

Humans are efficient communicators. We fill in blanks. We read between the lines. We make assumptions to save time.

Usually, that's great.

But in inbound conversations, those assumptions can backfire:

• A wife messages → Must be for her
• "I need to ask about pricing" → Must be a budget shopper
• A man asks about a service typically used by women → Must be a gift
• Someone asks about services for kids → Must be a parent

We don't even realize we're doing it. It's automatic. It's human.

And it leads to wrong-fit bookings, awkward corrections, and customers who don't bother coming back.

---

What a Structured Intake Would Have Caught

Here's the thing: you don't fix this with a smarter human. You fix it with a structure that can't skip the basics. And that's something you can build yourself in an afternoon.

If this salon had built their intake on a messaging API like Wabery, the first reply wouldn't have been an improvised guess. It would have been a WhatsApp Flow, a native in-chat form, that asks the few questions that actually matter before any slot gets offered.

A Flow doesn't assume. It collects.

Here's how that same conversation might have gone:

Customer: "Hi! I'd like to ask about booking a haircut for Saturday afternoon if possible."

Salon (sends a WhatsApp Flow): "Happy to help! A couple of quick questions so we get this right:

1. Who's the haircut for?
2. What kind of service (men's cut, women's cut, kids', something else)?
3. What name should we put the appointment under?"

Customer (fills in the form): For my husband Andrew · Men's cut · Andrew

Salon: "Perfect. For a men's cut on Saturday afternoon, we have 2:00 PM with Alex or 4:00 PM with Jordan. Which works better for Andrew?"

Customer: "4 PM with Jordan."

Salon: "Great. We'll confirm 4 PM Saturday with Jordan for Andrew. What's the best number to reach you on in case we need to get in touch?"

The Flow result arrives at the salon's webhook as clean JSON: { for: "husband Andrew", service: "men's cut", name: "Andrew" }. No parsing, no guessing, no assumptions baked into a hurried reply.

---

The Difference: Structure Over Assumption

Notice what happened:

1. Service and customer captured first, because the form required it, not because someone remembered to ask.
2. Natural, friendly tone, a short in-chat form, not a clunky web link.
3. Name and phone captured explicitly, no assuming who's messaging is who's coming in.

The human at that salon heard "haircut" and filled in the blanks.

A structured intake you build yourself collects a few facts first, then lets the customer fill the blanks in themselves. The result is clean data you can hand straight to your booking system or to the human who actually confirms the slot.

Same conversation length. Completely different outcome.

---

It's Not Just About Speed

When people talk about adding AI or automation to a business, they usually focus on:

• "It saves time!"
• "It works 24/7!"
• "It handles multiple conversations at once!"

All true. But here's what gets overlooked:

A well-built intake doesn't skip steps to seem efficient.

Humans do. We think we're being helpful by not asking "obvious" questions. We think customers will appreciate the quick reply.

But customers appreciate getting what they actually wanted even more. And the nice thing is, you control exactly which questions are required, because you built the form.

---

The Real Benefit: Clarity

My wife wasn't angry at the salon. But she was mildly embarrassed when I came home and told her what happened.

"I literally said it was for a haircut. Why would they assume it was for me?"

"Because you're the one who messaged."

"But I didn't say it was for me!"

"You also didn't say it wasn't."

That's the gap. Humans hear what's said and fill in the rest. A structured intake collects what's said and asks about the rest, every time, because you wired it to.

---

When Assumptions Add Up

One wrong appointment is funny. A pattern of wrong-fit bookings is a problem.

Think about:

• Couples where one partner handles logistics for both
• Parents reaching out on behalf of their kids
• Assistants contacting businesses for executives
• Friends coordinating for each other

Every one of these is an assumption trap. And every one of them is closed by a form that asks one question: who is this for?

---

The Takeaway

I didn't get my haircut that day. And I'm probably not going back to that salon.

But I'm now hyper-aware of how often businesses make assumptions in the very first message of a conversation. And how a simple, structured intake, something you can build yourself in an afternoon, would prevent all of it.

If you're running a business and handling inbound messages yourself, consider:

• Do you ask who the service is for, upfront?
• Do you capture the 2-3 facts that would let you match a customer to the right offering?
• Or do you skip ahead to "here's a time slot" because it feels faster?
• How many customers have quietly walked away because you filled in a blank wrong?

The fix isn't a packaged product that "does the booking for you." It's a few primitives, a WhatsApp Flow for intake and a webhook that drops the result into your system, that you wire up once and never have to think about again.

---

Why This Matters More Than You Think

Customers who get the wrong experience don't always complain.

Some just... don't come back.

They chalk it up to "that place wasn't paying attention", even if the real issue was an unspoken assumption on both sides.

You might never know you lost them.

---

Final Thought

The best customer experience isn't the fastest one. It's the one where:

1. The customer feels heard
2. They get exactly what they asked for
3. They don't have to correct anyone along the way

Sometimes that means asking one more question before confirming anything.

Sometimes that means building a structured first step yourself, not because it's cheaper, but because it's clearer, and because you decide exactly what it asks.

Either way: stop assuming. Start collecting. Get the facts before you commit.

Your customers (and their spouses) will thank you.

---

Curious how this works in practice? Build it free on Wabery: wire up a WhatsApp Flow for intake and a webhook for the results, no assumptions, no guessing.