No. SleekAI is configured with strict guardrails to decline diagnostic, treatment, and dosage questions and refer the patient to a qualified dentist or, in urgent cases, emergency services. The system prompt enumerates the declined topics explicitly and provides standard refusal language. Audit-test the bot quarterly with edge-case prompts ('is it a cavity?', 'should I take ibuprofen?') to confirm the guardrails hold under varied phrasings.

Compliance is a stack question, not a single-plugin question. SleekAI runs on your WordPress site, so data residency is yours - which is the foundation for both HIPAA and GDPR. For HIPAA in the US you need a HIPAA-eligible OpenAI configuration, BAAs across the stack including hosting, and proper access controls. For GDPR in the EU your DPA setup applies, retention windows match your data-policy, and the bot is documented in your privacy notice.

It links to your existing system or captures details for manual front-desk booking. Most clinics use it as the first-line filter rather than a replacement scheduler - the booking system stays the single source of truth on calendars, the bot funnels routine intent into it. For practices with custom PMS, the standard pattern is to deep-link with prefilled query params; the bot doesn't need to write directly to the calendar.

It can list which insurers you're contracted with, plus general notes - 'preventive care typically covered fully, cosmetic treatments out of pocket'. Specific coverage decisions still need confirmation with the insurer or your front-desk team because plan tiers vary. Keep the bot's posture conservative on coverage - it's better to defer than to quote a number that turns out to be the wrong plan tier.

Yes - patients writing in any common language get answers in their language. Useful for diverse neighbourhoods - a Berlin practice routinely sees logs in five or six languages within the first weeks. Service prices and operational details translate cleanly; clinical-deferral language remains as configured to ensure the safety guardrails hold across translation.

Yes, in your WordPress database. You control retention. For PHI/personal data we recommend short retention windows - days rather than years - encryption at rest on the WordPress database, and role-restricted access on who can read logs. Document the conversation log in your privacy notice and your records-retention policy. Build the conversation export into your data-subject-access workflow if GDPR applies.

For published rate-card services - cleaning, whitening, single-tooth fillings - yes. For complex treatment plans - implants, multi-quadrant work, ortho courses - the bot defers to a consultation because real estimates depend on imaging, exam findings, and treatment-plan complexity. This split keeps the routine value without making the bot guess at numbers that materially affect a patient's financial decision.

Configure the bot to recognise urgency keywords - severe pain, swelling, fever, knocked-out tooth - and immediately direct the patient to the nearest emergency dental service or hospital A&E rather than queue them for the next-day slot. Most practices include their emergency-line number or partner-clinic referral in the system prompt for after-hours routing. This is non-negotiable in the configuration we recommend.