Med Spa Lead Qualification: 12 Questions Before Booking

Med spa lead qualification should not feel like an interrogation.

The goal is not to make a website visitor prove they are worth your time. The goal is to ask just enough to route them correctly: booking link, consult request, call, staff follow-up, or a safer human review path.

That matters because med spa visitors often arrive with mixed intent. One person is ready to book Botox this week. Another is comparing lip filler prices. Another wants to know whether laser hair removal is appropriate for their skin and hair. Another is nervous and wants a human before sharing details.

A good Website Support Agent should separate those paths without pretending to be the provider.

Use this 12-question lead-readiness scorecard as a starting point for your website chat, consult request form, front-desk scripts, or AI Support Agent training. Think of these as pre-consultation questions for med spas, not a replacement for formal intake.

Quick answer

Med spa lead qualification works best when the first few questions are lightweight:

1. What treatment or concern brought you here?
2. Are you a new or returning client?
3. Are you looking to book, ask a question, or compare options?
4. When are you hoping to come in?
5. What is the best way for the team to follow up?

Those questions help route the visitor without asking for sensitive medical detail in casual website chat.

The deeper questions belong in a consultation, secure intake form, or provider review. The website layer should not diagnose, decide candidacy, estimate dose, approve treatment, or collect more health information than the clinic has intentionally designed for that channel.

For med spas, the strongest qualification system is not "book everyone." It is "route each person to the next step that fits their readiness."

The med spa lead-readiness matrix

Start by putting each website inquiry into one of three groups.

This matrix keeps the AI from treating every inquiry the same.

A ready lead needs a clear next step. A maybe lead needs enough information to feel safe moving forward. A staff-review lead needs the AI to stop before it gives a personal answer.

That is the difference between lead qualification and pressure. Med spa lead capture works better when the visitor feels guided, not screened out.

The 12 questions to ask before booking

These questions are designed for the first website conversation. They are not a full medical intake.

1. What treatment or concern brought you here?

This is the anchor question.

Good examples:

• "Are you interested in Botox, filler, laser, skin treatments, body contouring, or something else?"
• "What would you like help with today?"
• "Are you looking for a specific treatment or still comparing options?"

Why it helps: the answer tells the agent which service page, FAQ, pricing language, or consult path to use.

2. Are you a new or returning client?

New clients often need a different route than returning clients.

Good examples:

• "Is this your first visit with us?"
• "Have you had this treatment with our clinic before?"

Why it helps: new clients may need consultation first. Returning clients may already know the service and only need booking, policy, or staff follow-up.

3. Are you trying to book, ask a question, or compare options?

This prevents the AI from pushing booking too early.

Good examples:

• "Are you ready to request a consult, or are you still deciding?"
• "Would you like the booking link, or would you rather ask the team a question first?"

Why it helps: a visitor who says "just comparing" should not get the same push as a visitor who says "I want to book."

4. When are you hoping to come in?

Timing reveals readiness.

Good examples:

• "Are you hoping to come in this week, this month, before an event, or just researching?"
• "Do you have a date you are planning around?"

Why it helps: event timing, urgency, and appointment windows affect the route. The AI should not promise live availability unless the booking system is actually integrated.

5. Which result or outcome are you hoping for?

This is useful, but it needs a boundary.

Good examples:

• "What goal are you hoping to discuss with the provider?"
• "Are you looking for subtle maintenance, first-time guidance, or a specific concern?"

Why it helps: the clinic can understand intent without the AI deciding which treatment is right.

Bad version:

Tell me your facial anatomy and I will recommend the best filler plan.

Better version:

The team can review your goals during consultation. I can help route you to the right consult request.

6. Do you want pricing guidance before booking?

Price questions are high-intent, but they need approved language.

Good examples:

• "Would you like general pricing guidance before booking a consult?"
• "Do you want to see how this clinic explains starting prices, ranges, or consult-based pricing?"

Why it helps: a visitor asking about cost may still be a good lead. Do not dismiss them as price shopping. Use the med spa pricing questions decision tree to answer without inventing a quote.

7. Which location, provider, or appointment type do you prefer?

Only ask this if the clinic actually uses it.

Good examples:

• "Do you have a preferred location?"
• "Are you trying to book a consultation or a specific service?"

Why it helps: routing improves when the visitor names the right location, provider, or appointment category.

8. What is the best way for the team to follow up?

This turns a vague inquiry into a usable lead.

Good examples:

• "What is the best phone or email for the team to use?"
• "Do you prefer a call, text, or email follow-up?"

Why it helps: if the AI hits a boundary, staff still receives a contactable lead with context.

