How a Dutch VvE manager automated email triage for 500+ VvEs

The challenge: manual triage in a shared VvE Outlook mailbox

A Dutch property management firm manages 500+ Owners' Associations (VvEs). Every VvE sends a continuous stream of emails into one shared Microsoft Outlook inbox: AGM invitations, proxy vote requests, multi-year maintenance plans (MJOP), meeting minutes, budget approvals, leak reports and damage claims. All mixed together, with no dossier structure and no priority filter.

The problem was not email volume. The problem was that a VvE email is rarely just a message. It is the start of a decision and dossier workflow. An AGM invitation is a governance event with a hard proxy deadline. A leak report is an operational dispatch case that needs a forwarding email to the VvE administrator, a confirmation to the homeowner and a follow-up reminder. Treating these emails as "mail to answer" forced the firm's staff to do triage, document review, address matching and deadline tracking by hand, every day, across 500 active dossiers.

According to McKinsey research on knowledge-work productivity, employees spend roughly 19% of their working time searching for and gathering information. For a property manager handling hundreds of VvEs across a shared inbox, that share is considerably higher, and it produces zero billable output.

Five compounding problems followed:

• No dossier structure in Outlook. The latest state of any specific VvE was impossible to reconstruct from the inbox alone.
• PDF review was manual and slow. AGM packets ran to 60 pages and had to be opened and read end to end.
• VvE-to-email matching was fragile. Staff interpreted subject lines, sender domains and attachment filenames to find the right dossier in Bloxs.
• No daily priority view. With 500+ VvEs, no one could keep track in their head of what was open, overdue or deadline-critical.
• Service requests fell through the cracks. Forwarded leak reports without follow-up tracking became loose ends. Homeowners waited and the firm had no chase log.

The solution: an AI digital intern (Iris)

Iris is Sorrato's AI digital intern deployed at the firm. Iris is not a chatbot, a search layer or an Outlook plugin. Iris is an AI colleague that the firm onboards through a staffing model, the same way it would onboard a junior dossier coordinator. The difference: Iris runs on Sorrato's managed platform and never forgets a deadline.

Iris connects to the firm's existing systems, with no IT implementation project on the firm's side:

• Microsoft Outlook / Microsoft 365 (Graph API). Iris reads the shared VvE mailbox, including PDF attachments and forwarded threads.
• Bloxs (property management ERP). Iris pulls VvE, contract and address data to match each email to the correct dossier.
• Sorrato Layer (the dashboard). Iris shows prepared items per VvE, filtered to what is active, open or deadline-critical.
• OpenAI (LLM layer). Iris classifies emails, summarises PDFs and drafts replies for human approval.

The staffing model is the key design principle. Iris handles the repetitive intake layer; the firm's staff handle the judgment layer. Iris prepares the draft, flags the deadline and waits for approval. Iris never sends emails or submits proxies on its own. The human stays in control of every output.

The 8-step process: how Iris works end to end

1. Mailbox intake. Iris pulls incoming emails from the firm's shared Microsoft 365 VvE mailbox via the Graph API, including all PDF attachments and forwarded threads.
2. Type classification. Iris classifies each email as governance (AGM invitation, proxy vote request, budget, MJOP, meeting minutes) or operational (leak report, damage claim, maintenance complaint, service request).
3. VvE matching via the Multi-Signal Resolver. Iris matches each email to the correct VvE dossier in Bloxs by combining four signals: address normalisation, sender history, attachment metadata and Bloxs contract data. Emails below the confidence threshold go to a human-review queue instead of being matched incorrectly.
4. Attachment extraction. Iris detaches PDFs from the email thread, names them consistently and stores each document as a separate item under the correct VvE dossier, with title, date and document type.
5. Stream A, governance routing. AGM packets, MJOP documents, budgets and meeting minutes are summarised in 3 to 7 bullets covering decisions, financial and maintenance risks, and required actions. If a proxy or voting instruction is needed, Iris prepares a draft for review.
6. Stream B, service routing. Iris assesses operational reports (leaks, damage, complaints) for VvE responsibility. It prepares a draft forwarding email to the VvE administrator and a confirmation email to the homeowner. The case enters the Sorrato Layer with a status and a follow-up timer.
7. Status and automated reminders. Every open item has a status (new / waiting on info / waiting on VvE administrator / closed) and an automated reminder schedule that fires on day 10, day 15 and day 18. No manual tracking needed.
8. Dashboard. The firm's staff log in to the Sorrato Layer and see only what needs attention today: new items, open deadlines and escalations. Closed and low-priority dossiers stay out of view.

Technical insight: building the Multi-Signal Resolver

"The intuitive assumption is that PDF summarisation is the hard problem. It isn't. Modern language models handle a 40-page MJOP fine, extract decisions, flag risks, output bullets. The real engineering problem at the firm was correlating an inbound email to the correct VvE when the email contains a partial address, no VvE reference number, and an attachment named Notulen_2024_finaal_v3.pdf. Outlook's Conversation ID broke on forwards. Bloxs' address records had inconsistent house-number suffixes, the same property might appear as 131A, 131-A, or 131 A depending on who entered it. The match rate was unacceptable until we built the Multi-Signal Resolver, a four-signal scoring model that combines address normalisation, sender history, attachment metadata, and Bloxs contract data, then routes everything below a confidence threshold to a human-review queue rather than guessing. The lesson is one I keep relearning: in a staffing model, the Digital Intern is allowed to say 'I'm not sure, please check.' That admission is what made the rest of the system trustworthy."

