An assistant trained on your building manuals — HVAC, plumbing, electrical, fire safety — drafts the answer, your staff approves it, it goes out. The fifth "where's the shutoff" of the week stops eating a manager's afternoon.
Everything happens in writing — you'll get a concrete plan back, not a sales call.
Illustrative example — your build runs on your own rules, templates and software.
Building manuals, house rules, FAQs, maintenance schedules. PDFs, scans, old Word files - whatever exists, in whatever state.
Documents are indexed per building, so the answer about a boiler cites that building's boiler - not a generic one.
By email, portal message, or messenger - whatever channel they already use to reach you. Nothing new to install for them.
Strictly from your documentation. If the answer isn't in the documents, it says so and routes the question to a human instead of guessing.
One click. Over time, you can let routine answers go out automatically and keep approval only for sensitive topics.
Questions, answers, who approved, response times - so you can see what residents actually ask and fix the root causes.
Usually gathered in one email thread. No preparation beyond finding the documents you already have.
It drafts only from your documents and every draft passes staff approval before sending. When the documents don't cover something, it hands off to a human - it doesn't improvise.
Any language your residents write in. The knowledge base stays in one language; answers come back in the resident's.
In your accounts - your mailbox, your storage, automation on Make or n8n with the Claude API. Nothing lives on my servers.
Tell me where resident questions land today and who answers them — two or three sentences is enough. You'll get a concrete plan for your buildings back, not a pitch deck.
Tell me about your process