Not by itself. The bot asks the accreditation question and captures the response, but 506(c) requires verified accredited investor status, which means a third-party verification letter from a CPA, attorney, or registered service like VerifyInvestor. SleekAI hands the qualifying answer plus the prospect's contact details to your verification workflow so the partner doesn't have to redo the intake. The bot is the front door for the verification process, not the verification itself.

Yes. The bot is configured to summarise fund terms - management fee, carry, hurdle, lock-up, side letters, GP commit - directly from your PPM and tear sheet copy. It will not opine on whether the fund is right for the prospect, which is allocation advice and depends on the full picture. Sizing and fit conversations happen with the partner after accreditation is verified and the prospect has read the PPM themselves.

506(b) prohibits general solicitation, so the bot is configured differently for 506(b) offerings: it discusses the fund only after the prospect has self-identified via a pre-existing relationship gate (a referral code, a private link from a partner email, or a logged-in member area). Multibot lets you run a 506(c) bot on public marketing pages and a separate 506(b) bot behind the relationship gate without crossing the streams.

Yes, when the real estate sleeve accepts 1031 exchanges via a Delaware Statutory Trust structure. The bot can describe minimum exchange amounts, identification windows, qualified intermediary requirements, and your DST inventory at a high level. The actual exchange coordination - 45-day ID, 180-day close, QI selection - is partner-handled, and the bot routes 1031 conversations to the team member who runs that process.

Logs live in your WordPress database in the wp_sleek_ai_chats table with the model, tokens, and origin page captured. Most firms export them to Smarsh, Global Relay, or an in-house compliance archive on a recurring schedule via webhook. That puts the AI-assisted intake inside the same archival workflow as email and other written communications, which is what the SEC examiner expects to see.

Yes. 3(c)(7) funds require qualified purchasers, which is a $5M investable assets test, separate from the accredited investor test. The bot is configured per fund: a 3(c)(1) fund asks the accredited question, a 3(c)(7) fund asks the qualified purchaser question. Running both fund types? Multibot lets each fund have its own bot with the correct gate, so the screening matches the offering exemption.

If you run a Reg S sleeve for non-US investors, the bot can be configured to ask the residency question first and route US prospects to the Reg D side and non-US prospects to the Reg S side, with the correct disclosures and minimums for each. The bot will not offer Reg S terms to a US resident or Reg D terms to a non-US prospect, which is the operational rule that keeps the exemptions clean.

Claude Sonnet and GPT-4o both follow strict no-advice system prompts well across long conversations. The failure mode to watch for is prompt drift when a prospect repeatedly pushes for sizing or allocation advice; the larger frontier models hold the line better than the smaller fast models. Bring your own API key for whichever provider the firm prefers and switch models in the settings without rebuilding the bot.