No. SleekAI is configured to refuse evaluation of skin findings. Every dermatologic question routes to an in-person exam with a clinician, regardless of how the question is phrased or whether a photo is attached. The boundary is consistent across every conversation, and it is the only safe configuration for a dermatology practice given the liability around lesion assessment from chat. The bot does help with everything else: procedures, pricing, prep, scheduling.

Yes. SleekAI reads pricing from your WordPress posts and custom fields, so the chatbot quotes your published numbers - per syringe for Botox or Dysport, per area for filler, per session for laser, per square centimetre for cryosurgery. Update the price on the page and every conversation reflects the new number. The bot also distinguishes new patient versus established patient pricing where you have a tiered structure.

Yes. Tag each procedure with its prep instructions in custom fields, and the chatbot delivers them automatically when that procedure is discussed or when a booking for it is confirmed. Common prep items include no nail polish for skin checks, no moisturiser the morning of, retinoid pause two weeks before laser, sun avoidance before chemical peel, and antibiotic prophylaxis for some Mohs patients with cardiac history.

Yes, in your WordPress database. You decide retention through the plugin, typically 30 days for medical practices. Calls to the model use your own OpenAI or Anthropic API key. SleekAI does not proxy them, so the conversation does not pass through any third-party server beyond the model provider itself. Most practices forward conversation summaries to their EMR through a webhook and purge raw logs on a strict schedule.

Yes. SleekAI is multibot, so the medical and aesthetic sections can have separate chat experiences with different system prompts. Aesthetic intake is different from medical intake: the tone is more concierge, the pricing is per service rather than insurance-billed, and the prep instructions are different. Running them as separate bots through multibot keeps each experience appropriate to the patient population it serves.

Yes. With 28+ display conditions, you can show the chatbot only on relevant service pages and hide it on legal, careers, or research pages. The conditions cover URL, post type, page template, user role, device, and time of day. Most dermatology practices show the bot on services and aesthetics pages and hide it on the about page (where the visitor is researching, not booking) and the careers page (where it is irrelevant).

Yes, when you have a Mohs page. Mohs scheduling has different intake from a routine skin check: the patient usually has a confirmed biopsy diagnosis, the surgery is half-day, the prep is more involved, and the post-op care is significant. The bot can branch on the Mohs page to capture biopsy report status, anticoagulant medications, and transportation arrangements, then route to the Mohs surgeon's calendar specifically rather than the general dermatology calendar.

Yes, when you offer teledermatology. The bot can capture the basic information (location, insurance, primary concern in general terms), route to the asynchronous teledermatology platform you use, and explain what kinds of cases are appropriate for teledermatology versus in-person. The boundary on diagnosis still holds: even teledermatology requires clinician review of dermoscopic images, not chatbot assessment, so the bot's role is intake and routing only.