Instead of relying on an external service like AIM (perhaps a problem for security or reliability reasons), an organization could have its own self-contained IM system. Messages can also be encrypted with SSL and/or PGP. An organization can set up its own Jabber server. Another advantage is that it's free, open source, and extensible. That's why it's cool for users and developers.

Quick example: an app that tracks stock prices or network traffic, then notifies you when you come online of anything interesting - or sends you a text message, or communicates with a web service via XML-RPC, or whatever. Any system that uses XML to exchange data can do so using Jabber - with all the built-in benefits of presence management, security framework, etc. Jabber users don't even have to be people. Because Jabber is in essence a system for routing XML messages, there's nothing that says that those messages need to be restricted to IM and chat. There are Jabber clients for most platforms that people use in real life, and all the sorts of things you'd hope to find in an IM system: basic IM, chat, group chat, even whiteboard. Jabber is an open source, standards-based, XML-based IM framework - all messages, routing, etc. Otherwise, for example, AIM users can't chat with ICQ users. Jabber (, ) was originally set up as an instant messaging service that allows people on different IM networks (AIM, ICQ, MSN Messenger, etc.) to communicate. I've talked about Jabber enough that I feel that I should give a brief overview for those who aren't inclined to dig too far beyond the simple links that I've provided.

A good icq and jabber