Turn Inquiries Into Booked Consults.
Every Channel. Every Time.

Every dollar this business makes travels the same three-stage path. Your job at each stage is narrow on purpose: you are never trying to do the next stage's job early.

The single most common sales mistake is trying to run the consult during the inquiry -- answering ten questions on the phone, educating in the DMs, debating the program in a comment thread. The staff pack is blunt about this: the goal of every inbound call is name, contact, booked consult. Not education. Not selling. The consult is where selling happens, and it happens with proper time, attention, and the owner (or a trained closer) in the room.

1. Open operations/STAFF_HIRING_TRAINING_PACK.md in your build and read Section 1.1 end to end. It is the source document for every script in this module.
2. Map your inquiry sources. In your build they already exist: the site inquiry form at site/inquiry.html, the lead magnet marketing/lead-magnet/consumer-metabolic-scorecard.pdf (deployment steps in marketing/lead-magnet/LEAD_MAGNET_DEPLOYMENT_SHEET.md), the ad bank marketing/ad-bank/ad-bank.html, the caption bank marketing/social/SOCIAL_CAPTION_BANK_v1.md, and the email sequences in marketing/email-bank/consumer-email-bank.html. Every one of them points at the same two destinations: {{BOOKING_ROUTE}} and {{APPROVED_PHONE}}.
3. Confirm your CRM pipeline stages match the motion: New Inquiry, Consult Booked, Consult Held, Enrolled, plus a Nurture lane for not-yet. If a contact cannot be placed in exactly one stage, the stage list is wrong -- fix the list, not the contact.
4. Log everything. The staff pack's rule is absolute: an unlogged contact did not happen. Every call, DM, text, and voicemail gets a CRM entry the moment it is handled.
5. Track the four weekly numbers in tools/partner-kpi-tracker.html: inquiries in, consults booked, consults held, enrollments. These four numbers ARE the sales report -- read them out at the weekly huddle (staff pack Section 1.4) before any commentary.

Draw the three-stage funnel on paper from memory. Under each stage, write its ONE goal and list which of your build's files feed it. Then open your CRM and verify a test contact can move New Inquiry to Enrolled without ambiguity. Total time: 15 minutes.

Improvised answers drift. Drifted answers make promises, guess at facts, and wander into health territory. Your staff pack ships tested scripts for the three channels where inquiries actually arrive, and the standard is simple: everyone who touches the phone or inbox -- including you -- runs the script. The scripts live in Section 1.1 of operations/STAFF_HIRING_TRAINING_PACK.md; load them into your CRM as saved replies so nobody types them fresh.

Branch rules (memorize these three):

• Guardrail question mid-call (medication, condition, outcome) -- use the say-this line from Lesson 4's table, then return to Step 3.
• Caller will not book -- "No problem. Can I text you the booking link so it is there when you are ready?" Send {{BOOKING_ROUTE}}. Log as inquiry, never as lost.
• Caller is angry or reporting a problem -- skip booking entirely, go straight to the escalation script (Lesson 4).

If the return call goes unanswered: send the same content as a text with the booking link, and log both touches in the CRM.

Load all five scripts (phone, three DM scenarios, voicemail) into your CRM as saved replies -- the staff pack's Day-1 checklist already requires this. Then run one out-loud phone drill: a partner plays a chatty caller with a price question, and you get from "hello" to a booked test slot on {{BOOKING_ROUTE}} in under three minutes. That three-minute drill is also huddle training topic #2 -- reuse it weekly.

A booking system only produces consults if the humans around it follow four disciplines: respond fast, book live, confirm every time, and recover no-shows the same day. Miss any one and the calendar leaks. {{BOOKING_ROUTE}} is your single booking destination -- every ad, caption, email, and script in your build already points there, which means every leak is a people-process leak, not a marketing leak.

1. The 15-minute standard. Every DM, text, and email gets a first response inside 15 minutes during posted hours, first thing next morning otherwise. Phones: answered inside three rings. Voicemails: returned same business day, two attempts, then text. These are the standards written into both job descriptions in your staff pack -- hold yourself to them before you hold staff to them.
2. Book live, never "send a link and hope." On the phone, book while they hold (script Step 4) and read the slot back: day, date, time. The link-by-text branch exists only for callers who decline a live booking -- and even then it is sent inside the same conversation, logged as inquiry.
3. Confirm the machinery. The confirmation text and email must actually fire. The Day-1 checklist in operations/STAFF_HIRING_TRAINING_PACK.md has you create a test booking on {{BOOKING_ROUTE}}, move it, cancel it, and watch the confirmations send. Repeat that test any time you touch calendar settings.
4. Confirm next-day appointments. A personal touch the day before -- text or call -- is the cheapest show-rate lever that exists. It is a listed front-desk responsibility, not an optional nicety.
5. Rebook no-shows the same day they no-show. Same day is the whole trick: the no-show still wants what they booked for; a week later they are a stranger again. Script it plainly: "We missed you today -- no drama. I have two openings this week, want either?"
6. Watch show rate weekly. Consults booked vs consults held lives in tools/partner-kpi-tracker.html and gets read out at the huddle. A sagging show rate means confirmations or reminders broke -- check the machinery before blaming the market.

