Yes, with the right system prompt. The bot does not replace the on-call tech, it triages the call and routes to dispatch. For active flooding, the bot's first job is to walk the caller through main shutoff, which a human dispatcher would do anyway and which an answering service typically skips entirely. For gas smells or fire, the bot routes immediately to the gas utility emergency line or 911 and does not try to dispatch its own truck. The instruction enforces those rules consistently.

Gas smell is the one symptom where the bot does not try to dispatch. The system instruction routes any "I smell gas" message to the local gas utility emergency line or 911, with the explicit advice to leave the building and call from outside. The bot does not invent a hotline number, it tells the caller to use the number on the back of their utility bill or to dial 911. That is the only safe path for that call.

Sewage backups in occupied homes get prioritized with health-and-safety prep before booking. The bot tells the caller to keep people and pets out of the affected area, turn off the water to stop the source, and avoid running anything else that drains. It quotes the after-hours sewer line clearing rate and routes to the on-call tech with the symptom log filled in, including line size and access location if the caller knows them.

Yes, the system prompt lists the emergency signals: active leaks, no water, gas smell, sewage backup, burst pipe, ceiling drip from a unit above. Anything else (slow drain, dripping faucet, intermittent low pressure) gets framed as a next-business-day call so the homeowner does not pay an emergency surcharge for a non-emergency. That honest framing is how you build trust with overnight callers.

The bot quotes whatever ETA your on-call rotation actually supports. Most emergency shops promise 45 to 90 minutes overnight, and the bot quotes the real range, not a marketing number. If the on-call tech is already on a call, the bot says so and offers the next available window honestly. Honest ETAs win retention because the homeowner who hears "75 minutes" stays on the hook while the one promised "30" cancels at 35.

The chat itself requires the customer to be online, but the bot does not depend on local-only data. If the homeowner is on a mobile network because the power and Wi-Fi are out, the chat still works as long as they can load the site. For truly offline cases, the system prompt directs the caller to a phone number for dispatch, which the bot reads from the site's contact info.

No. The instruction explicitly tells the model to quote real ETAs and real prices, even when the news is bad. If the on-call rotation is overloaded, the bot says "earliest we can be there is 90 minutes" instead of "someone will reach out shortly." Honest framing is the entire point. The customer who books at an honest 90 minutes is happier than the one who feels deceived at 60.

SleekAI supports OpenAI, Anthropic, Google, and OpenRouter, so you bring your own key. For emergency dispatch, latency matters more than long context, since most calls are 4 to 6 exchanges. A fast mid-tier model like GPT-4.1 or Claude Sonnet is the typical pick. The same instruction works across providers, so you can A/B test which one your customers prefer on a Sunday at 3 AM.