William, your Branch inbox assistant.
William labels incoming messages into a workable queue. A person works the queue, answers what needs answering and decides what to escalate.
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 Branch Inbox Triage Assistant interface, using William’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
Twelve messages in the branch inbox this morning. Sort them into something I can work through.
-
William · prepared output
Prepared queue — labels only, no replies sent: Reply draft (3): viewing enquiry; tenant reference request; contractor invoice query. Book / check (2): valuation appointment; key collection. Escalate (1): complaint about a missed appointment. Waiting (4): solicitor; surveyor; two applicant documents. Information only (2): portal newsletter; supplier notice. Flagged, not guessed: one message is ambiguous and needs a person to read it. Checks: nothing deleted, nothing replied to, no appointments booked, no records changed.Prepared queueNo replies sentStaff work it
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.