The system prompt is configured per offering. For 506(b) deals, the bot refuses to discuss specific deal terms with visitors who do not already have a pre-existing relationship with the sponsor and instead directs them to a relationship-building intake form. For 506(c), where general solicitation is permitted, deal terms can be discussed publicly but the OM and financial model still gate behind accreditation verification. SEC counsel should review the specific prompt language for each offering.

Yes, when projections live on the deal page. The bot quotes target IRR, target equity multiple, and preferred return with the standard caveats: projections are not guarantees, past performance does not predict future results, and the full risk factors live in the OM. Realised returns from completed deals can be quoted with the same caveats and a link to the case study page.

SleekAI hands off via webhook to anything that accepts JSON, so InvestNext, Cashflow Portal, Juniper Square, AppFolio Investment Manager, and SyndicationPro all work for the IR side. The webhook payload includes accreditation status, target check size, target asset class, deal of interest, and the transcript. Verification flows that need a third-party service like VerifyInvestor can be linked from the chat as a next step.

Display conditions support URL patterns, page templates, and user roles, so the deal-detail bot can be hidden from anyone not logged in to the investor portal, while a separate marketing bot answers the public homepage. For 506(c) offerings where general solicitation is allowed, both can run on the same page with different scopes. For 506(b), the marketing bot stays on public pages and the deal bot is portal-only.

If your team page publishes bios with experience, certifications, and prior deals, the bot reads that and answers accurately. Personal details kept in private custom fields stay invisible. For sensitive questions like compensation, ownership stake, or specific deal involvement, the bot redirects to IR rather than answering, which avoids the risk of misquoting equity allocations or fee splits.

Yes. Multibot scopes each chatbot to a fund, an asset class, or a market. A core-plus office fund can run a chatbot separate from a value-add multifamily fund, each routing to its own IR team and quoting its own target returns. Display conditions tied to deal-page URLs ensure the right bot loads on the right offering page.

The bot can be configured to detect non-US investor enquiries and route them to a separate flow that covers Reg S or Reg D Rule 506 considerations as applicable. For sponsors not set up to accept non-US capital, the bot can politely decline and explain why. Specific cross-border tax and securities-law questions always escalate to counsel rather than the bot answering directly.

Yes. Stored in WordPress with deal of interest, accreditation status, and visitor metadata attached for IR review. SleekAI uses your own OpenAI, Anthropic, Google, or OpenRouter API key, and standard API terms exclude conversation data from model training. For sponsors with institutional LPs that demand strict data controls, OpenAI's enterprise terms tighten this further if required.