Yes. Multibot is designed for exactly this — separate tone, separate source pages, separate hand-off destinations, sharing one install and one licence. Landlord-side reads your fee schedules, accreditations, and onboarding pages and routes to your new-business CRM; tenant-side reads house manuals and tenancy guides and routes maintenance into your repairs platform. Each is invisible on the other's pages thanks to display conditions.

If your fees are on the site — say 9% plus VAT for single lets and 12% for HMOs — SleekAI reads them and quotes accurately. If your management fees are bespoke, you can keep ranges public ('from 8%') and route specifics to a human adviser. The bot will not invent a fee structure to sound helpful; it will say 'I don't have a specific figure, but I can have Hannah send you a tailored quote' and capture the lead.

Yes. The tenant-side bot captures property address, issue description, urgency level, photo uploads, and access arrangements (key safe code, pet warnings, working hours), then posts the package to your repairs system via webhook. Most agencies feed straight into Arthur or Reapit, where the maintenance ticket arrives pre-categorised by urgency and the property manager doesn't have to do data entry from a chat transcript.

SleekAI hands off via webhook to any system that accepts JSON. Many property managers feed enquiries straight into Arthur for management, Reapit for sales-and-lettings, or PayProp for client accounting. The webhook payload includes property reference, contact details, issue or enquiry type, and the full transcript so the receiving platform doesn't lose context. Custom mappings are straightforward in either platform's webhook handler.

Inside your WordPress install. Tenants' personal data — names, addresses, phone numbers — stays on your hosting; nothing leaves except calls to your own OpenAI key. For GDPR purposes, OpenAI is named as a sub-processor in your privacy policy and conversations are not retained for training when called via the API. CSV export is available for subject-access requests, retention policy, and audit.

Yes. Display conditions support login state, page templates, URL patterns, and user roles, so you can show or hide the bot precisely. A common setup: show the public landlord bot to logged-out visitors on /landlords, show the tenant bot only to logged-in tenants on the portal, and hide both from /admin and from the staff intranet. Display conditions can also schedule the bot to staffed-hours-only if you prefer.

If your service area pages flag which postcodes fall inside Selective Licensing zones or Article 4 directions, SleekAI references them when answering. A landlord asking about an HMO in Leeds Headingley will be told the property likely needs both a mandatory HMO licence and a Selective Licence; one in a non-Selective area gets only the HMO answer. Edge cases — boundary streets, transitional periods — escalate to a human compliance specialist.

The tenant-side bot is configured to handle rent-arrears and possession questions with care: it shares general information about Section 8 and Section 21 procedures from your published guides, but it never gives advice on a specific tenant's situation. Any conversation showing financial distress or eviction risk escalates immediately to a human property manager and is flagged in the log for sensitive handling, in line with how a responsible agency would route those calls anyway.