No. SleekAI is configured with explicit refusal language for every diagnostic, treatment, dosage, and symptom-interpretation question, including paediatric ones. The instruction includes a hard refusal clause: never diagnose, never recommend specific treatments, route medical emergencies to 911. If a parent describes symptoms, the bot offers to book a sick-visit or, for urgency keywords like high fever in an infant under three months or signs of breathing difficulty, routes them to call 911 immediately. Audit the bot quarterly with paediatric edge cases.

Yes, as published information. It can quote your clinic's adopted CDC or WHO-aligned immunisation schedule, list which vaccines are typically given at each well-child visit, and link to your published vaccine information sheets. It does not authorise or skip vaccines, and it firmly defers any 'should my child get this vaccine' clinical question to a conversation with the physician. The schedule is data, the recommendation is clinical.

Yes, if your scheduler supports it. SleekAI reads your scheduler's appointment types and constraints, so if your practice runs same-visit family scheduling (parent and one or two children in adjacent slots with the same physician), the bot can offer that pattern when families ask. For practices that prefer separate visits per family member, the bot defaults to standard sequential booking instead.

The system prompt is configured to recognise paediatric urgency keywords with extra sensitivity (high fever in infants under three months, breathing difficulty, signs of dehydration, lethargy, seizure, head injury) and immediately direct caregivers to call 911 or the local emergency number. This routing is non-negotiable in the configuration and tested as part of the standard setup. A visible disclaimer in the widget header reinforces the scope.

Yes, and this is one of the strongest fits for family medicine specifically. Many practices serve linguistically diverse catchments where the front desk can't staff every language. SleekAI replies in whatever language a parent writes in, with operational details translated cleanly and the clinical-refusal language translated faithfully so the safety boundary holds across Spanish, Vietnamese, Tagalog, Mandarin, Arabic, or any common language.

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 family medicine 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, and role-based access on conversation logs. The plugin provides the building blocks, the compliance posture is wider than the bot.

Yes, in your WordPress database. Retention is configurable. For PHI we recommend short retention windows (days, not years), encryption at rest, role-restricted log access, and a documented BAA with every vendor in the stack. The conversation log can be part of your data-subject-access workflow if any state-level privacy laws apply. Document the chat channel in your Notice of Privacy Practices.

The bot accepts bookings the same way it accepts any other intake, and captures both the patient's name and the booking party's name separately when relevant. Consent rules for minor patients (eligibility for confidential care, parental consent requirements that vary by state and topic) stay with the front desk and clinicians on arrival. The bot is configured to never engage on confidential adolescent-care topics directly, and to route those conversations to a human clinician.