The Multi-Signal Resolver can be reused in any property management or document-flow integration where ERP records and inbound communication need to be reconciled without a clean foreign key.

How to integrate Bloxs with Outlook for VvE management

Integrating Bloxs with Microsoft Outlook for VvE management takes four working components, each one addressing a specific failure point in manual VvE workflows:

1. Microsoft Graph API access on the shared mailbox. Outlook's native rules cannot classify by document type or business intent. Graph API access, with delegated permissions on the shared VvE mailbox, gives an AI layer programmatic access to messages, attachments and metadata.
2. A document classifier trained on VvE document types. AGM invitations, MJOP packets, budgets, meeting minutes and service reports each follow distinct patterns. Iris's classifier separates governance from operational on arrival.
3. A Multi-Signal Resolver to link emails to Bloxs records. Bloxs holds VvE, contract and address data, but inbound emails rarely include a clean reference number. The resolver scores four signals (address normalisation, sender history, attachment metadata, contract data) and routes low-confidence cases to human review.
4. A dashboard layer that filters by deadline and status. Bloxs is an ERP, not a daily worklist. The Sorrato Layer adds the operational view the firm's staff need: open items, deadlines, escalations.

Without all four components, integration produces noise rather than leverage. Iris delivers all four as one managed intern for a fixed monthly fee: no per-component licensing, no IT project on the client side.

Iris vs. a traditional chatbot: capability comparison

Old flow vs. new flow, side by side

Old flow (before Sorrato)

1. A VvE email lands in the shared Microsoft Outlook inbox, mixed with all other VvE traffic.
2. An employee opens the email and decides by hand: governance event or service case?
3. The employee interprets subject line, sender and attachment filename to find the right VvE in Bloxs.
4. The employee opens the PDF attachments (sometimes 60 pages) and reads them to pull out decisions, risks and action items.
5. The employee types the proxy response, forwarding email or voting advice by hand.
6. Employees track reminder dates and follow-up deadlines in personal notes or their Outlook calendar.
7. The employee scrolls through 500+ VvE dossiers to find what is open or overdue today.

New flow (with Iris)

1. Iris pulls the VvE email from the shared Microsoft 365 mailbox via Graph API on arrival.
2. Iris classifies the email as governance or operational. 100% coverage, no email skipped.
3. Iris matches the email to the correct Bloxs VvE dossier via the Multi-Signal Resolver; uncertain matches go to human review.
4. Iris extracts and stores all PDF attachments as separate items (stukken) under the correct VvE, with title, date and an AI summary of decisions, risks and required actions.
5. Iris prepares a draft proxy, voting advice or forwarding email; the firm reviews and approves before sending.
6. Iris sends automated reminders on day 10, 15 and 18 for every open item. No manual tracking.
7. Staff open the Sorrato Layer dashboard. The default view shows only active dossiers with open actions or deadlines.

The results: 100% automated triage and PDF summarisation

The firm measures its outcomes with Iris in work shifted, not headcount cut. Before Iris, staff spent a large part of every working day on tasks that produced no decisions and no client value: opening emails, reading PDFs, matching addresses, typing repetitive drafts and remembering to chase. Iris takes over that layer entirely. Staff now open the Sorrato Layer and find prepared summaries, flagged deadlines and draft responses waiting for a judgment call.

The shift is most visible during AGM season, when governance documents spike across all 500+ VvEs at once. A 60-page MJOP packet that an employee used to read, extract and summarise before any decision could be made now arrives in the dashboard as a 5-bullet summary, with financial risks flagged and a draft proxy attached. The employee reads the summary, checks the draft and approves.

For service and maintenance cases, the change is in reliability rather than speed. Iris logs every case, sends reminders on a fixed schedule and keeps a status per item. No service request disappears into the inbox without follow-up. The firm's operational lead put it directly:

"We could send out all the first email contact and we could manage the reminders, and if those reminders went unanswered, we could still send someone over. All of it can be managed from the Layer."

Key results

• 100% automated triage coverage. Every incoming VvE email is classified, matched and routed, with no emails skipped or misplaced.
• 3 to 7 bullet AGM summaries per meeting packet. They cover decisions, financial risks and required actions, replacing manual reading of 20 to 60 page PDFs.
• Automated follow-up cadence. Reminders on day 10, 15 and 18 for every open item, zero manual tracking.
• Single priority dashboard. The default view shows only VvE dossiers with open actions or approaching deadlines, across the full portfolio of 500+.
• Zero login friction. A token-link flow for tenant-side interactions removes drop-off at account creation.
• Zero IT project on the firm's side. Sorrato places Iris as a managed intern for a fixed monthly fee.

Vito Kloots
Lead Developer at Sorrato
Published 8 May 2026 · Updated 21 September 2026
LinkedIn

Frequently asked questions