How do you connect Outlook to SharePoint in Microsoft 365 so that an email reaches the right colleague and the right file?
Put Bombos next to Microsoft 365: it reads the email in your shared mailbox in Outlook, looks up the client and the file in SharePoint, and proposes the colleague, a draft reply and the folder for the attachment. After your approval in Bombos, the reply goes out and the attachment lands in the right SharePoint library. It works next to Microsoft 365, not instead of it.
What Does Microsoft 365 Already Do, and What Not?
Microsoft 365 already does a lot on its own. Rules in Outlook act on mail as it arrives, for example by moving it to another folder or changing its importance. A shared mailbox lets several colleagues read and send from one address, such as info@ or the front desk. A SharePoint document library keeps all files for a project or a client in one place, and Copilot in Outlook helps you draft an email or a reply.
What stays with a person is judging the content. A rule acts on the criteria you set; it does not see that a client is asking about an invoice that belongs with your colleague in accounting. A library stores the attachment, but it does not choose the client and the folder. Copilot drafts when you ask it to. So someone still reads each message and decides who takes it and where the attachment goes.
That groundwork is what Bombos prepares. It reads the mail in the shared mailbox, looks up the client, proposes the colleague and the SharePoint folder according to your own agreements, and puts the reason and a draft reply next to it. An agreement about who handles what that lives only in one colleague's head, Bombos asks about and records, so it counts next time.
Which Tasks Run on Microsoft 365?
Each task below starts in Outlook and ends, after your approval in Bombos, with the right colleague, in your calendar or in SharePoint. A question about an invoice goes to accounting with the answer drafted. A signed document goes to the client's folder instead of staying in someone's inbox. A request for a meeting gets a reply with open times from your own calendar. You keep using Outlook and SharePoint the way you do now; Bombos works with the mailbox and the libraries you already have, and your folder structure stays exactly as your office set it up. You start with one task. After that, your own team teaches Bombos the next one, and you do not need to be technical for that.
What Changes in Your Week?
Nobody divides info@ in the morning anymore. Your colleagues open Bombos and review proposals: this email to you, with this reply, and this attachment to that folder. Attachments stop living in personal inboxes, so when a colleague is out, the file in SharePoint is complete. The same team does more work, at a higher quality, for less than half a day a week of the colleague you would otherwise hire.
We set up the first task together with you, with your own Outlook and your own SharePoint. Bombos asks how your office divides the mail and which folders you use, and we write that down, so nothing changes in how you store things. We take you through that first task; after that you can do it yourself, and your team teaches Bombos the next one.
What Doesn't Go Out Without Your Approval?
Bombos sends no email, saves nothing for good in a SharePoint library and schedules no appointment until someone at your company presses Approve in Bombos. A proposed folder stays a proposal until then, and a draft reply stays a draft, even when it goes to a client you write to every week. That limit is always on. Only Bombos can switch it off, at your explicit request and at your own risk.
For every step you can read back afterwards what happened and why. For the work inside your office, such as looking things up, checking and preparing, you decide how much Bombos does ahead of time; messages to customers and payments always wait for your approval. A proposal can be wrong, even when the reason sounds believable. When in doubt, Bombos asks instead of guessing.
All tasks Bombos takes on are listed under use cases.