Aesthetic Consultation Form Template: Qualify the Next Step Safely

In short: An aesthetic consultation request form should collect only enough to identify the person, understand the service category, route the next step and contact them through an approved channel. Keep it short, and do not use it to diagnose, determine candidacy, have people self-assess contraindications or promise results. Keep it separate from medical intake and informed consent, and add a field only when it changes routing and has an owner.

An aesthetic consultation request form should collect only enough information to identify the person, understand the requested service category, route the next step, and contact them through an approved channel. It should not diagnose, determine candidacy, ask a person to self-assess contraindications, promise a treatment result, or replace a clinic's clinical intake and informed-consent process.

The practical template is short: name, contact method, broad service interest, new-or-returning status, preferred location or consultation format, broad scheduling preference, a limited question box with a warning not to submit urgent or highly sensitive information, communication choice, and acknowledgment of what happens next. Add a field only when it changes routing and has an owner.

This distinction matters because “consultation form” can refer to several different documents. A public request form, a medical-history intake, a photo upload, a treatment plan, and informed consent have different purposes, access, timing, and governance. This article covers the first one.

Define the form's single job

Write the completion sentence before choosing fields:

When this form is submitted, [role] will review [specific information] and take [one of defined next actions] within [clinic-approved service window].

If the team cannot complete that sentence, the form is not ready. A form that feeds an unowned inbox merely changes where the delay occurs.

Choose one primary job:

• request a general aesthetic consultation;

• ask an administrative question before booking;

• express interest in a service that requires staff review; or

• request help choosing the correct appointment type.

Do not make one form handle emergencies, adverse-event reports, existing appointment changes, employment inquiries, vendor pitches, and marketing subscriptions. Give those jobs separate routes and language. A public form should clearly say it is not monitored for emergencies and provide the clinic-approved urgent route without attempting to assess urgency.

Separate five documents that are often confused

Consultation request

Captures contact and routing information before an appointment. This is the template in this article.

Administrative intake

Collects operational details needed for a scheduled visit, such as preferred name, accessibility request, communication preference, or arrival information. Keep it proportional.

Clinical or medical-history intake

May collect health information for review by authorized people under the clinic's policies and applicable requirements. It needs a deliberately governed system, not an accidental expansion of a marketing form.

Photo or document submission

Creates additional privacy, security, access, quality, and retention questions. Do not add uploads because a form builder makes the field easy.

Informed consent

Documents an informed process for a defined service under applicable professional and legal requirements. It is not the same as agreeing to be contacted or acknowledging a privacy notice.

A checkbox cannot transform a lead form into informed clinical consent. HHS guidance also distinguishes “consent” from an authorization required for particular uses or disclosures under the HIPAA Privacy Rule. Applicability and exact duties need qualified review.

Apply a purpose test to every field

For each proposed field, document:

1. the decision it changes;

2. who needs it;

3. when they need it;

4. where it is stored and copied;

5. how long it is retained;

6. what happens if it is blank;

7. whether a less sensitive alternative works; and

8. what notice or permission is required.

Remove fields that are merely “nice to know.” A public lead does not need to provide a full medical story so marketing can decide which calendar link to send. Conversely, do not hide a question that genuinely changes whether staff or a qualified reviewer must take over.

HHS's minimum-necessary standard applies to covered entities in defined uses and disclosures, with exceptions. Do not cite it as proof that every spa is covered by HIPAA. Use qualified privacy and legal advice to classify the clinic, the data, vendors, and workflows. The operational lesson is to make data purpose and access explicit.

Use the field-by-field template

Keep a field only when its purpose, owner, and safer alternative are understood.

1. Preferred name

Ask how the person wants to be addressed. Make legal name optional unless it is genuinely required at this stage.

2. Contact details

Collect the channel the clinic can support. If both email and mobile number are requested, explain which is required and why. Validate format without exposing whether an account already exists.

3. Preferred contact method

Offer actual choices the team honors. Do not imply that selecting SMS alone supplies every permission required for automated marketing texts.

4. New or returning client

This helps staff search for an existing record and avoid duplicates. Do not reveal client status on the public confirmation page.

