Yes, from your published price tiers and add-on schedule. Standard fee, square-foot brackets, age surcharges, crawlspace and detached-structure adders, and add-ons like radon, mold, sewer scope, pool, septic, and water testing all read directly from the service posts. Confidential agent-network pricing stays in private fields the bot does not surface, so volume agreements do not leak to retail visitors.

Yes. SleekAI hands off via webhook to anything that accepts JSON. Most inspectors use ISN, HomeGauge, Spectora, or InspectorPro for scheduling, all of which accept structured intake. The webhook payload includes property address, square footage, age, contingency deadline, add-ons, and the transcript, so the receiving system creates the booking with the data already populated rather than requiring re-entry.

The bot detects when the visitor identifies as a real-estate agent and switches to an agent-flow. The agent flow captures the agent's firm and contact details, buyer-client contact, property address, contingency deadline, and specific inspection concerns the agent wants flagged (older roof, recent renovations, water in basement). The inspector receives a high-priority notification on agent-referred bookings because timing usually matters more on agent-driven inspections.

If you publish commercial inspection services as a separate post, the bot reads them and routes commercial enquiries accordingly. Commercial work typically requires a custom quote rather than tier pricing, so the bot collects building size, type (office, retail, industrial), age, and intended use, then routes to the commercial inspector for a custom proposal rather than quoting from a residential schedule.

Yes, as add-on services or standalone services depending on how you structure them. The bot reads each add-on's price, timing constraint (radon needs 48 hours, septic dye test needs water access), and certifications required (well water lab testing typically routes to a certified lab partner). For inspections requiring third-party labs, the bot quotes turnaround based on the lab's published time, not the inspector's report time.

Yes. Multibot scopes each chatbot to an inspector, a service area, or a property type. A firm running three inspectors across a metro can have each inspector's calendar loaded into their own bot, with display conditions on the booking widget showing the right bot based on the visitor's location or URL. Reporting in WordPress tracks bookings per inspector for commission and capacity planning.

The bot detects the visitor's role (buyer, agent, seller) and switches between pre-purchase and pre-listing flows. Pre-purchase is timed to contingency deadlines; pre-listing is timed to listing date. Pre-listing inspections often include a different report format (minor repair list versus full disclosure-grade report), which the bot quotes accordingly from your service tier descriptions.

Stored in WordPress with property address, booking ID, agent details, and visitor metadata attached for inspector review. SleekAI uses your own OpenAI, Anthropic, Google, or OpenRouter API key, and standard API terms exclude conversation data from model training. For inspectors handling sensitive transaction details and buyer financial position information, this keeps client data inside your account rather than a third-party SaaS database.