No. SleekAI is configured to describe what a session looks like and what training each practitioner has, but never to claim the work will treat, cure, or improve a specific medical condition. The system prompt enforces that boundary across every conversation regardless of how the visitor phrases the question. If someone asks whether craniosacral can fix their migraines or their child's reflux, the bot redirects to a conversation with the practitioner and a check-in with their physician, rather than answering the implicit medical claim.

Your system prompt should instruct the bot to recognise red flags (acute neurological symptoms, post-injury concerns, infant feeding refusal, suspected concussion without medical clearance) and route to a physician or 911 first. The bot does not attempt to triage. It simply names the red flag, points to appropriate medical care, and offers to be available for booking once the visitor confirms the situation is not urgent. This keeps the chatbot inside its scope and the visitor safe.

Yes, when each practitioner is tagged in custom fields. The bot reads the training lineage into the prompt and matches conversationally. Some visitors arrive with a preference (often because their referring practitioner uses specific language), and the bot routes them accordingly. Others have no preference, and the bot defers to the practitioner's bio framing rather than improvising a comparison the practice has not authored itself.

Yes, in your WordPress database. You set retention through the plugin, typically 14 to 30 days for bodywork practices. Conversations stay on your server, and OpenAI or Anthropic calls use your own API key directly. There is no SleekAI proxy or hosted middleware. Most practices review the log weekly to catch recurring questions that should be added to the bot's instruction or the FAQ pages, and to spot misunderstandings before they reach a booking.

Yes. SleekAI is multibot, so the infant and pediatric pages can run a chat scoped specifically to those intake patterns, while the adult side runs a separate bot with its own instruction. This is useful because parental concerns (cleared by pediatrician, feeding context, birth history framing) are different from adult intake (referral source, prior bodywork history, session frequency expectations), and forcing them into one prompt produces awkward answers in both directions.

The bot can describe whether you accept HSA or FSA cards and whether you provide superbills for out-of-network reimbursement, drawn from your fees page. It cannot verify a specific plan's coverage because that requires a call to the carrier with the patient's member ID. The bot makes that limit explicit: it can quote what you accept in general, but verification happens at intake. This keeps the conversation accurate without overpromising.

Yes. SleekAI's 28+ display conditions let you scope the chatbot to booking-intent pages (contact, fees, practitioner bios, modality overview) and hide it on the blog, the case-study posts, and the deeper modality history pages. Visitors reading those pages are usually researching rather than booking, and pushing chat onto them tends to feel intrusive. Scoping the bot precisely is one of the meaningful differences from a generic site widget.

The bot is configured to recognise distress signals and route to 988 (the US Suicide and Crisis Lifeline) or the visitor's local equivalent before continuing any other flow. Craniosacral practices are not the right place for that conversation, and the system prompt makes that clear with warmth rather than dismissal. After surfacing the crisis line, the bot offers to be available for body-focused booking later if the visitor still wants that, but safety comes first.