Nobody emails a property manager to say the building is fine. The inbox is a rolling census of what's wrong: a boiler down in one unit, an owner asking about arrears in another, three vendor quotes for a roof, a tenant's third message about the first message. Volume scales with the portfolio, urgency is wildly uneven, and a dropped thread isn't embarrassing; at the habitability end, it's liability.
Severity first, always
Arrival order is the enemy. The morning pass sorts tenant mail by severity before anything gets answered: safety and habitability issues (heat, water, locks, leaks) first and immediately; service failures second; routine requests and questions third. The pass takes minutes, and it prevents the one failure that matters: an urgent issue aging quietly under a pile of routine mail.
Run repairs as a pipeline with owing parties
A repair is a small supply chain: reported, quoted, approved, scheduled, done. Threads stall between stages, and they stall on a person: the vendor who hasn't quoted, the owner who hasn't approved, the tenant who hasn't confirmed access. So every open job tracks two things: its stage, and who owes the next step. The daily review question is simply "who's the blocker on each job," and the quiet ones get chased before tenants chase you. This is the waiting-for discipline applied to the built world.
How do you keep owners calm by email?
Scheduled updates beat reactive ones. A monthly per-owner summary (occupancy, works in progress, money in and out) answers the questions before they're asked, which is what actually reduces the ad-hoc "any update?" volume. Reactive-only communication trains owners to chase; rhythm trains them to wait for the rhythm.
The layer a machine should hold
Severity-sorting arrivals, extracting job details into the pipeline, tracking which vendor or owner owes a reply, drafting the reminders and the owner updates: all of it is mechanical, and all of it is what Pidgy runs on a Gmail or Outlook inbox, with the manager approving every send. The portfolio keeps its manager; the manager loses the ledger-keeping. The property setup in full: the property managers use case.
