21 October 2026 · modelprop-chatprop-2026-10-21-v1
These terms apply to new agreements that expressly incorporate this version. An existing agreement continues until validly changed. Reading this page does not place an order.
Product terms
B1. This schedule covers the agreed website, email, messaging and voice-chat channels, agency knowledge and supported integrations. AILSA is a former product name; an old AILSA agreement is not silently replaced by this schedule.
B2. Identify the assistant as AI and provide an accessible privacy notice in the interaction. The agency is ordinarily controller of private client conversations we process for it; ModelProp’s own account, security and marketing activities are separately described. The actual purpose determines the role.
B3. The order identifies approved knowledge sources, refresh responsibility and escalation contacts. Do not provide invented staff, fees, property facts or availability. Handle uncertain or sensitive requests by clarification or human escalation. No claim of booking or sent communication is made before the corresponding confirmed save or delivery state.
B4. Keep conversations, attachments and summaries within the correct agency and permissions. Identity-aware CRM answers require a verified identity and authority appropriate to the data. A name or email supplied in chat is not sufficient authority to reveal private tenancy, offer or account information.
B5. Collect only relevant details. A request to contact the agency permits the requested interaction under its proper lawful basis; it does not subscribe the person to unrelated marketing. Any optional marketing permission must be distinct. Apply the callback-number and refusal rules in Schedule A where the channel uses caller context.
B6. Bookings use the agreed booking authority and real conflict checks. Website and telephone channels sharing a diary must not double-book. Preserve cancellation status, assigned staff and agreed time zones. Third-party messaging and email connections require valid customer authorisation and provider conditions; there is no implied right to mass-message contacts.
B7. The order states what counts as a conversation, included units, channel-specific charges, transcript access, retention, support and refresh commitments. Browser microphone permission is a device choice, separate from contract acceptance and data-protection consent. Do not activate recording or create a paid provider session merely because a page was visited.
B8. Acceptance must cover knowledge accuracy, escalation, identity controls, callback preferences, save failures and the actual customer experience on each purchased channel.