No, and that is the point. Severity assessment requires examination, imaging, and bloodwork. A chatbot estimate based on a few sentences is wrong often enough to be dangerous. The bot is configured to refuse triage and to tell every owner the same thing: come now, the team will assess on arrival. For toxin exposures it also surfaces ASPCA Animal Poison Control (888-426-4435) because that line can start dose-based guidance while the owner drives, but it never estimates dose or risk itself.

Yes, if your triage queue exposes a wait estimate through an API. The JS API hook in SleekAI lets the bot call your queue endpoint and quote the current wait by acuity level. Without an API hook the bot quotes the general pattern (busiest on weekend evenings, slowest on weekday mornings) from custom fields you maintain. Owners value an accurate number more than a generic answer, so the API integration is worth wiring.

Pet name, species, breed, age, weight, presenting complaint in general terms, ETA, owner name, and contact phone. Plus relevant toxin specifics (substance, quantity, time of ingestion) if it's a toxin case. The capture happens conversationally during the drive, and the structured intake hits your triage screen before the owner walks in. The team is ready with the right doctor, the right stall, and the right gear, which is the whole operational point.

Yes, for every toxin exposure. The number (888-426-4435) is hard-referenced in the system prompt and surfaces immediately whenever toxin keywords appear (chocolate, xylitol, grapes, raisins, lily, onion, garlic, ibuprofen, acetaminophen, antifreeze, rodenticide, marijuana). ASPCA Poison Control can start dose-based guidance while the owner drives, which materially changes care plans. The bot does not estimate dose itself, it just refers and routes the owner to the ER simultaneously.

Yes. With 28+ display conditions including URL pattern, post type, and page template, you can hide the chatbot on memorial pages, the careers page, and any other page where it would be tonally wrong. Most emergency clinics show the bot on the home page, services pages, insurance page, and the ICU page, and hide it on memorial, careers, about, and team bio pages where it adds nothing and intrudes.

From your published service pages. The bot can confirm pet insurance accepted (Trupanion, Embrace, Healthy Paws, Nationwide), explain that emergency clinics generally do not bill insurance directly but provide itemised receipts, and quote estimated emergency exam, imaging, hospitalisation, and surgical deposit ranges from your pricing pages. It can describe CareCredit terms and the general deposit policy for surgical admits. Specific case quotes go to the doctor.

Yours. SleekAI is BYO API key. Bring your own OpenAI, Anthropic, Google, or OpenRouter key, and the model bills you directly. No per-message markup. For an emergency clinic the monthly model cost is usually $20 to $80 in actual API usage because emergency chat volume is higher than wellness clinic chat. GPT-4o-mini handles most intake well, GPT-4o or Claude Sonnet for higher reliability on the refusal boundary and tone.

Yes, through the JS API. The bot can hand off to a live triage tech when the conversation crosses a threshold (severe trauma, breathing distress, owner in distress, more than 5 messages without resolution). The handoff posts the captured intake to your tech queue so the human picks up with context rather than starting cold. Most emergency clinics keep the bot for after-hours intake and route to humans during peak triage shifts when the staffing supports it.