Thomas, your Lettings assistant.
Thomas triages routine lettings enquiries and flags anything sensitive. A person decides what is an emergency and what the landlord is obliged to do.
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 Landlord/Tenant Enquiry Assistant interface, using Thomas’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
Tenant email: “The boiler has been making a noise for a week and there’s been no hot water since yesterday.” The landlord is away until Monday.
-
Thomas · prepared output
Prepared acknowledgement draft and escalation flag (not sent): “Thank you for letting us know. I have passed this to the lettings team today. Could you confirm whether there is any heating at all, whether the boiler pressure has been checked, and when someone could attend?” Escalation flag: no hot water is a potential hazard. A person must decide today whether this is an emergency repair and who attends. Checks: no legal advice; no promised repair date; do not decide the landlord’s obligation from this page.Prepared draftEscalated to a personNot sent
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.
