How to architect Enterprise Chat for your organisation (Part 1) – The 5 Types of Chat Rooms


Attending the Microsoft Lync Conference in February, it was great to be able to meet a multitude of people from all sorts of companies who are using, deploying, or administering Lync Persistent Chat. What’s more, this year, the number of new Persistent Chat adopters had increased triple-fold, as more and more organizations begin to realize the value of implementing Enterprise Chat to drive their team-based collaboration needs.


It struck me though, that the very important aspect of both roll-out and realisation of ROI of Persistent Chat is often overlooked and little formalised or talked about. We’re not talking about architecture in a technical or infrastructure sense here – we mean the very cultural and people-based problem of creating and maintaining the right chat rooms for your organisation.

Our argument is this: To realise the full potential of persistent chat, careful up-front planning of which chat rooms you will need and which users will have access to them is absolutely necessary to drive adoption and build value from the chat room content.


All too often, we see Persistent Chat/ Enterprise Chat deployments that have let both users and administrators run wild with chat room creation, not least the worst case where chat rooms are treated as ad-hoc text-based conferences. This leads to:

  • Fragmented and often completely duplicate collaboration streams
  • Un-focused or incomplete chat history around a specific topic
  • Simultaneous duplication of conversation on email


Carefully managed chat rooms provide the following benefits:

  1. The collaboration culture shifts such that, teams move all day-to-day communication into a chat room. This requires assignment of a specific chat room to each team, and also closing the members list to only the members of that team.
  2. Natural adoption of the collaboration paradigm is faster, if the purpose of each chat room is intuitively mapped to a user’s mental model of the company structure.
  3. All knowledge on a particular topic (and discussion around that topic) gets accrued into the chat room history, which is of course fully searchable. This builds an organic and invaluable repository of knowledge around that topic. Again, this requires specific assignment of a chat room to a given topic – and that all experts relevant to that topic know that the chat room exists.
  4. Answers to a question on a given topic are easily obtained by asking in a chat room dedicated to that topic. This requires that the experts on the topic know about the chat room, and that those who may need to ask questions on the topic also know about the room’s existence.
  5. A succinct overview of all company activity relevant to you is easily obtainable by scanning recent messages in the chat rooms. This is possible when the entire company has migrated to Persistent Chat and understands which conversations should happen in which chat room.
  6. A well-managed chat room ecosystem will mean that new users’ appreciate the usefulness of using chat rooms quicker, and hence accelerate the adoption process themselves.

The process of implementing such a chat room architecture requires a careful analysis of your company’s organisation structure and working culture, and then re-creating this in chat room form.


We’ve found that it helps to think of the following, 5 different types of chat rooms, and then map them to your enterprise:


1) Team-based chat rooms:

  • Day-to-day running of each team happens in these rooms
  • Their membership is locked down to only the users on that particular team
  • Implemented correctly, ad-hoc text-based conferencing and group email will
    naturally migrate over to chat room-based collaboration

Example: A chat room for the marketing team

2) Project-based chat rooms:

  • Day-to-day work on a specific project happens in these rooms
  • All employees working on or dependent on the project are in the room
  • CC-email chains or endless conferences are replaced by the chat room’s
    collaboration stream

Example: A chat room for an IT system migration

3) Topic-based chat rooms:

  • All discussions & knowledge sharing around a particular topic happens here
  • Membership is less restrictive but the experts on the topic are in the room
  • The persistence of the chat history builds an automatic repository of
  • Chat room becomes a go-to place to find knowledge on a topic and
    to ask for help

Example: A chat room for product X

4) Auditorium chat rooms:

  • o General announcement or work-based conversation happens in these rooms
  • o Entire divisions or the whole company is a member of the room
  • o The chat room may be an “auditorium” to restrict those who can send
    messages to those important enough to make announcements

Example: A chat room for the whole company containing updates from the CEO

5) Social chat rooms:

  • A place to talk about specific or general non-work based topics
  • Membership list is generally unrestricted
  • Keeps non-business critical conversation separate from “work” rooms
  • Useful to aid in the initial adoption of the use of chat rooms

Example: A Gaming chat room

In this blog, we’ve talked about the importance of a well thought through chat room structure, its benefits and the 5 types of chat rooms.

  • An example of the chat rooms structure applied in a company
  • Management & Maintenance
  • Setting a naming convention

Ready to try persistent chat? Download the MindLink app on BlackBerry World or iTunes
Try it for 30 days now and let us know what you think below.

Editor’s Note: This blog post was a contribution from Ben Osborne, Lead Engineer working on the core collaboration stack, mobile and web products, from our partner MindLink. Ben has over 7 years experience working with enterprise collaboration systems including Microsoft Lync Persistent Chat, and has delivered mobile and collaboration projects to numerous tier-one investment banks.

Visit to learn more about secure and integrated enterprise chat and realize the full potential of your mobile environment.

About Maria Stockham

Maria Stockham is a Senior Enterprise Product Marketing Manager at BlackBerry focused on unified communications and collaboration and responsible for marketing enterprise applications (corporate and 3rd party including iOS and Android apps securely wrapped for deployment in Secure Work Space). Maria is a full time telecommuter based in Minneapolis, Minn. She understands how technology can enable the successful proliferation of virtual, global teams as well as the productivity and collaboration benefits it can provide. Her software industry experience spans over 10 years in digital imaging and telecommunications verticals. With a degree from the Carlson School of Management at the University of Minnesota, Maria has held various positions in Product Management as well as Product, Program and Channel Marketing.

Join the conversation

Show comments Hide comments
+ -
blog comments powered by Disqus