Yes. If your residential services and prices live on WordPress pages, ACF fields, or a custom post type, SleekAI reads them at request time using its data-source wizard. Drain clearings, toilet rebuilds, disposal swaps, water heater replacements, and any dispatch-fee waiver logic all carry into chat. You don't need a separate pricing database, the bot quotes from whatever your site already shows visitors.

No. Bookings only land in windows your calendar shows as open. If two homeowners ask about a 1 PM slot at the same time, the second one gets the next genuinely available window. The bot does not invent slots and does not promise same-day when the board is full. Honest availability beats over-promising every time, because the customer who hears "tomorrow morning at 9" stays booked while a fake same-day promise gets canceled at 2 PM.

The system instruction lists the emergency signals: active leaks, no water, sewage backup, gas smell, burning smell. Those calls get routed to your emergency dispatch path with shut-off guidance given before the booking, not after. Routine calls like dripping faucets or slow drains stay in the normal calendar. You can customize the list per site, since some shops treat water heater leaks as emergencies and others handle them next-day.

Yes. SleekAI's multibot feature scopes each bot to its own menu, pricing, and dispatch logic. The service bot quotes flat-rate residential jobs; the new construction bot routes to a project intake flow with general contractor fields and rough-in scheduling. Each bot can be embedded on the right pages using display conditions like URL pattern or post category, so the homeowner and the GC never see each other's flow.

It depends on the CRM. SleekAI logs the full conversation, model name, token usage, and page URL into WordPress automatically. From there, plugins like WP Fusion, Zapier, or your CRM's own WordPress integration can forward the booking to ServiceTitan, Housecall Pro, Jobber, or your back-office tool. SleekAI doesn't ship a built-in connector for those, the routing happens via your existing CRM plugin or webhook.

The bot asks for age, fuel type, and current symptom before quoting. A 6-year-old tank leaking from a fitting is a repair; a 12-year-old tank pooling at the base is almost certainly a replacement. The instruction tells the model to frame replacement honestly when the math says so, rather than dispatching a $89 service call on a tank that's beyond economical repair.

No. Anonymous visitors can describe the issue, get a quote range, and book a window. The bot collects address, phone, and symptom log inline. Logged-in customers, if your site offers accounts, get a slightly richer experience because the bot can match them to existing service history and skip the address question. Both paths land in the same conversation log.

Your choice. SleekAI supports BYO API key for OpenAI, Anthropic, Google, and OpenRouter, so you can pick GPT-4.1, Claude Sonnet, Gemini, or anything OpenRouter exposes. Most plumbing shops settle on a mid-tier model because the conversations are short and price-sensitive. The same instruction works across providers, so switching is a config change, not a rewrite.