December 2008 Archives

This blog entry was posted by Ed Margulies, Senior Director, Product Management CRM Service Products at Oracle. Margulies is a telecommunications architect, usability expert, inventor, and the author of 17 books on telecommunications, contact centers and service automation. The views expressed in this blog are Margulies' and do not necessarily reflect the views of Oracle.

 

CaaS: A Big Telecommuting Enabler

 

Communications as a Service is the right concept for at-home and remote workers. With applications ranging from contact center, customer relationship management and content management, thousands of job functions can be virtualized. In fact for some workers and even some companies, virtualization is quickly becoming a standard way to run companies. This accounts for both small and large companies.

 

Common Access Standards and Help Desk

 

Besides the more obvious issues of human capital and how to manage a remote workforce, it is a best practice to standardize on access methods and a means to troubleshoot those connections.

 

As a starting point, it is a good idea to establish a basic broadband connection standard. Increasingly, this can be done with wireless connections for a mobile workforce and economical cell phone and data broadband services can be negotiated with your favorite carrier. For at-home workers, a standard for DSL, satellite or cable connection is all you need. But it is easier for your IT Help Desk staff to support remote workers if everyone is using the same basic service. If this is not possible, you can still standardize on access packages. For example, you may want everyone using a connection that is at least 256 to 500Kbps and be willing to pay for whatever package allows that connection speed.

 

You also need to set up your corporate data network to allow remote access to your data stores. This will require separate tunneling or VPN software available from most networking vendors. It is important to make sure all of your remote workers have the ability to log on to this remote access software with regularly-changing passwords. Your IT Help Desk staff needs to be well-versed in basic PC troubleshooting, home networking, broadband modems, access services and VPN technology. If your staff is not set up to do this, consider outsourcing that capability so your remote workers have somewhere to turn when something goes wrong. This is crucial because every hour of down time for your remote staff is an hour work is not getting done.

 

I recommend doing a small, workgroup trial of both "remote worker beta testers" and also the Help Desk staff who would be their lifeline. This will help you to get all the kinks out before rolling the remote technology out to the whole workforce.

 

Social Apps and the Virtual Water Cooler

 

Nowadays, there is no reason why remote workers should be segregated or cut off from the rest of your employees. There are simple and direct ways to keep them in touch with one another to keep the social bond between them active. For example, you can set up your own social networking site or use sites that are available on the internet. You can encourage members of each time to interact by posting information about their projects (security allowing of course), asking for feedback from customers and readers, and by posting blogs.

 

In addition to non-real-time social networking sites, you can also encourage employee-to-employee communication with internal or public Instant Messaging (IM). While there is certain utility in sending short messages to one another, it is also useful in replacing the emotional gratification once supplied by chats at the water cooler. IM can be the "virtual water cooler" for a whole new generation of remote workers.

 

It is a best practice to encourage social interaction amongst your remote workers and to publish basic guidelines for these types of communications. These guidelines can point out issues dealing with company privacy, ethics and general on line etiquette. Of course, workers' personal productivity will dictate how much water cooler activity is appropriate. One thing's for sure, you cannot cut people off from socializing or it will hurt morale and generally cause a lack in productivity.

 

Remote Peer Review

 

Consider bolstering your peer review procedures to benefit remote workers. You can use file sharing, white boarding, email and web sharing applications to facilitate peer review, so there is little in the way from a technology point of view. What matters is a regular, and frequent review of one another's' work from co workers. This helps to engender not only a spirit of teamwork, but also encourages high-quality output.

 

For example, consider the development of an outline for a user guide. Before getting started on the rich content of such a document, the author can host a working session on line and with a conference call where one or two co-workers can brainstorm the table of contents and chief topics. In some cases, this may be all some people need to get on the right track. This is also useful for a project manager to establish key milestones for a complex project, or for synthesizing input for a sales pitch or a product demo. It doesn't matter what the nature of the project is. What matters is a standard way to approach, define, and solicit input at crucial steps along the way. It is a best practice, then, to put together simple guidelines for the approach and kickoff of virtually any project. You can build more examples as your remote workers begin to participate in remote peer reviews.

 

Weekly Cross-Team Meetings

 

Cross-Team meetings are a great way to develop trust and interactivity between remote workers. For the remote worker, having transparency with their work product as well as others also engenders a spirit of accountability. A basic cross team meeting is hosted by a facilitator - usually the same person each week. It is a best practice to establish a 'same day - same time' schedule for these meetings so there is no misunderstanding about who is supposed to show up when.

 

A common and effective best practice is to agree on a common template for presentation materials so each department has one slide or one graph to present each week. A remote file locker can be set up for each participant to upload their part of the presentation ahead of time.

 

Content-wise, it is best to limit each department's contribution to one slide. For example, the sales team can show a grid of hot prospects and needs they have for other teams to fulfill in helping to close deals. The support department might have a slide that addresses customer satisfaction issues or support newsflashes. Development may have a slide to show the status of a new feature release. The idea is to give each department a few minutes to present their part and have enough time after each mini-presentation for questions and answers. Any big issues requiring more discussion can be handled in breakout sessions for the stakeholders involved.

 

In summary, you can enable a productive and well-adjusted workforce by following a few simple principles. Make sure you establish standards and basic nuts and bolts support services so everyone can be connected. Encourage electronic forms of social interaction. And encourage regular and standard ways for your workers to review one another's work products and share ideas in cross-team meetings. By following these simple principles and providing guidelines for appropriate use, you can develop a strong and productive telecommuting workforce.

 


