No. SleekAI is configured with explicit refusal language for every diagnostic, treatment, dosage, and symptom-interpretation question. The instruction includes a hard refusal: never diagnose, never recommend specific treatments. For urgent gynecologic concerns (heavy bleeding, severe pelvic pain, signs of ectopic pregnancy, fever after a procedure), the bot routes immediately to call 911 or the local emergency number. The clinical conversation always stays with the clinician at an in-person or telemedicine visit.

The system prompt is configured to avoid assumption-laden prompts (no 'are you trying to conceive', no 'are you sexually active') unless the patient brings the topic up themselves. Replies are warm and operational without being intrusive. The widget can include a privacy disclaimer at the top so patients know what's logged. Sensitive clinical detail is never invited into the chat, and the bot is configured to redirect such detail to the visit.

Yes. The bot reads each provider's profile including gender if you publish it, and routes patients accordingly when they ask. This is one of the most common preferences in gynecology practice and a chatbot that handles it correctly improves first-visit satisfaction. For practices where all providers are female (or all male), the bot is configured to acknowledge the question and confirm the practice's provider composition rather than ignore it.

The system prompt recognises gynecology-specific urgency keywords (heavy bleeding, severe pelvic pain, signs of ectopic pregnancy, post-procedure fever or severe pain, signs of sepsis) and immediately routes the patient to call 911 or the local emergency number, plus the practice's after-hours line if you provide one. This routing is non-negotiable in the configuration. A visible disclaimer in the widget header reinforces the channel's scope upfront.

Yes, for practices that handle both. The bot is configured to recognise pregnancy-related signals (last menstrual period dates, prenatal care, post-partum follow-up) and route them to the obstetric calendar rather than the gynecology one. For gynecology-only practices, pregnancy-related questions are routed to a confirmation conversation and, if needed, a referral to a partner OB practice. Mis-routing between OB and gynecology is one of the bigger sources of patient confusion, and the chatbot can clean it up.

Yes, and discretion matters more here than in most specialties. Retention is configurable per channel. For gynecology we recommend short retention windows (days, not years), encryption at rest on the WordPress database, role-restricted access on logs, and a clear note in the widget about what's logged. The system prompt is configured to avoid inviting clinical detail into chat, so the log contains operational text rather than sensitive clinical content.

Yes. Patients writing in any common language get responses in their language, with operational details translated cleanly and the clinical-refusal language translated faithfully. For diverse catchments this is genuinely useful, especially for patients who would not call the front desk in their second language to ask about a well-woman visit. The multilingual front door raises access without compromising the safety boundary.

HIPAA compliance is a stack question, not a single-plugin question. SleekAI runs on your WordPress install with an API key you provide. For US gynecology practices handling PHI, you need a HIPAA-eligible API vendor configuration, a BAA in place with that vendor, encryption at rest on the WordPress database, role-based access on conversation logs, and the chat channel documented in your Notice of Privacy Practices. The plugin is the building blocks, the compliance posture is wider.