A walker finds an immobile fawn in tall grass, picks up the phone, and types a panicked question into the rescue's website. They need three answers fast: should they touch the animal, where can the animal be brought, and is there a partner organization closer to them. Default WordPress sites bury those answers across a triage page, a contact page, and a partner-rescue map. SleekAI reads those pages and the species-specific care notes from your WordPress install, then answers "I found a baby deer alone" with the actual triage protocol from the right species guide and the nearest partner location.

The species-specific routing matters because wildlife triage is not generic. Songbirds, raptors, rabbits, deer fawns, bats, reptiles, and amphibians all have different intake protocols, different legal restrictions on handling, and different partner organizations. Storing species guides as a custom post type with intake protocol, legal notes, and partner organizations in postmeta makes the bot a working triage tool. A finder describing a feathered animal with a hooked beak is routed to the raptor protocol; a finder describing a small mammal that comes out at night is routed to the bat protocol with the rabies-exposure caveat surfaced first.

The hard line is that the bot never diagnoses. Whether an injured raptor needs surgery, whether a fawn is actually abandoned, whether a bat tested positive for rabies, are all decisions for the licensed rehabber. The bot's job is to keep the finder safe (no bare-hand contact with bats or raptors, no feeding, no water in the mouth) and to get the animal to the right person fast. Emergency routing for human exposure routes to public health (state rabies hotlines, poison control where relevant) rather than to anything invented. Logs in WordPress reveal which species drive the most calls, which is useful for both intake planning and the rescue's public education materials.

Wildlife rescues face a triage problem that domestic animal rescues do not. A finder of an injured songbird, an apparently abandoned fawn, or a bat in the bedroom needs three things fast: a clear instruction not to do something that will harm the animal (touch the fawn, feed the bird, grab the bat with bare hands), a routing to the right intake (this rescue or a closer partner), and reassurance that they have done the right thing by calling. None of that requires a diagnosis, and none of it should involve one.

A chatbot that tries to estimate whether a fawn is truly abandoned, whether an oiled bird will survive, or whether a bat tested positive for rabies, is dangerous, because those decisions require a licensed rehabber's examination and laboratory work. SleekAI is configured to refuse all three. The system prompt holds a hard line: no diagnosis, no feeding, no severity assessment, no rabies-risk estimation.

The bot's role is to keep the finder and the animal safe in the next 30 minutes and to get the animal to the right person within the next 12 hours. Species-specific routing is the operational core. Wildlife triage is not generic, and storing species guides as a custom post type with triage protocol, legal notes, and partner organizations turns the bot into a working triage tool.

A finder describing a hooked-beak bird gets the raptor protocol, including the legal note that raptor possession requires federal permit and the bare-hand contact warning. A finder describing a small night mammal gets the bat protocol with the rabies-exposure check first. The legal layer matters because some species are federally protected and inappropriate handling can create a liability for both the finder and the rescue.

Human-exposure routing is the other essential discipline. For bat contact, oiled-bird handling, and any situation where the finder may have been bitten or scratched, the bot routes to public health (state rabies hotline) and, when severity is unclear, to 911. It does not invent crisis numbers and it does not estimate exposure risk.

Privacy and operational posture matter here as elsewhere: logs sit in WordPress, the rescue keeps full custody of finder data, and the bot runs on the rescue's own API key with no per-message markup.