Postcards from the Centrex Edge

December 3, 2008 12:05 PM | 0 Comments
This blog entry was posted by Ed Margulies, Senior Director, Product Management CRM Service Products at Oracle. Margulies is a telecommunications architect, usability expert, inventor, and the author of 17 books on telecommunications, contact centers and service automation. The views expressed in this blog are Margulies' and do not necessarily reflect the views of Oracle.
 
Centrex: A CaaS Heritage
 
Centrex service is an excellent example of how CaaS-based offerings are successfully married to enterprise-based, on-premises applications. New York Telephone realized this 40 years ago. In the mid-sixties, this its customers asked for an alternative to the massive on-site switchboards of the day. New York Telephone's engineering department then added simple extension dial and transfer capabilities to their central office switches. These features allowed on-site phone extensions from the central office to act like an on-site switchboard system. And Centrex was born.
 
Early Centrex service came with large multi-button operator turrets and intermediary answering positions. Later, more sophisticated Automatic Call Distributor (ACD) applications such as the Pinnacle ACD option (AT&T 5ESS option) were developed. Even more heavy-duty uses of ACD SaaS offerings were co-mingled with special Emergency 911 software. The on-premises systems handle Public Safety Answering Point (PSAP) duty. Here the calling number ID passed by the Centrex system is used in conjunction with a computer-assisted dispatch (CAD) system. These CAD systems provide heads-up maps and other displays so the emergency dispatcher can use the map data to advise the best available responders.
 
Centrex meets on site Messaging Systems
 
Another Centrex-based innovation is the Simplified Message Desk Interface (SMDI). Here, the Centrex system sends information over a data channel dealing with line availability, phone call time stamps, forwarding information and the like. This is typically used to couple Centrex service with on-site SMDR (Station Message Detail Recording) call accounting software and on site Voice Messaging systems. The interface is emulated by numerous manufacturers now for interoperating between devices - even if they are not CaaS-based.
 
Enhanced Services based on Centrex later gave birth to Basic Rate ISDN offerings (now essentially replaced by cable and broadband DSL). The data channel on BRI lines enabled everything from simple file transfer to real-time third party call control for on-site PBXs and custom service center applications. In fact there were offshoots of this based on analog technology.
 
Centrex and the Birth of Short Message Service
 
Even Data over Voice technology has facilitated the marriage between CaaS and On-Premises Enterprise software. Data over voice is a way soup-up analog Centrex lines in lieu of the more expensive Basic Rate ISDN. Today this is the very popular Analog Display Service Interface (ADSI). It's also called CLASS (Custom Local Area Signaling Services). There are different versions of this service offering all over the world. It's quaint considering the data is sent on-hook using a simple Bell 202 1200 bit FSK modem circuit.
 
Now this technology is embedded in everything from Dialogic voice and network cards to televisions and modern single line phones. The applications for the technology are endless taking into account everything from simple Caller ID-based applications to "visual versions" of Interactive Voice Response - a.k.a. SMS and SMS-based services.
 
Centrex: Incubator for Spatial and Temporal Automation
 
As you can see, Centrex and associated services have been an incubator for a host of innovations - both in the temporal and spatial domains. On the temporal side, interfaces such as SMDI facilitate voice messaging and IVR (temporal) interfaces for automated services. On the spatial side, ADSI and SMS-type services transfer data visually as in a web site. In fact, you can look at new SMS-based services as kind of a visual version of IVR (Interactive Voice Response). Here the dialog is directed and not as self-directed and spatial as a web page.
 
The simplicity and convenience of SMS - that is the keypads on your cell phone - make it both ubiquitous and universal like the web. Traditionally, you text a friend or relative and get a simple chat-type dialog going. But now contemplate how an SMS can be sent from your phone to get automated responses from a machine. Companies like Agent511 offer automated applications like this (From your cell phone, text: DEMO to 511-511 for a sample).
 
So SMS is another medium pretty much dependent on CaaS. And the marriage between CaaS and the enterprise? OK, imagine how an SMS gateway can be used to route messages to an on-premises SMS-equipped ACD (Automatic Call Distributor). In this example, users can use published short codes to send SMS queries to a service center. Those messages are not answered by a single person, but are put into queue so the best-equipped agent can type back a response or push a URL to the "caller."
 
Companies like Oracle are developing this technology along with its customers and partners. The point is, you don't "own" an SMS even though you may own the telephone that you send it from. And on the other end, enterprise-based and software-controlled systems can respond to your text messages - all piggy-backing on the cell phone provider's SMS network - which in itself is a CaaS-based offering.
 
In summary, many innovations came out of the simple idea of Centrex. And today, modern CaaS services continue to add value to enterprise applications - just like Centrex has for almost half a century. Whether it's on-site messaging, Business Intelligence apps, contact center or SMS-based services, the co-mingling of CaaS and the enterprise seems pretty much here to stay.

 

Recent Comments

  • Tom Keating: Just a test comment. welcome to the TMC blogs, Ed. read more
  • Matt Edic: CaaS connotes greater integration of available services and end-user control read more

Subscribe to Blog

Categories

Blogroll

Recent Entry Images

Around TMCnet Blogs

Latest Whitepapers

TMCnet Videos