Contact me
Resident communication

Same question. Different resident. Every single day.

An assistant drafts the answer from that building's own documents, such as house rules and building systems. Your staff read it and send it, and the fifth "where's the shutoff" of the week stops eating a manager's afternoon. A staff version runs today at one portfolio. The version that answers tenants directly is what I build for you.

Everything happens in writing — you'll get a concrete plan back, not a sales call.

The problem
  • Every repeat question pulls a manager off real work
  • Vendor calls get tracked in someone's memory, not a system
  • The answer you get depends on who's in the office that day
→
What changes
  • If there's no answer on file, it lands in your inbox for a human to handle — nothing guessed
  • Can answer each resident in their own language, off one knowledge base
  • Can also run as a chatbot link — share a QR code and residents ask it directly, any time
Resident inbox — Maple Court
Hi, no hot water in unit 8B since this morning. Is something going on?
Resident · 8:12 am
Good morning! Boiler maintenance is scheduled today from 2 to 4 pm — hot water will be back by 4:30. If it isn't, reply here and we'll send a technician.Drafted from: Building manual, p. 14
AI draft · awaiting approval
Approve & sendEdit
Good morning! Boiler maintenance is scheduled today from 2 to 4 pm — hot water will be back by 4:30.
Sent 8:16 am · approved by staff

Illustrative example, not a screenshot of a client system. What I build runs on your own rules, templates and software.

Ask about your own building manuals

Step by step

From a resident's question to an approved answer

1

You share the documentation

Building manuals, house rules, FAQs, maintenance schedules. PDFs, scans, old Word files - whatever exists, in whatever state.

2

I build the knowledge base

Each building gets its own profile from its documents, so the answer about a boiler comes from that building's boiler, not a generic one.

3

A resident asks a question

By email, portal message, or messenger - whatever channel they already use to reach you. Nothing new to install for them.

4

The assistant drafts an answer

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.

5

Staff approves and sends

One click. Over time, you can let routine answers go out automatically and keep approval only for sensitive topics.

6

Everything is logged

Questions, answers, who approved, response times - so you can see what residents actually ask and fix the root causes.

Setup

What I need from you

Usually gathered in one email thread. No preparation beyond finding the documents you already have.

Building documentationManuals, rules, schedules - per building, in any format.
Real resident questionsA few weeks of typical emails, to tune the tone and coverage.
Access to the channelThe mailbox or portal where questions arrive.
Questions

Fair questions

What if it gives a wrong answer?

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.

Which languages does it handle?

Most languages your residents write in. The knowledge base stays in one language and answers come back in the resident's. I test it on your languages before it goes live.

Where does it run?

In your accounts or on your own server: your mailbox, your storage, automation on Make or n8n with the Claude API. Nothing lives on my servers.

How many questions did your team answer this week?

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