# Arguments against integrated intranet solutions?

**URL:** <https://meta.discourse.org/t/arguments-against-integrated-intranet-solutions/99900>\
**Category:** Community Building\
**Created:** [18.Октябрь.2018 19:17:33 UTC](https://meta.discourse.org/t/arguments-against-integrated-intranet-solutions/99900 "2018-10-18T19:17:33Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![wroot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wroot/32/113992_2.png) [@wroot](https://meta.discourse.org/u/wroot)\
**Post date:** [04.Май.2019 07:36:19 UTC](https://meta.discourse.org/t/arguments-against-integrated-intranet-solutions/99900/10 "2019-05-04T07:36:19Z")

</div>

Teams is more a chat platform in my eyes. Yes, you can have a threaded discussion, but it still feels like a chat. And you always see only the latest messages in the channel, 1:1 chat. Not a list of topics. And yes, there is no (maybe there is, but not easy) way to split posts, move to other categories (teams or channels) like in Discourse.

I realize this post is old, but i would add another idea.

When integrated system goes down, everything goes down. This was the problem with Office 365 services for us. We had a few outages and email was down, Skype was down, no way to alert users. So we had to put a message on our on-premise intranet and fight calls flood. Previously we had a local IM product and i would just send an IM to everyone if email is down. Or i would send an email to everyone if IM is down 🙂

Having separate solutions for every need minimizes the risk of all of the communication channels being offline at the same moment.

---

_[View the full topic](https://meta.discourse.org/t/arguments-against-integrated-intranet-solutions/99900)._
