Yes. The bot reads the exchange custom post type and pulls the identification deadline, closing deadline, and the three replacement properties from the identification letter stored in postmeta. The dates are computed from the actual relinquished sale closing date. A verified investor on their own dashboard gets the same data your coordinators see in admin.

The QI escrow balance is stored as postmeta on the exchange post and updated after each wire. The bot reads that field at request time and quotes the current balance, the bank, and the last reconciliation date. Display conditions ensure only the assigned investor and CPA see balance figures. Other roles see a general escrow explanation without a number.

Yes. The exchange post has a structure field with values like forward, reverse parking, and improvement. The bot reads that field and pulls the right firm memo from the OpenAI Files vector store. A reverse parking question gets the EAT structure and the 180 day deadline tied to the parked property. Improvement questions get the construction draw timeline.

Both rules live in the firm memo collection in the vector store. When an investor wants to identify more than three properties, the bot quotes the 200 percent rule and the 95 percent rule, then asks for the total fair market value of the relinquished property to compare with the replacement list. The bot does not file the letter but flags the call that needs to happen.

Display conditions in SleekAI Multibot scope each bot by URL pattern, post type, and logged in role. The investor dashboard at /my-exchange/ runs a bot tied to the investor's exchange post. The CPA portal at /cpa/ runs a different bot that explains rules without leaking client specifics. Marketing pages run a third bot that books a call.

All conversation logs stay inside your WordPress database. The data path is browser to WordPress to your OpenAI or Anthropic key directly, with no Sleek server in between. For a QI handling client escrow this matters because the balance and the deadline never pass through vendor middleware. You can export or delete logs through standard WordPress admin.

Yes. The same data the bot reads at conversation time can power an internal Slack or email notification through SleekAI Agent Mode. A nightly run looks at every exchange where day 45 is within 7 days and no replacement closing is on the calendar, then posts a short summary to the operations channel. The dashboard bot becomes a check on an already nudging system.

Most chatbots run on a vendor server and read a help center copy of the 1031 rules. They cannot see your actual exchange files, the identification letter, or the QI escrow balance, because that data lives in WordPress postmeta they have no access to. SleekAI installs inside WordPress, reads the exchange custom post type natively, and runs on your own API key.