5. Broad service interest

Use clinic-approved categories such as skin consultation, injectable consultation, body service consultation, wellness service, or not sure. Avoid symptom checklists and claims about suitability.

6. Goal in the person's own words

Make this optional and limit length. Prompt for a general goal or administrative question, not a diagnosis. Show: “Please do not include urgent concerns, detailed medical history, or payment-card information.”

7. Location or consultation preference

Ask only when it changes staffing or availability. Name virtual options only if the clinic actually supports them and has approved what can occur remotely.

8. Broad availability

Use day or time bands when staff must assist. When an appropriate consultation can be self-booked, offer current availability instead of collecting preferences that someone must manually reconcile.

9. Accessibility or communication request

Provide a voluntary way to request assistance without forcing a diagnosis. Include another contact route if the form itself is a barrier.

10. Referral source

Optional marketing attribution should not block submission. Keep choices broad and include “prefer not to say.”

11. Contact acknowledgment

Explain who will respond, through which chosen channel, and for what request. Separate this from any optional marketing permission.

12. Privacy and next-step acknowledgment

Link to the applicable notice and state that submission requests contact; it does not establish suitability, guarantee an appointment, or create informed treatment consent.

Use conditional fields sparingly

Conditional logic can reduce clutter, but it can also create hidden collection paths that reviewers forget. Use it when one answer clearly changes the next administrative question. Examples include selecting a location before showing location-specific consultation options or identifying an existing client before asking for an appointment reference.

Do not use public conditional logic to imitate diagnosis: “If you have condition X, choose treatment Y.” Do not present a marketing form as a clinical decision tool unless the clinic has separately validated and governed that use.

Maintain a field map that lists every branch. Test it with contradictory answers, skipped fields, back navigation, mobile autofill, translation, keyboard navigation, and screen readers. Export test submissions and inspect where hidden fields appear in emails, notifications, integrations, and spreadsheets.

Route the submission to one of four outcomes

Every submission needs one owned outcome; a confirmation page is not the end of the workflow.

Direct consultation booking

Use when the selected next step is clearly appropriate for public booking. Show live availability and carry permitted context without making the person re-enter it.

Staff administrative reply

Use for pricing structure, location, scheduling help, published policy, accessibility support, or uncertainty about the correct appointment type.

Qualified review

Use when the message includes personal suitability, health information, a possible complication, or another question outside administrative scope. The form should not answer it. Route it under the clinic's protocol.

Outside scope or different route

Use for unsupported services, vendor requests, careers, existing booking changes, or urgent paths. Provide the correct destination without creating false expectations.

Every outcome needs an owner, status, service window, fallback, and closure code. A confirmation screen is not a completed handoff.

Write a confirmation that reduces uncertainty

A good confirmation states:

• that the request was received;

• the clinic or location receiving it;

• what type of request was recorded;

• what happens next;

• the expected service window stated honestly;

• how to correct or withdraw the request;

• the non-emergency boundary; and

• a booking option only when appropriate.

Do not repeat sensitive free text in a confirmation email or page. Do not include a person's full submission in a subject line, calendar description, analytics event, or notification preview.

Example:

Thank you. [Clinic] received your consultation request for [broad category]. Our team will review it during [stated business coverage] and contact you by [chosen method]. This form is not monitored for emergencies and does not determine treatment suitability. To change your request, use [approved contact route].

Test accessibility and error recovery

WCAG 2.2 is the current W3C Recommendation for web accessibility. Practical form tests include visible labels, instructions that do not rely only on color, keyboard access, meaningful focus order, clear required-state indicators, and errors that identify the field and explain how to fix it.

Test the exact embedded form, not only the vendor demo. On a 390-pixel viewport:

• zoom to 200 percent;

• enlarge text;

• submit every error state;

• navigate with keyboard only;

• use a screen reader to hear labels and errors;

• check date, phone, and dropdown controls;

• confirm the submit button does not disappear behind a banner; and

• verify focus moves to the error summary or confirmation.

The med spa website accessibility checklist covers the wider journey. Fixing the form alone does not help if the service page or booking step remains unusable.

