No, and the system prompt explicitly forbids it. The bot will not quote a calorie target, a protein-fat-carb split, a body-fat-percentage goal, or a pound-loss timeline. Those are coach decisions after a real conversation and an intake. The refusal is enforced in the prompt and the guideline filter. Generic chatbots make this mistake constantly because their templates optimise for the close, and it's the most common reason a nutrition chatbot crosses into clinical territory.

Routing is explicit. Any mention of restriction history (past or present), binge episodes, purging, laxative use, compulsive exercise, body-image distress, or active ED concern routes the conversation to a clinical referral path. The bot does not run an intake, does not propose a calorie target, does not push a self-serve checkout, and surfaces NEDA's helpline (1-800-931-2237 in the US, or an equivalent local hotline you configure) for active concerns. The coach decides on the discovery call whether coaching is the right fit or whether a clinician with ED training is more appropriate.

No. Supplement recommendations are out of scope for a coaching chatbot regardless of the coach's credential. The bot will not name a brand, a dose, or a timing for any supplement. It can describe the coach's general philosophy on supplementation ("food first, supplements only where indicated by a clinician") at a marketing level and route any specific supplement question to the discovery call or to the prospect's healthcare team.

Yes, with different system prompts. Registered dietitians can configure the bot to acknowledge their clinical scope (medical nutrition therapy, condition-specific protocols where licensed) inside the boundary of what they're licensed to do in their state or country. Non-RD coaches keep a tighter prompt with no clinical scope. The right configuration depends on credential and jurisdiction, and the prompt should be reviewed by the coach's compliance or legal advisor.

No. The bot is configured to refuse any condition-specific protocol (PCOS, type 2 diabetes, thyroid, IBS, IBD, hypertension) and any medication interaction question. Those route to the prospect's healthcare team. The bot can acknowledge that the coach has experience working with clients in those populations at a marketing level, but it will not propose a protocol or imply a clinical outcome.

Indirectly. SleekAI does not write into Practice Better, Healthie, or That Clean Life directly. It captures the discovery call booking, the goal, the intake answers, and any flags (ED history, medical condition, medication) and pushes the lead via webhook or email. The coach onboards the client inside their platform the same way they would after a phone consultation. Real-time food logs and meal plans stay in the coaching platform.

No. The system prompt frames it as an assistant for the coaching business, not as the coach. It describes the coach's approach, credentials, and packages, but it will not roleplay as Coach Mara during a sales conversation. Prospects who want plan-specific guidance get routed to the discovery call. That separation protects the coach-client relationship and the scope-of-practice boundary.

Yes. SleekAI is bring-your-own-key, so prompts go from your WordPress server directly to OpenAI, Anthropic, Google, or OpenRouter. Conversation logs stay in your WordPress database, not in a SaaS dashboard. For nutrition coaches handling health-adjacent intake, document the chatbot in your privacy notice, list it in your scope-of-practice disclosure, and set retention to match your records policy. For RDs working in the US, review HIPAA applicability with a compliance advisor.