Run the full booking machinery test right now: create a test booking on {{BOOKING_ROUTE}}, verify the confirmation text and email both fire, move the booking, cancel it. Then time yourself answering a mock DM with Scenario 2 -- from "message received" to "reply sent and logged" must land under 15 minutes with room to spare.

Compliance guardrails are not a brake on selling -- they are what makes selling safe enough to delegate. A desk that never guesses at health questions is a desk you can staff. A script that never promises outcomes is a script that never generates a refund fight, a review disaster, or a regulator's attention. The guardrails page (Section 1.1 of operations/STAFF_HIRING_TRAINING_PACK.md) is signed by every hire on Day 1 before they touch phone, inbox, or DMs -- and it protects your close rate as much as your license to operate.

The three lines that never move:

1. Staff never diagnose. No naming conditions, no "sounds like," no interpreting symptoms, labs, or health history. Ever.
2. Staff never promise outcomes. No numbers, no timelines, no "you will," no repeating another client's result as a prediction.
3. Staff never discuss medication. Not prescriptions, not dosing, not comparisons, not "instead of," not "alongside." The word medication ends the staff portion of the conversation and starts an escalation.

Everything the business offers is described in supports language only: supports, is designed to support, is part of, helps you build. That is the whole vocabulary for what the program does -- and note that it is genuinely honest, which is why it holds up in a sales conversation.

Escalation is automatic -- no judgment call required. Staff stop, log the contact, and route to {{SIGNATURE_NAME}} the same day when any of these appear:

Print the guardrails page from operations/STAFF_HIRING_TRAINING_PACK.md Section 1.1, read it aloud (yes, alone counts), and sign it yourself -- the owner signs first, then every hire. Then quiz yourself cold: three lines from memory, ten triggers from memory, escalation script verbatim. That cold quiz is the Day-30 fluency bar you will hold staff to (Section 1.5), so clear it first.

Price questions arrive at every stage, and the rule is the same at every stage: pricing is presented at the consult, in person, by someone authorized to present it. Your program pricing is [CONFIG: your program pricing] -- set by you, published nowhere in the marketing stack, and quoted from a printed sheet, never from memory. This is not evasion; it is accuracy. The honest answer to "how much?" before a consult is "it depends on what you actually need," because it does.

Why this structure sells better than a price list: a number without context is only ever compared to zero. A number presented inside a consult is compared to the mapped process, the accountability structure, and the person's own stated goals. Same number, different conversation.

1. On the phone or in DMs: Scenario 2, verbatim -- "Pricing is covered at the consult because it depends on what you actually need -- flat answer either way, no games. The consult itself is free: {{BOOKING_ROUTE}}." Never guess, never quote from memory, never discount on the spot (all three are named never-says in the staff pack).
2. At the consult: present from a one-page printed pricing sheet -- [CONFIG: your program pricing] filled in, options laid out, no math done aloud. Hand it over, walk the options top to bottom, then stop talking.
3. Discount requests: the desk has zero discount authority -- "That is {{SIGNATURE_NAME}}'s call, and I will flag it today." Any flexibility you choose to offer is [CONFIG: partner's own discount policy], decided in advance, never invented mid-conversation.
4. Payment logistics (methods, terms, refunds): answered from your written policy only -- [CONFIG: payment and refund policy -- partner's counsel]. A refund demand is escalation trigger #5, not a desk negotiation.

1. Prepare: pull the CRM record before the consult. Know the inquiry source (scorecard download? inquiry.html form? call-in?) and everything already logged. Never make someone repeat their story.
2. Open with their starting point: the consult promise made in every script is "where your actual situation gets looked at" -- so look at it. Ask, listen, take notes in the CRM.
3. Explain the program in supports language: walk the structure of consumer-program/CONSUMER_PROGRAM_12WEEK_MASTER.html -- the mapped weeks, the check-ins, the accountability. Structure is the product; describe what it IS, never what results it will produce. The say-this table from Lesson 4 applies in the consult room double.
4. Guardrails still bind: anything medical surfaced in a consult routes to the inquirer's own doctor and to {{SIGNATURE_NAME}} -- the consult is not a clinical screening, and escalation triggers fire in this room too.
5. Present pricing from the printed sheet (step 2 above), then ask one closing question: "Do you want to start?" Silence after the question. No pressure was promised in every script -- honor it, because a pressured enrollee is a refund demand with a start date.
6. Handle "I need to think about it" honestly: "Take the time. I will put a note to check in with you [day] -- and nothing about this changes if you take a week." Log the follow-up date in the CRM and actually follow up. The nurture emails in marketing/email-bank/consumer-email-bank.html carry the long tail.
7. On a yes, enroll cleanly: paperwork per [CONFIG: enrollment agreement -- partner's counsel], first session booked before they leave the room (or the call), welcome materials handed over -- consumer-guides/ATLAS_ConsumerGuide_SevenSecrets_v1_PRINT.pdf makes a strong welcome piece -- and the CRM stage moved to Enrolled the same hour.

Build your one-page pricing sheet: fill [CONFIG: your program pricing] with your actual offer structure, print five copies, and put them where consults happen. Then role-play one full consult with a partner playing "I need to think about it" -- your job is to close the conversation warmly, log the follow-up date, and NOT chase. Time the whole consult; if it runs past 45 minutes, you are educating instead of consulting.