Test failure recovery before collecting real inquiries

A form needs a failure path as much as a success screen. Disable a required integration, use an invalid email address, interrupt the connection during submission, refresh after clicking submit, and submit twice. The visitor should learn whether the request was received without seeing technical details or creating uncontrolled duplicates.

Assign monitoring for form availability, notification delivery, queue creation, and aged unassigned requests. Keep a fallback contact route visible on the same page. If a submission reaches the form database but not the staff queue, the system should create an observable exception rather than a silent loss.

Review analytics conservatively. Record visits, form starts, validation errors, completions, and the next owned action when those events can be collected appropriately. Do not place free-text answers, names, email addresses, phone numbers, service concerns, or other sensitive values in analytics labels or advertising pixels. Confirm what embedded tools transmit before launch.

Read the surrounding page as part of the test. The med spa service page template shows how to answer common questions and set a clear next step before asking for contact information. A better page can reduce unnecessary submissions. If the clinic also offers conversational intake, apply the separate permission and handoff tests in the AI chatbot buyer guide; do not let the chatbot bypass the form's data boundary.

Keep marketing permission separate

A consultation request is an operational request for contact about that inquiry. A campaign subscription is a different purpose. Use separate, optional controls and record the source, language, time, and channel permission needed for the clinic's program.

Do not preselect a marketing box. Do not make marketing consent a condition of requesting an ordinary consultation unless qualified counsel confirms the design. Make opt-out mechanisms functional across connected systems and suppress future sends as required.

FTC guidance applies to commercial email, and FCC rules govern certain automated calls and texts. State laws and professional requirements may add duties. The form should preserve the evidence your compliance process needs rather than relying on a generic “I agree” sentence.

Set retention, access, and deletion rules before launch

Document where submissions live, who can view them, where notifications copy them, when they become client records, and when unsuccessful inquiries are deleted or de-identified under clinic policy. Review vendor access and exports. Remove access promptly when a staff member changes roles.

Use test identities to inspect:

• the form database;

• email and SMS notifications;

• staff dashboards;

• calendar events;

• analytics and advertising tools;

• spreadsheet or integration destinations;

• backups and exports; and

• mobile lock-screen previews.

Never ask for raw payment-card details in a free-text field. Never assume a secure form makes every downstream destination appropriate.

Connect the form to a measured workflow

Track process quality before claiming conversion impact:

• completed submissions by source;

• error and abandonment points when available lawfully;

• duplicate rate;

• percentage assigned to an owner;

• routing outcome;

• time to accepted review;

• consultation booked;

• outside-scope and escalation count;

• opt-outs or complaints; and

• forms containing information the form explicitly asked people not to submit.

Review the last item. It may show that instructions are unclear or the form invites detail through an overly broad prompt.

The med spa booking flow guide helps test the next step. The consultation follow-up templates begin only after the consultation occurs.

Frequently asked questions

Is a consultation request form the same as medical intake?

No. A consultation request generally routes contact and broad service interest before an appointment. Medical or clinical intake may collect health information for qualified review under separate policies and applicable requirements. Do not combine them by default.

Should a med spa ask for photos in the first form?

Only after the clinic has defined a legitimate purpose, secure collection and storage, access, retention, review, deletion, and an alternative for people who cannot or do not want to upload. A photo should not be an automatic requirement for asking an administrative question.

How many fields should the form have?

There is no magic number. Keep each field only when it changes routing or the next action. Test completion and data quality rather than copying a competitor's field count.

Can the form recommend a treatment?

A public lead form should not diagnose or make individualized treatment recommendations. It can route someone to general information, staff help, or an appropriate consultation.

Build the request path in Workee without crossing the boundary

Workee's September 2026 product update says Lead Forms can capture contact details, service interest, consultation and general inquiries, direct links, embedded submissions, and leads for team review. Its booking page documents available-time scheduling, confirmations, reminders, and buffers.

Use those verified capabilities to build a bounded path: request, review, route, and book. Keep clinical intake, qualified judgment, informed consent, and emergency processes in the systems and roles your clinic has approved. The most useful consultation form is not the longest one; it is the form whose every field changes a safe next action.