Industries

Med spa marketing built around informed inquiries

A prospective patient wants to understand a treatment before requesting a consultation. Your team needs enough context to route that inquiry, without turning a marketing form into a medical intake questionnaire. Between those needs sit practical decisions: which services deserve attention, what a page can responsibly explain, who approves treatment language, and how an inquiry reaches the right person. A proposed engagement with Ninetyfifth Marketing would begin by defining those decisions before choosing channels or producing content.

If search work is part of the scope, our website rule applies. We only do SEO on a site we built.

If you are assessing a med spa marketing agency, the first question is what you need it to own. A focused scope could cover one priority service and its consultation path. A broader scope could include service-page planning, local discovery, advertising, inquiry handling, and measurement. Each component would need a defined deliverable, an internal owner, and an approval requirement. The scope should also identify dependencies that could prevent a page or campaign from being ready for review.

Choose the service and the appointment you can support

An initial planning session would distinguish commercial priorities from operational readiness. A service might be important to the business while still lacking approved descriptions, current provider information, suitable photography permissions, or appointment capacity. Those gaps would affect what could responsibly enter the marketing plan. Rather than treating every treatment as an equal priority, the proposed work would identify a manageable starting scope and document what must be supplied or approved.

• Service priorities: identify the treatments under consideration, their approved names, and whether the intended next step is a consultation, a general inquiry, or an appointment request.
• Operational constraints: confirm locations, appointment availability, routing responsibilities, response coverage, and any services that should be excluded from promotion.
• Content dependencies: list the clinical reviewers, brand approvers, source materials, image permissions, and policy questions needed to prepare each deliverable.

The resulting planning document would separate work the agency could draft from decisions your practice must make. It could also define exclusions, such as clinical recommendations, patient eligibility decisions, medical intake design, or changes to practice software. Naming those boundaries early gives the buyer a concrete way to assess whether the proposed engagement fits the work actually required.

Give each treatment page a decision to support

A treatment page should have a clear purpose within the consultation process. Someone researching a service may need a plain-language explanation, questions to bring to a consultation, and clarity about what the appointment involves. They may also need to understand that suitability, risks, alternatives, and expected recovery require an individualized conversation. Proposed page briefs would specify which questions the content should address and which questions should be directed to a qualified clinician.

Plan the content before drafting the claims

For each selected service, the proposed deliverable could include a content outline, search intent notes, draft headings, body copy, metadata, and a consultation call to action. Drafts would use practice-approved service information as their foundation. Where details about discomfort, downtime, treatment intervals, contraindications, or potential benefits are relevant, the draft would flag them for clinical review. Marketing language would not substitute for that review or present a treatment as suitable for every visitor.

Make the next step specific

The page would explain what the visitor is requesting and what happens afterward, subject to your actual process. For example, a consultation request could be described as a request for staff follow-up if it does not reserve an appointment. Any statement about response timing, consultation fees, deposits, or cancellation terms would require confirmation from the responsible owner. A clear button label would be paired with supporting copy so that the action and its operational meaning agree.

Separate discovery work from paid campaign scope

Search content, local business information, and advertising have different requirements. A proposed discovery scope could examine how selected services are organized, whether location and contact details are consistent across materials you control, and whether important pages can be reached through sensible navigation. Deliverables could include a page map, content revision briefs, metadata drafts, and a prioritized implementation list. Recommendations would be tied to the selected services and locations rather than an open-ended promise to address every search topic.

Paid campaign planning would be a separate decision. Before preparing ads, the scope would establish the service being promoted, the geographic area, the destination page, the inquiry action, and the approval process. Proposed deliverables could include campaign structure, keyword themes, exclusion themes, ad drafts, and landing-page requirements. Any channel selection would remain conditional on current platform rules, the service category, available assets, and the practice's review requirements.

Treatment imagery, promotional wording, and audience choices would receive particular attention during review. A campaign brief would identify where permission records, clinical review, or qualified legal guidance may be needed. If an asset or claim could not be approved, the working scope would document an alternative or hold that item for a decision. Ad spend authorization and campaign activation would be explicit steps, separate from approving a draft.

Define what happens after someone presses submit

The inquiry path would be mapped from the page through the form or booking interface to the person responsible for responding. That map would distinguish a submitted request, a scheduled consultation, and any later status your team elects to track. It would also identify whether staff update those statuses manually or through an approved integration. The proposed deliverable would describe the handoff and its dependencies rather than assume that existing systems exchange information correctly.

• Form scope: propose fields that serve the initial contact purpose, with medical intake questions referred to the appropriate clinical and privacy owners for a separate decision.
• Routing rules: document which team receives each inquiry, how location or service selection affects routing, and what happens when the normal recipient is unavailable.
• Confirmation language: draft an acknowledgment that accurately describes the next step and avoids implying that submission confirms an appointment or establishes treatment eligibility.
• Access and retention questions: identify who needs inquiry access and refer storage, deletion, vendor, and permission decisions to the practice's designated privacy and technical owners.

Measurement would start with a written event plan. It could describe page interactions, consultation-button clicks, and completed request submissions, along with the meaning and limitations of each tracked action. The plan would specify proposed data fields and destinations for technical and privacy review before implementation. Contact details, free-text responses, treatment interests, and page addresses would need explicit assessment where their collection or transmission could raise sensitivity concerns.

Agree on review gates and acceptance criteria

The proposed statement of work would name the deliverables, revision allowances, required inputs, and approval owners. Clinical content would go to a qualified clinical reviewer. Privacy-sensitive collection and tracking decisions would go to the designated privacy owner, with qualified legal or technical review where appropriate. Brand and operational details would have their own approvers. Unresolved comments would remain visible in a review log so that approval of layout does not accidentally stand in for approval of treatment language.

Acceptance criteria could include approved service terminology, working inquiry routes, accurate confirmation messages, completed metadata, and verified behavior for the agreed measurement events. A final handoff could contain the reviewed content, implementation notes, an asset register, the event definitions, and a list of outstanding dependencies. If implementation or ongoing campaign management is included, those responsibilities would be described separately. This gives your team a specific package to evaluate before deciding what should move forward.

We do not have a published client example for this healthcare or dental service under this brand. This page describes a proposed workflow and the decisions we would settle before work begins. It is not a record of patient campaigns, clinical outcomes, or regulatory approval. A qualified practice would review every proposed deliverable and applicable professional rules before launch.