Matching incoming post to the case
Not to a folder, but to the property, the matter or the order. That takes your master data, and it rarely sits in Microsoft 365.
Integration
Microsoft 365,
where the work already sits
Outlook, SharePoint and Teams are long since in place and paid for in most businesses. The inbox is in Outlook, the documents are in SharePoint, and between the two sits a person doing the sorting. That route can be shortened without anyone having to learn something new.
This stays
What your application keeps doing
- Outlook as the mailbox, with the folders and rules that already exist.
- SharePoint and OneDrive as the store. We do not build a second document store.
- Teams as the place people talk. We put nothing alongside it that also sends messages.
- Your existing permissions. Anyone who may not open a document does not get it quoted by us either.
We do not replace anything
This is not a replacement and not a migration. Your application stays authoritative for its data and keeps its interface and its workflows. We sit alongside it and take over the routes that today run by hand between applications. Switch us off tomorrow and your application carries on exactly as before.
The boundary
Where we come in
Microsoft ships built-in tools for a lot of this. They help where a task looks the same for every business. They do not help where your workflow is your workflow.
An assistant that answers from your own store
With the source, so it can be looked up, and with a no when there is nothing there. What is saved is the reference; the file stays in SharePoint.
Workflows across application boundaries
A workflow rarely ends in Microsoft 365. It starts there and carries on into the trade software, the accounting package or the inspection software.
Traceability rather than automatic answers
Under every suggestion you see which rules applied. Below the threshold the field stays empty rather than being guessed.
Technically
How we connect
Microsoft 365 has a documented interface for reading mailboxes, files and calendars. We use it with credentials scoped as tightly as possible, and we use it read-only.
- Dedicated credentials with exactly the rights the workflow needs, and no more.
- The permissions from your directory still apply. We do not work around them.
- No second store. What is saved is the reference to the document, not the document.
- Where the content may not leave the building, the language model runs on your own server rather than at a provider.
Objections
What you are wondering now
- So does everyone get to see everything?
- No. Permissions come from your directory and still apply. Anyone who may not open a document does not get it quoted either.
- Does this send our email to an AI provider?
- Only if you want it to. Where it must not, the language model runs on a machine in your building, and then no request leaves your network.
- Could we not build this with the built-in tools?
- For simple rules yes, and then you should. It carries as far as the workflow stays inside Microsoft 365. As soon as your master data sits elsewhere or a match has to be justified, it stops.
- What if we switch later?
- Then the connection switches with you. What we build hangs off the workflow, not off a vendor. That is also why no second store appears that you would have to dig yourself back out of.
Information as at: Microsoft, Microsoft 365, Outlook, SharePoint and Teams are trademarks of Microsoft Corporation. We have no business relationship with them. Information as at 15 September 2026.
Next step
Let us take one workflow
and cost it out.
45 minutes, free of charge. We look for the workflow that costs you the most time between Outlook and everything else, and record three numbers. If it does not pay off, we say so.