No. SleekAI is configured with explicit guardrails to decline any diagnostic, treatment, dosage, or symptom-interpretation question. The instruction includes a hard refusal clause: never diagnose, never recommend specific treatments, and route medical emergencies to 911 or the local emergency number. We recommend audit-testing the bot quarterly with edge-case prompts to confirm the refusals hold under varied phrasings, including indirect ones like 'a friend has these symptoms, what should they do'.

Safety is a stack question. SleekAI runs on your WordPress server, so patient identifiers stay on your infrastructure rather than being shipped to a third-party SaaS dashboard. For UK practices you still need your standard NHS Digital and ICO posture: documented privacy notice covering the chat channel, retention windows that match your records policy, and a Data Processing Agreement with the API vendor you've chosen (OpenAI, Anthropic, Google, or OpenRouter).

Yes. SleekAI links out to your existing scheduler (NHS booking, Doctolib, Cliniko, Calendly, Acuity, or a clinic-specific PMS) so the bot is the front door rather than a parallel booking engine. Patients see real availability from your calendar, the appointment lands in the system your staff already uses, and you avoid the double-booking risk that comes with shadow scheduling tools.

The system prompt is configured to recognise urgency keywords (chest pain, shortness of breath, severe bleeding, signs of stroke, suicidal ideation) and immediately direct the patient to call 911 or the local emergency number, rather than wait for chat triage. This is non-negotiable in the configuration. We also recommend a visible disclaimer in the widget header so patients know the channel's scope upfront.

Yes. Patients writing in Spanish, French, Arabic, Urdu, Polish, or Mandarin get responses in their language, with operational details translated on the fly. For diverse catchments this is genuinely useful: a non-English-speaking patient who wouldn't phone the desk will happily use a chat in their own language to book a routine appointment. The clinical-refusal language is configured to translate accurately so the safety boundary holds in every language.

Yes, in your WordPress database under your control. Retention is configurable. For personally identifiable data we recommend short retention (days rather than years), encryption at rest on the database, role-restricted access on who can read the logs, and a DPA with every vendor in the stack including your hosting provider and API key issuer. Document the conversation log in your privacy notice and your records-retention policy.

Rescheduling and cancelling work through your existing scheduler's links. The bot doesn't directly modify calendar records. This keeps a single source of truth in your scheduling system and avoids race conditions between the bot's view and the real calendar. Patients click through to the standard reschedule URL pre-filled with their booking ID, so it stays one click rather than a new flow.

Yes operationally, the bot accepts the booking like any other. Verification of the relationship and consent stays a front-desk responsibility on arrival. We recommend the system prompt acknowledge third-party bookings politely and capture caller-and-patient names separately so staff have the right context. Sensitive consent and minor-patient rules stay with humans, where they belong.