No. SleekAI is configured to refuse diagnosis and refer every clinical question to the licensed urgent care physician at the visit. The system prompt enforces this on every conversation, even when the patient describes symptoms in detail. The bot's role is to share what services are available, quote wait time and insurance, route emergencies to 911, and book the visit, not to assess what is going on. This is the only safe configuration for an urgent care site given the liability around symptom assessment from a chat window.

The system prompt lists explicit emergency signals, chest pain, stroke signs (sudden weakness, speech problems, facial droop), severe bleeding, head injury, trouble breathing, suicidal thoughts, and instructs the bot to direct the visitor to call 911 or go to the nearest emergency department immediately. The bot does not invent crisis hotline numbers or try to triage further. For mental health crises specifically you can also include the 988 Suicide and Crisis Lifeline as a US-specific resource.

Yes, if your wait time lives somewhere SleekAI can read. Most clinics maintain it as a custom field a manager updates, a JSON endpoint exposed by the queue system, or a transient updated by a cron job. Point the data-source wizard at it and the bot quotes the same number the lobby screen shows. When the queue is closed or the clinic is at capacity, the bot says so plainly.

Yes. Store the in-network plan list per location as ACF fields or a custom post type and the bot reads them into the prompt. Different locations may be in different networks and the bot quotes per location instead of clumping the chain together. 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 urgent care clinics show the bot on services, billing, and locations, 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, DocResponse, or Experity directly. It captures the booking intent, location, symptoms in general terms, insurance carrier, and contact details, 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.

Yes. Every conversation is stored in the WordPress database with retention you control. SleekAI does not proxy model calls, so the conversation passes through your own OpenAI, Anthropic, Google, or OpenRouter account. Most urgent care clinics keep a 30 to 60 day window and review the log during the daily huddle to spot recurring confusion (insurance, hours, wait time) 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 urgent care site the monthly model cost is usually $10 to $40 in actual API usage. Pick a fast model (GPT-4o-mini or Claude Haiku) for short triage chats and switch up for longer questions.