The GAIS AI assistant menu
Each assistant follows the same safe pattern: the repeated job, what it receives, what it prepares, where staff approve, and what it must not do. These are fictional examples — used to make the idea concrete before anyone shares private data.
Respond to viewing enquiries without missing basic details.
Old way: portal, email and phone notes arrive separately. Staff retype similar replies and chase missing information.
Prepares: reply draft, missing-detail questions, viewing checklist, internal owner note.
Does not do: confirm a viewing, send a reply, access a live diary, promise availability.
Turn scattered activity notes into a calm vendor update.
Old way: viewing notes, feedback and staff comments sit in different places. The vendor waits for a clear summary.
Prepares: vendor update draft, factual activity summary, gaps to check, call-or-email suggestion.
Does not do: invent activity, advise on price, negotiate, send updates.
Organise buyer feedback and chase missing comments.
Prepares: feedback summary, polite chaser draft, safer wording options.
Does not do: fabricate sentiment, pressure buyers, give legal advice, send messages.
Follow up old appraisal conversations without starting from a blank page.
Prepares: polite follow-up draft, call prompt, missing-context list.
Does not do: claim market value, give pricing advice, pressure owners, promise outcomes.
Turn incoming branch messages into a workable queue.
Prepares: labels such as reply draft, book/check, escalate, waiting, information only.
Does not do: delete messages, send replies, book appointments, update records.
Draft listing copy from supplied property facts.
Prepares: listing draft, short caption, brochure paragraph, missing-facts checklist.
Does not do: invent features, claim school catchment, set price, publish anything.
Triage routine lettings enquiries and flag sensitive cases.
Prepares: acknowledgement draft, missing-information questions, escalation flag.
Does not do: give legal advice, promise repairs, handle emergencies, decide arrears.
A short morning view of what is stuck and what needs approval.
Prepares: morning queue, stuck-items list, approvals needed, suggested check-ins.
Does not do: discipline staff, contact clients, judge performance, alter CRM records.
The best first assistant is usually boring in a useful way.
Look for a job that happens often, has clear inputs, produces a draft or checklist, and has an obvious human approval point.
A useful first question is: Which of these jobs feels real in your branch?
If none of them do, that is useful feedback too.
