Yes. The bot captures the requested effective date (divorce date of separation, date of death for estate, hearing date for tax appeal) and quotes the retrospective surcharge accordingly. Retrospective appraisals need historical comparable sales research, which adds time and fee; the bot quotes both transparently. For effective dates more than 5 years back, the bot routes to the appraiser for confirmation since historical data availability varies.

Yes. If the visitor mentions a lender, mortgage broker, or AMC, the bot detects the AMC workflow and redirects to standard ordering channels (AppraisalPort, Mercury Network, REVAA) rather than trying to take the order directly. This preserves the appraiser's panel relationships and avoids the conflict of bypassing lender-required AMC review. Private appraisal orders, where the appraiser sets the fee directly, get booked through the chat.

At the general level, yes. The bot can describe what USPAP requires (Uniform Standards of Professional Appraisal Practice), why the intended use must be clearly defined at engagement, and why a tax-appeal report cannot simply be reused for a mortgage. Specific compliance questions about scope of work, extraordinary assumptions, or jurisdictional exceptions route to the appraiser since they depend on the specific assignment.

SleekAI hands off via webhook to anything that accepts JSON. TOTAL by aLaMode, ACI Sky, Bradford ClickFORMS, and SFREP all accept structured intake from external systems. The webhook payload includes property address, intended use, effective date, product type, and the transcript, so the receiving system has the order intake populated rather than requiring full re-entry. AMC-side integrations remain on their own platforms.

If you publish commercial services as a separate tier with general-purpose narrative reports, the bot routes commercial enquiries accordingly. Commercial work typically requires a custom quote rather than tier pricing because the scope varies dramatically by property type (office, retail, industrial, multifamily, special purpose). The bot collects building size, type, age, intended use, and approach (sales, income, cost), then routes to the commercial appraiser for a custom proposal.

Yes. Multibot scopes each chatbot to an appraiser, a county, or a property type. A firm covering multiple counties can have each county's fee schedule loaded into its own bot, with display conditions on the contact page showing the right bot based on the visitor's stated location or URL. Reporting in WordPress tracks orders per appraiser for workload planning and revenue attribution.

If you offer desktop (2055 exterior or 1004 with desktop modifier) or drive-by products, they read as separate service tiers with their own fee, turnaround, and limitations. The bot explains the trade-offs (faster and cheaper, less data, intended use must permit) and routes to the right product based on the visitor's intended use. For lender-required full interior appraisals, the bot redirects to the lender's AMC since the lender, not the borrower, dictates the product.

Stored in WordPress with property address, order ID, intended-use category, and visitor metadata attached for appraiser review. SleekAI uses your own OpenAI, Anthropic, Google, or OpenRouter API key, and standard API terms exclude conversation data from model training. For appraisers handling sensitive divorce, estate, and tax-appeal matters, this keeps client data inside your account rather than a third-party SaaS database, which matters for confidentiality obligations under USPAP.