A working agent's inbox on a Tuesday morning: portal leads from three platforms, two buyers asking about the same listing, a notary waiting on a signed compromis, a seller asking why the notary is waiting, a surveyor proposing Thursday, and forty other threads in various states of almost. Property work is coordination work, and the coordination arrives by email.
Split the inbox into its four streams
Real estate email isn't one kind of mail, and treating it as one pile is the root mistake. Four streams, four treatments:
- Portal noise. Listing confirmations, view counts, platform digests. Filter it out of the inbox entirely; it's reference, not work.
- Buyer enquiries. Speed matters commercially here. Template the first reply per listing (availability, viewing slots, next step) and answer within the half day.
- Transaction threads. Offers, notary, bank, survey. This is where deals live and die, and every message here contains either a commitment or a dependency.
- Vendor coordination. Photographers, certificates, contractors. Schedulable, chaseable, delegable.
Why do property deals stall in the inbox?
Because a transaction is a chain of parties who each owe the next step, and email hides whose turn it is. The buyer thinks the notary has it; the notary is waiting on the bank; nobody is chasing. The fix is mechanical: every transaction keeps a waiting-for list (who owes what, since when), reviewed each morning in two minutes. A quiet thread gets a chaser before it costs a week; the cadence and scripts are here.
Batching around viewings
Agents live on the road, which makes continuous checking both tempting and ruinous. The pattern that works: a processing window before the first viewing, one midday, one at day's end, each to zero decisions. Between windows, notifications off except named VIPs (the notary on this week's closing, the buyer at offer stage). The batching method applies unchanged; the windows just fit around viewings instead of meetings.
Where AI fits in an agent's email
The reading layer of all four streams is mechanical: sorting enquiries from noise, extracting dates and commitments from transaction threads, noticing which party has gone quiet, drafting the first replies and the chasers. Pidgy runs that layer on Gmail and Outlook, keeps the per-deal waiting-for lists automatically, and queues every draft for the agent's approval, so nothing sends without you. The full property workflow is on the real estate use case page.
