Mary, your Vendor update assistant.
Mary turns scattered notes into a calm vendor update. A person checks every fact, decides what the vendor is told, and makes the call or sends the message.
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 Vendor Update Assistant interface, using Mary’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
Three viewing notes for 8 Larch Avenue, and the vendor has asked for an update this week. Nothing has gone to them yet.
-
Mary · prepared output
Prepared vendor update draft (not sent): “Thank you for your patience. To summarise the activity so far: three viewings have taken place since the property came to market. Feedback has been mixed, with two viewers commenting on the kitchen and one asking about parking. No offers have been received. I will call this week to talk it through.” Gaps to check: whether the second viewing was confirmed to the vendor; whether any follow-up call was promised. Checks: do not add activity that is not in the notes; no price commentary; no negotiating.Prepared draftNot sentFacts checked
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.