No. Varicose veins, spider veins, venous insufficiency, and DVT are clinician diagnoses based on history, exam, and ultrasound. The bot describes what each consultation involves and refuses to estimate diagnosis from text. The refusal is enforced in the system prompt and tested before launch with a standard set of diagnosis-bait prompts. For red-flag symptoms the bot routes to 911 or the nearest ER.

Sudden unilateral calf swelling, calf pain that worsens with walking, shortness of breath, chest pain, or any sign that could be a DVT or PE triggers an immediate routing to 911 or the nearest emergency room. The bot does not estimate likelihood, does not ask follow-up questions to triage severity, and does not delay the escalation with chat. The behavior is the first thing tested before go-live.

Yes, in plain prose from your published policy. Medical vein treatment (typically endovenous ablation for symptomatic venous reflux) is usually covered with documentation of reflux on ultrasound and a trial of conservative therapy like compression stockings, per most major insurers. Cosmetic sclerotherapy for spider veins is typically not covered. The bot explains your policy and routes verifications to the billing team.

It describes what each procedure involves at a high level (length, what to expect, recovery basics) from your published patient guides. It does not describe technique-level details, choose between modalities for a specific patient, or compare your clinic's outcomes to other clinics. Detailed clinical discussion belongs to the consultation, where the clinician has the ultrasound and the patient's full history.

Yes. Ultrasound mapping (typically 30 to 45 minutes per leg) is booked with the imaging team. The bot captures contact details, the referring clinician if applicable, and any prep details from your published guide. Bookings funnel into the same scheduler the imaging team uses, so there is one source of truth for the calendar.

Pregnancy and postpartum involve specific considerations for vein evaluation and treatment timing. The bot acknowledges that, refuses to recommend treatment timing or specific approaches, and routes the patient to a consultation where the clinician can have that conversation with the full clinical context. Pregnancy-related red-flag symptoms (sudden leg swelling, shortness of breath) still escalate to 911.

HIPAA compatibility is a stack decision, not a plugin feature. SleekAI uses your own API key (OpenAI, Anthropic, Google, or OpenRouter). For US clinics handling PHI, a HIPAA-eligible OpenAI configuration with a signed BAA, encryption at rest on the WordPress database, role-based access on logs, and BAAs with all relevant vendors are required. The plugin gives you the building blocks; the compliance posture is your assembly.

Yes. SleekAI is multibot. Configure a cosmetic-focused bot with its own tone and pricing language for spider-vein sclerotherapy and a medical-focused bot with insurance-prerequisite language for ablation. Display conditions pin each to the right page. Both bots share the same hard escalation on red-flag symptoms and the same refusal on diagnosis.