No. SleekAI is configured to refuse diagnosis and refuse to assess severity. Every clinical question is answered the same way: that is a call for the licensed physician at the visit. This is enforced in the system prompt and tested before launch. Even when the patient describes symptoms in detail or asks for an OTC recommendation, the bot redirects rather than guessing. This is the only safe configuration for a walk-in clinic given the liability around remote symptom assessment.

The system prompt lists explicit emergency signals, chest pain, stroke signs, severe bleeding, head injury, trouble breathing, suicidal thoughts, and instructs the bot to direct the visitor to call 911 or go to the nearest ER immediately. The bot does not invent crisis numbers or attempt further triage. For mental health crises in the US you can also include 988 Suicide and Crisis Lifeline as a published resource.

Yes, when the wait time exists somewhere SleekAI can read. Most clinics maintain it as a custom field a manager updates, a transient set by a queue system, or a JSON endpoint exposed by the lobby screen. Point the data-source wizard at the source and the bot quotes the same number visitors see in person. When the queue is closed the bot says so cleanly rather than inviting a wasted drive.

Yes. Store the in-network plan list per location as ACF fields or a custom post type and the bot reads them per page. Different locations of the same brand may be in different networks and the bot answers accurately. Verification at the visit is still required because real coverage depends on plan tier, deductibles, and benefit year.

Yes. SleekAI ships with 28+ display conditions covering URL, post type, page template, user role, device, time of day, and visitor status. Most walk-in clinics show the bot on services, locations, and billing, and hide it on careers, the HIPAA notice, and the privacy policy. The conditions are clickable rules so you do not need to maintain a code list.

Indirectly. SleekAI does not write into Solv, eClinicalWorks, or Experity directly. It captures the booking intent, location, contact details, and insurance carrier, then emails or webhooks the structured handoff to the front desk. The team confirms in the scheduling system the same way they would for a phone call. The handoff cuts down on duplicate entry and missed callbacks.

Yes, in your own WordPress database with retention you control. SleekAI does not proxy model calls, so conversation content passes through only your OpenAI, Anthropic, Google, or OpenRouter account. Most walk-in clinics keep a 30 to 60 day window and review the log during the daily huddle to spot recurring questions and refine the prompt.

Your own. SleekAI is BYO API key. Bring an OpenAI, Anthropic, Google, or OpenRouter key and the model bills you directly. There is no markup or per-message fee from Sleek. For a single-location walk-in site the monthly model cost is usually $10 to $35 in actual API usage. Pick a fast cheap model (GPT-4o-mini or Claude Haiku) for short triage chats.