The Business of Instant Messaging
willll writes "The Washington Post is running a story about how AOL plans to make money from Instant Messaging, one of the few successes in recent times for AOL. This article includes plans for corporate versions of AIM as well as discussion on some of the state on instant messaging."
First post and all, but....
I have successfully implemented IM at a number of large organisations here in Australia.
Microsoft decided ages ago to start charging for the service with the release of Titanium (Exchange 2003), so it's hardly news that IM can be profitable.
Good to hear other vendors are getting involved, but until AOL pull their act together in terms of marketing and security, no corporate IT department in it's right mind would deploy their stuff.
that the most trivial application of the internet is the most profitable?
I mean sending text from peer to peer is pretty much the "hello world" of TCP/IP 101.
Sure the clients are a little more advanced, but the base concept is the same.
I don't need no instructions to know how to rock!!!!
Perhaps they could charge by the lol or 'omg u 2' used on their services? Make money and maybe even improve the interweb a little at the same time.
"Its core subscriber base is shrinking, its users are being swamped with junk e-mail,...."
I know one of the reasons family members of mine left was because of the spam. Its insane the crap that gets through to an AOL account. With young members of the family using the accounts it was intollerable. Instead of trying to make money in ways, how about fixing some of the issues with the service and maybe the userbase won't fall. Before long you may start getting new users again. *sigh*
More suggestive is the "serious" use of IM happening on trading desks. Logged, secure, time critical IM. These are the folks who do not screw around. At least not at work. (;
"All that is required for evil to triumph is for good men to do nothing." - Edmund Burke
Amongst other things, AIM still needs some sort of Quality of Service guarentees thrown into the protocol...thus saving conversations like,
...watch...it'll happen!
Tech Peon: Sorry boss, I didn't get the IM informing me I've been laid off due to the tech downturn.
CEODude: But I sent it via AIM to you.
Tech Peon: Ah...putting all our faith into AIM streamlining operations, are we?
These concerns are largely unfounded. Any organization that uses a groupware (e.g. Exchange/Outlook) package already has virtually instant messaging through their standard email conduit. Similar predictions were offered when high-speed access to the web came to employee's desktops. As with the web, novelty wears off quickly and everyone still needs to get their job done. In my experience, using IM in the office reduces the impulse for someone to walk to my cube and interrupt me face to face for something "quick" that becomes protracted and a more significant time sync as we converse. I see IM as a filter for "time-suckers".
Not at all. We use it 'unofficially' in our company and it's invaluable for tracking which customer site your workmates are at, asking them quick questions that aren't worth the bother of a distracting phone call, discussing stuff in the 'background' while on conference calls - this last one had the unfortunate side-effect once of someone on the conference call not realising they weren't on mute, someone (ok it was me) sent them a funny IM to which they started laughing out loud, for all on the call to hear... oops. Wouldn't live without it!
Here's an idea that I'd really love to see implemented. Imagine if somebody were to come up with a grammar that worked on top of an open instant messaging protocol (jabber?) that encapsulated features useful for developers within an IDE?
The usage scenario would go something like this: I'm working Foo.java and have a question about some line of code. I right click on the line of code and a popup menu appears. I select Discuss, and then a side menu appears that lists my coworkers. The IDE uses "cvs annotate" (if I'm using CVS) to see who last modified the line of code I mouse'd over, and highlights their user id in my "Discuss" menu. I click the author (or anyone else for that matter), and my IDE sends an instant message to the other user indicating that I would like to collaborate on Foo.java. The remote user accepts the collaboration invitation and my version of the code appears in their editor window. At that point we can both edit the file at the same time, ask questions about code, or maybe even share a mouse? (Might be nice to be able to point to some code, ask a question, and have the remote user not only read what you are typing, but SEE what you are referring to).
Anyhow, it's a pipe dream, but man that would be cool.
Do it for da shorties
I believe that it is this simplicity that is part of what makes AIM so popular. The average AIM user, which never seemed to be very bright to me, could probably really appreciate the straightforward approach AIM takes to instant messaging. ICQ, which is almost the exact opposite, might repulse those same users, but since AOL owns both, then all is good! They are making use of the best of both worlds, it seems.
However, I currently use Yahoo as my primary messenger, and I have no intention of switching. As far as I'm concerned, Yahoo has found a happy medium, and provides, in my opinion, a much more effecient and useful system than the aforementioned clients.
What AOL should be afraid of is users migrating away from them if they get too pushy on the dollar, though since they claim not to be charging money for existing services, they ought to be secure in this area.
Though I'm not a personal supporter of AOL, I do think that they definitely do have a good opportunity for growth, and believe that any innovations they make might help to benefit everyone.
As more and more employees are using products like AIM to communicate, there is a definte need for some accountability with this communication, especially with security and logging.
If I call someone else in the company, the PBX system (or whatever else is in use) can be set up to log the call. Email is very easily tracked and logged.
AIM conversations, however, use a third-party for most of the communication. Logging is not great in most clients.
The article mentions an enterprise solution developed by IBM to help with that, and I think that there is a market for AOL to get into. Provide a plug-and-play either hardware or software solution that allows internal AIM traffic to remain encrypted on the internal network (internal Buddy Lists and so on) and completely logged. There would also have to be a way for the system to work with other AIM users not on the internal network.
The nice thing about a solution like that would be that the logging and traffic could be completely internal, and the company could place restrictions on outside traffic (no file transfers from the outside, for example).
- (c) 2018 Hank Zimmerman
Another technology that you probably fear is P2P sharing. This is another useful tool that I believe will start to make an impact on the business world. Locutus is what I have set up for them, and they are able to share documents/media that have had to have been requested while still making sure priveleges and security are a priority.
Perhaps you didn't like the computer -- imagine the gaming that would go on...
This is my digital signature. 10011011001
Been struggling with allowing customers access to me when I'm sitting down in front of my pc, and I've done a bit of a test.
I found that customers who demand my time more is a great thing, makes customer service all the easier, but let's face it, INSTANT MESSAGING is just that. Instant.
When you say hello to someone, you don't expect them to take 10 min to say hello back.
When you leave a voicemail, you expect a reply in one business day unless you mark it urgent. With email you expect a response back what? Half day?
I equate an IM an IMMEDIDATE priority even if I'm busy with something else.
Personally, I have seen customers only let down by me not able to keep up with IM customers fast enough.
Great idea, but in the end, the purchasing agents, CEO's with decision making ability and the standards committee's don't have time for me, let alone IM me.
Any other account managers successfully integrate this into their 100-200 customer/month workday?
Yo Grark
Canadian Bred with American Buttering.
Canadian Bred with American Buttering
If only AOL expanded their instant messenger service. Sure you can type and they can type back, but what if you could actually hear the person you were chatting with? Maybe this could even be done in "Real Time." We could come up with a device so you could walk around the room and talk at the same time without tricky networking setup. We could take everyone's name and give it a number and put them in a big book so that if you wanted to chat with someone and didn't know their number you could look it up. It would even have their address!
Think of the possibilities!
Did I miss something in the article or what? I didn't see ANY mention of how AOL plans on turning a profit. Not much more than the very old news that there "should" be a way to turn that many eyeballs into dollars. I wouldn't bet on it.
As to all the folks whining on about how awful IM is in the workplace, I couldn't disagree more. A couple years back our sales force started using IM to message eachother, as it was the only way to communicate while on the phone. This spread to other areas of the company, and has grown in importance to how we do business.
For example, say a salesman has a customer on the phone and needs detailed inventory data that only the purchasing folks have. Rather than putting that customer on hold, an IM over to the right person and the call never has to go on hold to get an answer.
Like any other Internet technology, there's a fair amount of non-business related communication going on. This doesn't even begin to outweigh the benefits IM has had at my company. YMMV.
The line must be drawn here. This far. No further.
Mr. Shein wants to legalize spam and allow ISP to charge for it, a position that I completely oppose. Shein's proposal will result in more spam and flood our in-boxes with even more junk. Meanwhile, users are grabing any technology that is less spam friendly (and not acrane and difficult to use).
I'm not talking about Trillian Pro here.
I'm talking about a professionally written program that supports both UNIX and Win32 (using QT, perhaps), doesn't crash every few hours (WTF is up with all the crappy IM clients that crash more than Win 3.1?), implements REAL features, has technical support (for those luser friends of mine who can't figure out how to install AIM, even when I talk them through it), and doesn't use ads or spyware.
Here are the features I want:
I've come to the conclusion that I must write this software myself. Nobody else is going to implement a portable, spyware and ad free IM client that doesn't constantly crash.
If someone beats me to it, I guess I'll pony up my cash. But I'm sort of hoping to get a free ride on my own protocol specification.
And please don't suggest Trillian Pro. Thank you.
You seem to have missed the point. The technologies you mentioned are great when you don't know whether or not the person is there. However, it's difficult to have a conversation over e-mail or voice mail, and that's where IM shines. IM is not about leaving a message for somebody, but engaging them in conversation when you can't speak to them in person. Yes, you could use the telephone, but you don't know for sure if they're there or not, and that also involves interrupting whatever you happen to be doing at the moment. IM let's you know when somebody is available, and you can ping back and forth without having to walk across the building or stop your work to pick up the phone.
A good example of IM technology being used in a "business" would be my college job as a computer lab sitter. During each shift, there were sitters at all of the different labs on campus, and we were all in contact through an internal IRC server. It made it very easy to keep in touch with other sitters, and even managers. We could ask questions of the other sitters when we didn't know the answer, and doing it over IRC was a lot less disruptive than telling the user, "Hold on while I call over to another lab." One advantage this system has over IM is that for a small group, we were all in the same channel (chat room, conference, party line, whatever you want to call it), so if one sitter was away from his desk, any of the others could still see the question and help out.
Cryptography support.
Servers currently support SSL, and future versions will allow end-to-end encryption of the conversation itself.
Stability.
There are many different jabber clients. Some are more stable than others. Right now, I use Psi, which hasn't crashed on me once.
It should look nice and have a cool GUI.
Again, lots of different clients. I think Psi's GUI is nice. It certainly isn't as crufty as ICQ. But YMMV on this one.
It should be IM client, and nothing else.
Again, lots of clients to choose from. I don't know what kinds of features they may offer, but I'm sure there's bound to be one suited to you.
Portability.
Psi is written against QT and runs on Windows and linux. Not sure about other platforms, but I know there are Java clients out there that should run on nearly anything.
Zero tolerance policy on SPAM.
This would be up to the individual jabber server. The only thing I really got spam with is ICQ, though, which is why I don't use it. I don't get AIM spam since I stopped accepting messages from people not on my buddy list.
Support for modules.
This I'm not completely sure about. I know the SSL stuff for Psi is a drop in module. You just put the DLL (or .so if using linux) in the program's directory, and when you start back up, you have SSL available.
An open protocol specification.
The jabber protocol is completely open and 100% free. Anyone who wants is able to not only write their own client, but also their own server. Anyone can download the reference server code and run their own, too. It's very nice.
A real revenue model, not based on ads or spyware.
How about just free?
A shiny retail box.
Can't help ya there.
Jabber apparently stacks up pretty well. :)
bytesmythe
Hypocrisy is the resin that holds the plywood of society together.
-- Scott Meyer
It's a historical accident that, instead, we have this kludgy, centralized, closed infrastructure that's owned by AOL and a few other players. If AOL goes away and takes their "free service" with them, all the better, as far as I'm concerned. But we'll probably have to listen to this kind of whining over and over again.