Yes. The system prompt scopes commercial voltage class first: 120/208V single-phase, 277/480V three-phase, or higher service. That distinction drives the right scope questions (which panel, which suite, what the building's service is rated at), the right rate tier (commercial vs residential), and the right tech assignment. Most commercial shops staff differently for high-voltage work, and the bot routes to the right side of the bench.

Yes. When a property manager or landlord asks for a Certificate of Insurance, the bot confirms your standard limits ($2M general liability, $5M umbrella typical for commercial work), confirms whether you support additional-insured language for landlords and property managers, and frames the lead time for issuance. The actual COI is still cut by your insurance agent, but the bot removes the back-and-forth that usually happens before the dispatch.

Yes, but as a separate flow. Tenant build-outs are project work, not service work, and they involve rough-in scheduling, permit coordination, and inspection windows. The bot routes those inquiries to the project manager queue with square footage, tenant name, lease details if available, and the GC's contact info. The PM handles the rest, the bot just makes sure the right intake fields land in the right inbox.

Yes. The bot collects property name, billing contact, PO contact, and COI request to set up a new master account. If the inquiry is from an existing account, the bot matches the contact or property name against the customer database (via WP postmeta or a custom table) and confirms the account is on file. New accounts get same-day setup mentioned, so the dispatch isn't held up by paperwork.

Yes. Fire alarm circuits, emergency lighting, and elevator power get scoped on their own intake path with the right code references (NFPA 72, NFPA 110, local AHJ requirements). The bot is explicit that life-safety work requires the right license certifications and inspection sign-offs, and routes to the appropriate PM rather than dispatching it as a routine service call.

Data center and retail after-hours work has its own SLA tier because the downtime cost is high. The bot reads your after-hours commercial rate (typically $325 to $425 per hour with a 2-hour minimum) and the agreed-upon SLA response time (2-hour, 4-hour, or next-day) and routes the dispatch accordingly. Conversation logs tag the SLA tier so accounting can bill it correctly later.

Yes. Multibot lets each bot scope to its own master electrician license number, jurisdiction-specific permit fees, and applicable inspection rules. A contractor licensed in three states keeps each bot scoped to the right license, the right code edition, and the right typical inspection lead time. Customers see the right specifics for their location, not a generic catch-all.

SleekAI supports OpenAI, Anthropic, Google, and OpenRouter, so you bring your own key. Commercial conversations tend to be longer and reference more context (property records, SLAs, PO history, license info), so most commercial shops pick a higher-context model like GPT-4.1 or Claude Sonnet. Latency matters less than reasoning depth here, since facility managers expect a thoughtful response more than an instant one.