But in a time when everyone's getting all excited about presence, communications-enabled business applications, everything that gets crammed under this heading of unified communications -- why should you care about something as seemingly mundane as click to call?
Well, Barry argues, maybe click-to-call is all you really need at this stage. Training a whole workforce full of users on a full-blown UC client like Microsoft Communicator or any of the packages offered by the PBX guys might be more of an undertaking than you'd think at first. As Barry notes, not that many people have used communications clients before, so skills may not be as transferable as they are between various office applications.
And that's important when you get to the "Who cares?" question. Why do you even need click-to-call? It's definitely not to save the person time in picking up and dialing their telephone; that is trivial. It has more to do with what that telephone connects to.
I've heard from several enterprises that they're encouraging or even requiring employees who travel internationally to deploy and use softphones on their laptops, to save the still-exorbitant cost of international cellular roaming. Click-to-call is a way to capture that same savings without the need to install, boot up, and switch to a softphone application every time you make a call. It's a more painless way to actually get these workers to take the steps to save the money.
The Citrix solution obviously only is meant for enterprises that use Citrix for their business applications, but the message really could apply to any enterprise deployment: Keep working on the heavier UC clients, keep developing the presence-centric architectures of the future, but also look for ways that enterprise IT managers can make cheaper communications easy for end users to actually use.