Yes, using your published modality page. SleekAI reads the WordPress posts you wrote, so the explanation matches what visitors see elsewhere on the site. The bot frames the comparison technically (sustained low-force pressure on fascia versus stripping strokes on muscle, longer hold times, different session lengths) rather than dismissively claiming one is better than the other. Whether myofascial release is the right fit for a specific person is left for the therapist to decide at intake, which keeps the boundary intact while still being useful.

The system prompt is configured to recognise post-surgical context and require written clearance from the surgeon before discussing booking in any detail. The bot does not assess scope, since that is the therapist's job at the start of the session, but the upstream gate (do you have written clearance, what restrictions did the surgeon list) happens conversationally before scheduling. Most practices set this boundary to a 6-week minimum post-op with written clearance as a hard requirement, and the bot enforces that consistently.

Yes, when each therapist is tagged in custom fields. The bot reads training lineage into the prompt and matches conversationally. Visitors referred by other practitioners often arrive with specific language (JFB unwinding, Rolf line work, Anatomy Trains meridians) and the bot routes them to the right person rather than booking a JFB-only therapist for a visitor looking for structural integration work. Training is not interchangeable in this niche.

No. SleekAI refuses diagnosis, refuses to claim the work will treat a specific medical condition, and refuses to position myofascial release as a substitute for medical care. The system prompt enforces those refusals across every conversation regardless of how the question is phrased. If a visitor describes red-flag symptoms (numbness, weakness, signs of DVT, post-op concerns without clearance), the bot routes to a physician or 911 before any other flow, and only offers booking when the situation is appropriate.

Yes. The 28+ display conditions let you scope the chatbot to booking-intent pages (contact, fees, therapist bios, modality overview) and hide it on the blog, case studies, and longer educational content. Visitors reading those pages are researching, not booking, and pushing chat onto them tends to feel intrusive. For myofascial practices specifically, most firms also hide the bot on the post-surgical recovery overview page since that conversation needs to start with clearance, not chat.

Yes, in your WordPress database. Retention is set 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 without a SleekAI proxy. Most practices review the log weekly to catch recurring intake questions that should be added to the FAQ pages, and to spot any post-surgical visitors whose clearance question needs human follow-up before the chat can move on.

Yes. SleekAI is multibot, so the prenatal page can run a chat scoped specifically to prenatal intake (positioning preferences, trimester gating, comfort considerations) while the post-surgical recovery page runs a separate bot with hard clearance requirements at the top of its instruction. This is useful because the two intake patterns share almost no overlap, and forcing them into one prompt produces compromised answers in both directions.

The bot can describe whether the practice accepts HSA or FSA cards and whether it provides superbills for out-of-network reimbursement, drawn from your fees page. It cannot verify a specific plan because that requires a call to the carrier with the patient's member ID and the result depends on plan-specific deductibles. The bot makes that limit explicit, which keeps the conversation accurate without overpromising what bodywork coverage looks like at any given plan.