Jelly doesn't directly integrate with Office365 or any existing shared mailboxes, at least not at the moment. You just forward email into it, from any source, and then use the Jelly web application to collaborate on those emails.
In the future we'll be looking at ways to streamline the setup with existing mail providers like Google, Office365 and so on, but we're starting out simple. There are lots of teams sharing logins to single email accounts whose lives we want to improve.
Ah, okay. I’ll keep an eye on Jelly. It looks really nice and could be something they go for, though I know a nice smooth transition would be nice and the possibility of falling back to the shared mailbox if necessary.
I’ve thought about putting for serious effort to setup discourse like they explain using it as a ticketing system with email but this seems better.
This is why Jelly doesn't price-per-seat -- other tools get expensive, fast.
And those other tools do a lot more too, and they're definitely a great choice if you've got great revenue and dedicated customer support "agents", or you want AI to answer your 10,000 daily support queries.
Jelly tries to serve the rest of us: companies, teams and other groups who just want to collaborate on email, and not get stung in the wallet every time somebody new joins in.
The higher tier also has a trial period, so you can go all-in using the sent mail sync, and then all-out, should you wish.
We (Good Enough) would rather help an unhappy customer exit cleanly, than keep you stuck using software you don't like.
If this is the only thing stopping you from using the service, get in touch with us and hopefully we can reassure you about how committed we are to helping you leave Jelly with all your data intact, if it turns out to be the best thing for you.
Quite a few comments now about how you can use forwarding or mailing lists to achieve something similar. There are definitely plenty of relatively-simple ways to _distribute_ incoming emails to multiple recipients.
But once the messages end up in your personal inbox, it's pretty hard for the other people you are collaborating with (or your family in the scenario here) to participate in the rest of conversation, unless you're willing to be extremely diligent with Cc/Bcc-ing.
It's also certainly possible to use things like labels or messages-left-in-draft to try and avoid stepping on each other's toes and coordinate responses. But again, you've got to be diligent.
What Jelly aims to do is make it _easy_ for non-technical people (and technical people who want something that "just works") to share email smoothly, without having to build the rules themselves or make sure everyone sticks to the system to keep it working well.