9. Have you already seen our service or pricing page?

This prevents repeated information.

Good examples:

• "Have you already looked at the service page, or would you like me to send it?"
• "Would seeing the pricing page help before you request a consult?"

Why it helps: some visitors only need the right page. Others need a human. The AI should adapt.

10. Is there anything the team should know before replying?

Keep this broad.

Good examples:

• "Anything you want the team to know before they follow up?"
• "Is there a specific question you want the provider or coordinator to review?"

Why it helps: the visitor can volunteer context without the AI asking for sensitive details.

11. Are you asking for general information or a personal recommendation?

This is a boundary-setting question.

Good examples:

• "I can share general clinic information. If you need a personal recommendation, the team should review that directly."
• "Are you looking for general treatment information, or do you want the team to help decide what fits?"

Why it helps: the AI can answer general info, but personal recommendation belongs to the clinic.

12. Would you like the booking link or a staff follow-up?

End with a choice.

Good examples:

• "Would you like the consultation booking link, or should I collect your question for staff follow-up?"
• "I can send you to booking now or help you leave a message for the team."

Why it helps: this moves the conversation from open-ended chat to a concrete next step.

What not to ask in open website chat

The Website Support Agent should not act like a full intake form.

Avoid asking for:

• Detailed medical history
• Medication lists
• Pregnancy or nursing status
• Photos of sensitive areas
• Diagnosis details
• Prior complications in detail
• Emergency symptoms
• Insurance, payment, or identity details beyond the clinic's approved process

There may be clinics with secure, formal intake workflows for some of this information. That is a different product surface than casual website chat and should be reviewed through the clinic's approved privacy and compliance process.

The safer rule is: website chat can collect routing context; formal intake collects clinical context.

Routing rules for ready, maybe, and staff-review leads

Once the AI has enough context, it should route instead of endlessly chatting.

If the clinic is comparing phone automation with website chat, read AI Receptionist vs Website Chatbot for Med Spas. For this website-first workflow, keep visitor qualification on the website and route anything that needs staff judgment to the clinic's existing call, booking, or contact path.

Example qualification flows

Botox consult request

Visitor: Do I need a consult before Botox?

Website Support Agent: New clients usually start with a consultation so the provider can review your goals and explain the right next step. Are you hoping to come in this week, this month, or are you just researching?

Visitor: This week.

Website Support Agent: I can send you to the Botox consultation request. The team will confirm the appointment details through the booking process.

Route: Consult request link.

Lip filler price shopper

Visitor: How much is lip filler?

Website Support Agent: Lip filler pricing depends on the product, amount used, and your goals. The consult is where the provider reviews options and confirms pricing before treatment. Would you like general pricing guidance or the consultation link?

Visitor: Pricing first.

Website Support Agent: Here is the clinic's approved pricing page. If you want the team to review your goals after that, I can help you request a consult.

Route: Pricing page, then consult request.

Laser uncertainty

Visitor: Will laser hair removal work for my skin type?

Website Support Agent: That depends on your skin, hair, treatment area, device, and provider assessment. The safest next step is a consultation so the team can review fit directly. Would you like the laser consultation link?

Route: Consultation, not an eligibility answer.

After-hours staff review

Visitor: I had filler before and had a bad reaction. Can I still book?

Website Support Agent: That should be reviewed by the clinic team directly. I can collect your name, contact information, and the question you want the team to review so they can follow up through the right process.

Route: Staff review.

These flows are short on purpose. A good qualification flow does not trap the visitor in a long script. It gets enough signal to route the person correctly.

Build one source of truth before training the agent

Lead qualification falls apart when the website, booking tool, FAQ, and staff scripts disagree.

Before you train a Website Support Agent, define:

• Treatment categories and approved service names
• Which services require consultation first
• Which questions can be answered from the website
• Which questions must route to staff
• Booking links for consults, services, and follow-up
• Pricing page or approved pricing language
• Phone, email, and contact paths
• After-hours follow-up expectations
• What the AI should never ask or answer

The med spa website FAQ examples article helps with answer content. This article handles the qualification layer on top of those answers.

Where CatchWhen fits

CatchWhen creates a business-specific Website Support Agent for appointment-based local businesses.

For a med spa, that agent should not behave like a generic chatbot. It should ask lightweight qualification questions, answer from approved clinic content, respect boundaries, and route ready visitors to the existing booking, consult, call, or contact path.

The best version does not make the clinic look automated. It makes the first step feel clear.

That is what med spa lead qualification is really for: fewer dead-end website questions, better consult requests, and a cleaner handoff to the team when judgment is needed.