No. SleekAI is configured to refuse exercise prescriptions, dosing, or progression advice. It refers visitors to a licensed physiotherapist for any clinical decision. Even when the patient is six weeks post-op and just wants a basic quad set, the bot defers because the right exercise depends on the surgeon's protocol, the surgical findings, and the current range of motion. The boundary is consistent across every conversation regardless of how the question is phrased.

Yes, based on data you provide. Add specialties, languages, and conditions treated as custom fields on each therapist profile, and SleekAI matches patients accordingly. A post-op knee patient routes to the post-op specialist, a vestibular patient routes to the vestibular specialist, a Spanish-speaking patient routes to the Spanish-speaking therapist. The match is conversational rather than form-based, which improves both fit and conversion.

Yes. SleekAI is multibot, so you can run a separate chat experience on the orthopaedic rehab section and a different one on the women's health section, each with its own tone, intake script, and therapist routing. The pelvic-floor bot has different sensitivities from the post-op-knee bot, and trying to fit them into one prompt usually produces a worse experience for both populations.

Yes, using the OpenAI Files vector DB integration. Upload protocol documents and the bot uses them as reference, while still refusing to give individualised treatment advice. The protocols inform the bot's general explanations of what an ACL or rotator cuff rehab program looks like in your clinic, but the actual prescription always comes from the licensed physio at the assessment, not from the chat.

Conversations are stored in your WordPress database. The model calls go to OpenAI or Anthropic using your own API key - SleekAI doesn't proxy them. This matters for HIPAA-style data handling because the conversation never passes through a third-party SleekAI server. You control retention through the plugin settings, and most clinics purge logs on a 30 or 60 day schedule and forward summaries to the EMR through a webhook.

Yes. The widget is fully customisable - colours, position, avatar, opening message, font - and you can override the CSS for tighter brand alignment. Most clinics restyle the widget to match the site header and footer, position it on the bottom right, and set an opening message that matches the practice tone. The customisation lives in the WordPress admin so you can iterate without touching theme code.

Yes. Pre-surgical or pre-hab patients have different intake needs from post-op patients: surgeon name, scheduled procedure date, current symptoms, and pre-hab goals. The bot can branch on a pre-hab page to capture those details and route to the therapist who runs your pre-hab program rather than the post-op specialist. This is increasingly common as pre-hab becomes a billable service alongside post-op rehab.

Both, when you have separate pages. Sports performance has different intake from rehab: sport, level, position, season timing, and performance goals. The bot can run a sports-performance intake on the sports page and a rehab intake on the rehab page, then route to the therapist whose specialty matches. Most clinics that offer both find that splitting them through multibot produces better conversion than trying to handle them in one bot.