No. SleekAI is configured to refuse interpretation of any diagnostic result. Even at specialty level the boundary holds: the specialist interprets the report at the consult, with the patient present and the full clinical picture available. The bot books the consult, captures the report status (pending, available, faxed to clinic), and prompts the owner to bring or transmit the report before the visit. Interpretation from chat would undermine the entire reason for specialty referral.

Yes. Each specialty service has its own page with its own intake schema in ACF, and the bot branches its questions per service. Oncology captures tumour location, biopsy status, staging, prior treatment. Cardiology captures murmur grade, ECG history, current cardiac meds. Neurology captures seizure history, neurolocalisation, prior MRI. Internal medicine captures GI, urinary, or endocrine history depending on the presenting workup. Dermatology and surgery have their own schemas.

If you store referring practices as a custom post type or taxonomy, the bot can recognise them and pull their referral preferences (fax versus secure email, preferred imaging format, preferred report turnaround). Most specialty practices maintain a referring-vet directory in WordPress for exactly this kind of operational context, and the bot reads from it conversationally during intake. New referring practices get added through the regular WordPress flow.

Yes. SleekAI reads service descriptions from your WordPress posts and ACF fields. Oncology chemotherapy protocols, cardiology echocardiogram and Holter monitor procedures, neurology MRI under anaesthesia, internal medicine endoscopy and ultrasound, dermatology intradermal allergy testing, surgical orthopaedic and soft-tissue procedures all live as service posts the bot can describe from your published copy. Quotes match your real numbers because the bot reads them in real time.

Specialty practices generally do not run after-hours, so acute deterioration routes to your local emergency hospital partner. The bot surfaces the ER partner's address, phone, and 24-hour status immediately whenever deterioration keywords appear (breathing distress, prolonged seizure, collapse, severe pain, bleeding). It also surfaces ASPCA Animal Poison Control (888-426-4435) for any toxin exposure. The bot does not estimate severity, it just routes to the right facility fast.

Yes, when each specialist has their own calendar exposed through the JS API. The bot identifies the specialty service from the page or the conversation, checks the right specialist's availability, and books the consult on their calendar specifically. Multi-specialist practices typically have oncologist, cardiologist, neurologist, internist, dermatologist, and surgeon on separate calendars, and the bot respects that routing rather than booking onto a generic slot.

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 a multi-specialty practice the monthly model cost is usually $15 to $50 in actual API usage. GPT-4o or Claude Sonnet are good picks for specialty intake because the prompt context is larger (referral context, specialty-specific fields, procedure descriptions) and benefits from the higher-capacity models.

Yes, with adjusted intake. Emergency and critical care specialists run a different intake from elective specialty consults because most ECC cases arrive through transfer from primary or ER rather than scheduled appointments. The bot can capture transferring clinic, presenting complaint in general terms, current stabilisation status from the transferring team, and arrival ETA, then post to the ICU triage screen. ECC-specific deterioration routing surfaces the closest fully-staffed ER if the specialty practice is full.