John, your Viewing enquiry assistant.
John prepares a reply draft, missing-detail questions and a viewing checklist. A person checks the property, diary and wording, then decides whether anything is sent.
Demonstration only · fictional example · nothing is sent, saved or published.
What this preview does and does not do
- It is a static design mock-up of the Viewing Enquiry Assistant interface, using John’s own portrait and existing identity colour.
- The conversation below is scripted and fictional. No AI model, provider or network call is connected, and no message is generated.
- The composer accepts typing so the layout can be exercised, but it cannot send, save or publish anything.
- The appearance switches change this browser only and are never saved on a server.
- A person still checks, edits and decides. This preview claims no live capability, no customer result and no release.
-
Branch negotiator · fictional
Enquiry from PropertyPal: “Hi, is 14 Birch Close still available? Could I view this Saturday?” Buyer is A. Quinn, phone on file.
-
John · prepared output
Prepared reply draft (not sent): “Dear Ms Quinn, Thank you for your enquiry about 14 Birch Close. I can check Saturday viewing options for you. Could you confirm a preferred time and whether you are sale-agreed or chain-free? I will come back to you once a negotiator has checked the diary.” Check before use: property still available; Saturday diary and key arrangements; applicant status; branch wording. Owner: duty negotiator.Prepared draftNot sentStaff decide
Stops here. A person checks the facts, edits the wording and decides what happens next. Nothing is sent automatically.
Mock-up only: this composer has no AI model, network connection or sending ability.