No. SleekAI is configured to refuse any clinical recommendation. It will not tell a patient whether they need a hip replacement, whether anterior or posterior is right for them, or whether their imaging shows arthritis severe enough for surgery. Those decisions belong to the orthopaedic surgeon after an in-person examination. The bot redirects every clinical question to a consultation booking, and the boundary holds regardless of how the question is phrased or how many follow-ups the visitor sends.

Yes. Each procedure has a separate page with its own description, surgeon list, recovery timeline, and preparation requirements. The bot reads them as distinct sources, so a knee patient gets knee-specific answers and a shoulder patient gets shoulder-specific answers. Multibot also lets you scope a separate chat instance per procedure category if the volume and intake patterns differ enough to justify it.

Yes, through a link or JS API. The bot hands off to your existing scheduler (Calendly, Acuity, NextGen, athenahealth, or a custom widget) rather than maintaining a parallel calendar. Patients click through with intake details prefilled, which keeps a single source of truth in your scheduling system and avoids the race conditions that come from shadow booking tools.

The system prompt is configured to recognise urgency keywords (chest pain, sudden severe limb pain, signs of stroke, signs of infection after surgery like fever or wound drainage) and direct the patient to call their surgeon's after-hours line or 911. This is non-negotiable in the prompt and reviewed quarterly. We also recommend a visible disclaimer in the widget header so patients know the channel's scope upfront.

It can describe the general categories of implants your clinic uses (cemented, uncemented, robotic-assisted platforms by name) from your published procedure pages, but it will not recommend one over another for the specific patient. Implant choice depends on bone quality, activity level, age, and surgeon preference, and the decision belongs to the surgeon at the consultation, not the chat.

In your WordPress database under your control. Retention is configurable through the plugin. For US clinics handling PHI, you need a HIPAA-eligible OpenAI configuration, signed BAAs with every vendor in the stack, encryption at rest on the WordPress database, and proper access controls on who can read the logs. SleekAI provides the building blocks; the compliance posture is a stack-wide responsibility.

Yes. Revision joint replacement has different intake needs than primary replacement: prior surgeon, prior implant, year of original surgery, reason for revision (loosening, infection, instability, wear). The bot captures those details and routes to the surgeon on your team trained in revision work rather than a primary-replacement specialist. The routing logic comes from custom fields you set once on each surgeon profile.

Yes. The bot replies in the patient's language (Spanish, French, Arabic, Mandarin, German, and other common languages) and can quote international patient services if you have a page describing them. It will still refuse diagnosis and treatment recommendations across every language, and route every clinical question to a consultation. Many clinics find that the language coverage materially expands the international patient pipeline at no added staff cost.