No. The system prompt holds a firm boundary against claiming CBD helps with sleep, anxiety, pain, inflammation, or any specific condition. The bot describes products you stock (spectrum, dose, carrier, extraction, lab status, price) and refers therapeutic questions to pharmacists or doctors. This stance is consistent with EU advertising rules and FDA-equivalent guidance in most jurisdictions where CBD is sold.

Yes. Add COA links, batch numbers, and testing dates as fields on each product. The bot surfaces them in conversation when customers ask. A customer asking 'is there a lab certificate for this oil' gets a real link, not a 'check the page' deflection. For shops that batch-test, the bot can also quote which COA applies to the current bottle on the shelf.

Yes. Full-spectrum (CBD plus minor cannabinoids plus trace THC), broad-spectrum (minor cannabinoids, no THC), and isolate (CBD only) all live as taxonomy fields. Form distinctions (oil, gummy, capsule, topical, vape) and carrier types (MCT, hemp-seed, olive) similarly. A customer comparing two oils gets a side-by-side from your data with the meaningful differences highlighted.

Only what the label says. The bot quotes manufacturer-stated typical use language verbatim, including drops per serving and mg per serving. It does not personalize dosage for body weight, condition, or use case, and it does not suggest 'start low, go slow' as personalized advice. Dosage tuning is a pharmacist or doctor's job, especially for customers on other medications where CBD interactions matter.

Yes. Multibot plus display conditions lets a hemp-food bot live on /hemp-foods/ describing seeds, oils, and protein powders without any CBD-related claims, while a CBD bot on /cbd/ handles spectrum and form questions with the therapeutic-claim boundary. Topical products and ingestible products can also live in separate scopes if you want different tones.

Yours. SleekAI is bring-your-own-key for OpenAI, Anthropic, Google, or OpenRouter. CBD retailers benefit from a model with strong refusal behaviour because therapeutic-claim avoidance is a compliance issue. Conversation logs let you audit interactions and tighten the prompt when a customer pushes for advice the bot should not give. That visibility is the kind of compliance documentation a regulated category needs.

Yes. The bot quotes the EU's 0.2% THC limit for hemp-derived CBD and your shop's stated compliance status from product pages. For products sold in jurisdictions with different limits (UK at 1mg per bottle, some US states with 0.3%), the bot can reflect those limits from your published category pages. THC content is one of the meta fields you should keep accurate because regulatory scrutiny lives there.

It refuses. CBD can interact with several common medications via the CYP450 enzyme system, and those interactions are pharmacist territory. The bot refers customers to their pharmacist or doctor with their full medication list before starting any CBD product. This refusal is consistent and explicit, which is the only sensible stance for a retailer in this category.