Yes. Multibot lets you run two distinct bots: one for sellers, one for cash buyers. Display conditions target each bot to the right page (seller landing pages versus buyer-list signup pages), and each has its own greeting, presets, and routing webhook. Sellers get the property-condition flow and acquisitions routing; buyers get the criteria-and-POF flow and deal-list routing. Reporting per bot keeps the pipelines independently measurable.

Yes. SleekAI reads your published buy-box criteria from a page or post (markets, property types, bedroom counts, condition tiers, price ranges, occupancy rules), and the bot uses those rules to screen each inbound seller lead. Properties outside the buy box get a polite handoff, sometimes with a referral option to a partner investor in markets you don't cover, depending on your published policy.

When a cash buyer signs up, the bot captures target markets, property types, capital range, cap rate or ROI targets, proof-of-funds status, and deal preferences (turnkey, BRRRR, flip), and adds those as structured tags in the webhook payload to your buyer list (often Podio, REI Reply, InvestorFuse, or a custom CRM). When you lock a new deal, you filter the list by matching tags and send the deal package only to relevant buyers.

No. The bot is instructed never to quote a specific cash offer in the conversation, because rehab scope and comps drive the number and that requires a walk-through. It can share recent acquisition ranges in the market as context, but always with the caveat that the real range comes from acquisitions after the walk-through. This protects both seller expectations and your negotiating position when the deal moves to contract.

Yes. The bot asks cash buyers whether they have POF ready or need to arrange financing, and captures the answer as a tag. Buyers without POF still get added to the list but tagged so they don't receive time-sensitive deals where the first wire wins the assignment. POF-ready buyers move to the top of the match list for new deals automatically based on the tag, which speeds up the close.

JV partner enquiries (other wholesalers looking to co-source, dispo partners, or capital partners for transactional funding) get routed differently from buyer-list signups. The bot captures partnership intent, target markets, and history, and routes to the partnership manager rather than acquisitions or the buyer-list webhook. Multibot or a conditional branch in the system instruction handles this cleanly without confusing the standard flows.

By answering process questions directly. Sellers ask about close timeline (typically 7 to 14 days), assignment fee structure (we sell the contract, not the property), no-commission terms, who pays closing costs, what happens if they have a mortgage or liens. The bot quotes your published process and timeline, so the first acquisitions call starts with aligned expectations rather than negotiating definitions. Complex situations like probate or distress route to acquisitions with a sensitive tag.

Yes, via webhook. Common integrations include REI Reply, Podio, InvestorFuse, GoHighLevel, Salesforce, and HubSpot, plus any custom endpoint that accepts JSON. The webhook payload differs by flow: seller leads carry property and condition fields, buyer signups carry criteria and tag fields, JV partners carry partnership fields. Most operators map each flow to a different CRM pipeline so reporting stays clean.