This is the whole rulebook in one place. Every other module taught you how to grow. This one makes sure nothing you say -- on the phone, in an ad, in a DM, on a flyer -- ever turns into a claim you cannot defend. Learn it, drill it, make your team sign it.
You will convert outcome claims into DSHEA-safe wording on sight, using the drill patterns in Lesson 1.
Never diagnose, never promise, never discuss medication -- and run the escalation script without hesitating.
You will know exactly what may be published, what needs a written release, and what only counsel-cleared documents may say.
Day 1, read aloud, signed, filed, re-run on drift -- for every hire, clinic or platform.
{{PUBLIC_BRAND_NAME}} is a metabolic wellness business. It is not a drug company and not a medical practice making disease claims. Under DSHEA-style language discipline, everything the business offers is described one way: it supports. It supports healthy habits. It is designed to support your routine. It is part of a structured program. It helps you build consistency.
The moment a sentence connects your program to a disease or promises a health outcome, it stops being marketing and becomes a claim -- the kind regulators read letter by letter. The fix is not to whisper the claim more carefully. The fix is to never make it.
Your approved vocabulary lives in the assets you were shipped. The words there were chosen deliberately. Your job is to stay inside them.
| Green words (use freely) | Red words (never attach to your program) |
|---|---|
| supports, is designed to support, helps you build, is part of, structured, mapped, accountability, routine, habits, consistency, energy for daily life, overall wellness, healthy lifestyle | treats, cures, prevents, diagnoses, reverses, heals, fixes, eliminates, "clinically proven to," any disease or condition name attached to your program, any drug name, "FDA approved" |
The red column is banned even inside softeners. "May help reverse" is still a reversal claim. "Some say it can heal" is still a healing claim. Quotation marks, hedges, and emojis do not launder a claim.
Each drill shows a sentence a well-meaning partner has actually tried to publish. Say your rewrite out loud before you open the answer.
Marketing compliance protects you in public. Conversation compliance protects you one customer at a time -- on the phone, in DMs, at the front desk. Your operations/STAFF_HIRING_TRAINING_PACK.md Section 1.1 ("The Compliance Guardrails") sets three lines. They apply to you, {{SIGNATURE_NAME}}, exactly as much as to any hire:
Notice the trap inside line 3: "alongside" and "instead of" feel helpful and neutral. They are still medication discussion. There is no safe angle into that conversation for staff -- the only move is the escalation.
Section 1.1 of the staff pack lists ten triggers that route to the owner the same day, no judgment call required. Learn the big ones cold:
The escalation script is one sentence: "That is exactly the kind of question that goes straight to {{SIGNATURE_NAME}}. I am flagging it right now, and you will hear back today. What is the best number or email for that?" Then log the contact and route it. A person who mentioned medication does not get booked until the escalation clears.
A happy customer's story feels like free marketing. Handled wrong, it is the most expensive sentence you will ever publish, because a testimonial you select, post, or amplify becomes YOUR claim. If a customer says "this fixed my blood sugar" and you repost it, you just made a disease claim -- with a witness.
The staff pack already sets the conversational rule: "People's experiences are their own, and we never turn one person's experience into a promise for the next." Publishing has three more gates.
| Gate | The rule | What fails it |
|---|---|---|
| 1. Written release | A signed written release on file before anything is published. [CONFIG: written release form and process -- counsel] -- until counsel supplies your release form, the publishable testimonial count is zero. | "She said I could use it" (verbal). A DM screenshot. A public review copied onto your site. |
| 2. Content check | The testimonial itself must pass Lesson 1: no disease or condition names, no medication mentions, no "cured / fixed / reversed," no implication the result is typical or predicted. | "Down 22 lbs!" as a headline. "My doctor was amazed." "Better than [drug name]." |
| 3. Framing check | Presented as one person's experience, never as a prediction, with results-vary framing per site/disclosures.html. Never "typical," never "average," never "you will too." | "Results like Maria's every week!" A before/after grid implying a standard outcome. |
A customer posts on YOUR page: "This program cured my [condition]!!" You did not write it -- but it now lives on a channel you moderate. Leaving it up (or liking it) is adoption. The move: hide or remove it per your platform policy, reply privately with thanks and a gentle correction, log it, and flag it to {{SIGNATURE_NAME}}. Comment moderation is claims control.
Ads are your highest-risk surface: paid distribution means maximum reach for any bad sentence, plus platform ad review, plus screenshots that outlive the campaign. Your build ships pre-written, language-disciplined creative precisely so you never have to improvise under deadline pressure:
The rule: publish from the bank. The banks are not inspiration -- they are the approved claim set. Anything new you write must clear the same bar before money goes behind it.
Everything your business says falls into exactly two classes, and mixing them up is how good operators get hurt:
| Class A -- operating language (you and staff may use) | Class B -- only counsel-cleared documents may say it |
|---|---|
| Supports language, program structure, scheduling, logistics, the scripted answers in the staff pack, copy published from the banks after the Lesson 4 gate. | Legal disclaimers and their exact wording; terms of service and privacy commitments; refund and guarantee terms; testimonial releases; anything about regulatory status; any response to a regulator, legal threat, or media inquiry. |
Class B lives in documents -- site/disclosures.html, site/terms.html, site/privacy.html -- and in counsel's files. Staff never paraphrase Class B. If someone asks a Class B question, the answer is a pointer to the document or an escalation, never an improvised summary. Your builds mark every unset legal value with [CONFIG: ... -- counsel] tags: those are not placeholders to fill creatively. They are holes only your attorney fills.
Rules on paper protect nobody. The staff pack makes the guardrails enforceable with a ritual, and it is not optional:
Eight scenarios, all drawn from situations partners actually face. Pass mark is 7 of 8. Wrong answers here are cheap; wrong answers in the wild are not. The full answer key appears after you submit.
The answer key with explanations is now shown under each question. Review every miss, re-read the lesson it points to, and retake until you clear 7 of 8. Your best score is saved on this device.