Microsoft Communicator. If you're in a big company that already uses MS Exchange for emails then it's a pretty easy integration. Probably not a great solution for small companies due to the cost.
The O365 plans that include Lync aren't really that expensive, surprisingly enough. It's not a reason to switch, but for companies already used to Exchange, it's probably a viable option.
Office365 makes the cost pretty low. And Lync has got to be one of the better MS products. It blows other PBX/presence solutions out of the water.
Probably the main reason it hasn't completely dominated is because MS is taking a weird partner-oriented approach to VoIP with it. So getting setup with some numbers and outbound calling is tons more work than it should be.
I used to be on a team which used SameTime. Although I disliked using Lotus Notes for email SameTime was a joy, especially the ability to take and send screenshots from the chat window.
We also figured out you can add arbitrary gifs as "emoticons" with built-in keyboard shortcuts and everything. Great fun ensued sending terrible reddit gifs to communicate :-)
I'll second this. We have a team in New York and a team in Paris, and flowdock has absolutely been the best hub for seeing what's happening across teams, and communicating with each other
God says...
harts smile unyielding devout illusion pence population
acting Kenya happier chiefest late matrons wantonness
extension mystery VERSIONS sticking NO inchoate Sierra_Leone
faulty commission licensed recent bedewed avenue drowsiness
entirely beasts not sole antidote
We predominantly use our feet. Unless someone's snowed in, sick, or subcontracted (and not local) we just walk on over to their desk and talk. Or, hold an ad-hoc meeting. When someone's physically absent from the office, we have no standard policy (though Skype is common).
VoIP, email and very occasionally an internal messenger. The idea is not interrupting others too lightly, since we already have scheduled meetings. If something needs dealing with urgently, then these measures kick in.
Engineers use primarily IRC and collaborating with non-engineers is in a Hangout, although we'll use Hangouts too when just need to over something in detail over a short amount of time.
56 comments
[ 3.0 ms ] story [ 116 ms ] threadWhat XMPP server are you using or would you use?
My setup is LimeChat -> Bitlbee -> GTalk.
Probably the main reason it hasn't completely dominated is because MS is taking a weird partner-oriented approach to VoIP with it. So getting setup with some numbers and outbound calling is tons more work than it should be.
And sometimes XMPP.
Still pretty new, and in closed beta. But it adds an interesting threading/topic model onto the typically chaotic stream of most group chat apps.
God says... harts smile unyielding devout illusion pence population acting Kenya happier chiefest late matrons wantonness extension mystery VERSIONS sticking NO inchoate Sierra_Leone faulty commission licensed recent bedewed avenue drowsiness entirely beasts not sole antidote
http://www.templeos.org/Wb/Apps/HolySpirit/HSNotes.html
A stupid configuration prepends an underscore to urls, preventing it to be clickable. Hate it.
Pros:
-Outlook Integration
-Screen Sharing
-Decent UI
Cons:
-Literally the worst copy & paste implementation I've ever seen.
-No third party chat protocol integration. (I want to integrate Facebook and Google's Jabber).
Edit: Formatting.