No. SleekAI is configured to refuse outcome claims for individual cases. It explains in general terms what music therapy can address (communication, emotional regulation, motor function, family support in palliative care) using your published program copy, and refers every individual question to a board-certified music therapist. The boundary is in the system prompt and applies to every conversation regardless of how the question is framed. Outcome claims from a chatbot are exactly the kind of harm bounded systems are built to prevent.

Through WordPress taxonomies and custom fields. Tag each therapist with populations served (NICU, hospice, pediatric, adult mental health, NMT, dementia), and SleekAI matches inquiries accordingly. A NICU referral routes to the NICU-credentialed MT-BC, a hospice family routes to the hospice specialist. The match is conversational, which lets the family share context without filling out a long form before they know who they'll be working with.

Yes. The intake script branches on whether the visitor is a family member, the client themselves, or a referring clinician or case manager. Each branch captures different details: family inquiries focus on the client's age, focus area, and setting; clinical referrals capture the referring provider, primary diagnosis (general category, not specifics over chat), and any case management or insurance context. Both flows summarize cleanly for the therapist on the consult call.

Yes, if you publish them as content. Most practices maintain a school services page that lists which districts they contract with, the IEP-related services they provide, and how billing works. The bot reads from that page and answers district-specific questions with whatever you've published, without making promises about coverage you don't offer. School-related inquiries get a different intake script focused on coordinator name, district, and service request rather than family-level intake.

In your WordPress database. Model calls go to OpenAI, Anthropic, Google, or OpenRouter using your own API key, never through any Sleek-hosted service. You set retention through plugin settings, typically 30 or 60 days. For a practice handling PHI, treat the bot as an administrative tool and avoid asking for clinical detail in chat. The intake should capture enough to route the call, not enough to be a clinical record.

Yes. Publish a clinical partnerships page describing your hospice, NICU, or hospital partner work, and the bot answers questions from care coordinators about scope, scheduling, billing, and credentialing. The intake for partnerships looks different from family intake: facility name, point of contact, patient population, and care setting. Route those inquiries to the clinical partnerships coordinator rather than the standard consult flow.

Yes. SleekAI is multibot. You can run a parent-facing bot on the family-services pages and a coordinator-facing bot on the school services page, each with its own tone, intake script, and routing. School coordinators ask about IEP-aligned goals, contract structure, and billing; families ask about session content and session frequency. Splitting them produces better answers for both audiences than trying to handle everything in one prompt.

Yes. Publish both service models as pages with the relevant policy (technology requirements for telehealth, geographic radius for in-home, equipment provided, fees). The bot reads both and matches the family to the appropriate model based on geography and access. For telehealth specifically the bot can describe the platform and what to expect, while leaving the clinical fit decision to the MT-BC at the consult.