Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Online Community For a Call Center?

Posted by timothy on Tue Oct 14, 2008 11:07 AM
from the legal-department-would-kill-the-dating-features- dept.
kirkmacdonald writes "I work as an analyst in a small call center. There are about 200 on phone agents, but half of them work from home. About a month ago I submitted a Project Charter to create an online Community for the agents. The basic premise was something approaching the combination of a wiki application and a standard forum (phpbb and the like). We already have an online knowledge base for company policies, training and system documentation. This community environment would be intended to simulate being able to talk shop with the person next to you, along with the lunchroom and water cooler. The Charter was well received but there were questions from upper management about how using this type of environment could affect the call center metrics (average handle time, after call wrap up, etc). Can anyone comment on other companies that have online communities for their staff? How did they mitigate productivity risks?"
+ -
story

Related Stories

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • tsk tsk (Score:4, Insightful)

    by Anonymous Coward on Tuesday October 14 2008, @11:10AM (#25370239)

    Your mistake was to ask upper management for an official project. Instead, just ask your co-workers for their IM contact information and get to know them that way.

    • Re:tsk tsk (Score:4, Funny)

      by ushering05401 (1086795) on Tuesday October 14 2008, @11:42AM (#25370747)
      "Your mistake was to ask upper management for an official project"

      And if you ever wake up and think - "wow, my boss finally gets the new web paradigm," you will have people like the submitter and commenters who post productive advice to thank.

      Btw, I have never dealt with the subject the poster is asking about, so I have no productive advice to give.
    • Re: (Score:3, Interesting)

      In every call center I've ever dealt with, there have been two things I've noticed.

      One is that the floor supervisors (the actual ones, not the second level people who pose as them when callers ask for them) usually care about the agents working under them, and will do what they can to improve their ability to do their jobs.

      The second is that higher management cares about their clients, and want to match whatever metrics their clients are setting for them, often to the exclusion of the needs of the agents.

      Ne

  • by Kintanon (65528) on Tuesday October 14 2008, @11:10AM (#25370247) Homepage Journal

    Are you hiring? Any language requirements? What company? What kind of call center? Come on man, hook a brotha up!

  • by Joe The Dragon (967727) on Tuesday October 14 2008, @11:11AM (#25370255)

    Say it can save time by having logs of how to fix stuff vs having to google the same stuff over and over.

    • Re: (Score:2, Interesting)

      I was going to say that they already have a knowledge base for that, but it seems they don't use it for that purpose. They really should.
      • Many issues have more than one possible fix. Speaking from years of experience in tech support, knowledge bases of fixes are of limited usefulness and are often misused because all they have are cheat-sheets on fixes. That means that unless the tech knows how to tell which fix to use (and only needs the cheat-sheet as a memory aid) they're going to pick one at random and hope for the best. Then, they'll either guess again or escalate the call and let some more senior tech try to clean up the mess.

        Granted, this can still happen (and often does) when the tech has access to other techs for suggestions, but it doesn't have to. If the company had (let's say) a private chat server and one or more chat rooms for techs only, somebody who couldn't tell which of several fixes to try first could ask questions and get back suggestions as to how to narrow the possibilities down. Management might go for this because it would be easy for them to monitor and keep the techs from using it for time wasting. (Just like you they don't have to monitor every call for it to have an effect; just knowing they might be listening in can keep you on your toes.)

    • I did this very thing, although I didn't ask first. #1 rule is it's better to ask forgiveness than permission. anyway, here's my system:

      1) Backend is SOLR [apache.org]. It's a fulltext search engine you can configure and speak to via XML.
      2) The front end is a search page like google I wrote in PHP, but searches over other sections of the website. The sections include a wiki I threw together, documentation, training videos in a youtube like format and the corresponding powerpoints, our KBA system (which is availa
  • by LaminatorX (410794) <sabotage AT praecantator DOT com> on Tuesday October 14 2008, @11:11AM (#25370259) Homepage

    Roll it out to a test group first.

    Make sure they understand that this is a privilege, and that if important metrics are negatively impacted it will go away.

    Measure over a 60 day period. Be sure to incorporate user-feedback as well.

    • by eggoeater (704775) on Tuesday October 14 2008, @11:34AM (#25370613) Journal
      I'm a call center engineer.
      It will affect metrics. Without any doubt.
      To the call center managers it's all about AHT (average handling time.)
      In larger call centers (4000+ agents), shaving 1 second off of AHT will save you $100K a month.
      A lot of the products my company sells is all about analysis of call data (MIS) and the ability to better route the call to reduce AHT.

      The only way these types of projects/products get sold is to convince the managers that it will help solve the customers problem so they don't need to call back, thus saving money.

      It's INCREDIBLY difficult to get a call center manager to spend money on training agents how to better service their customers.

      But all that aside, I wish you luck.
      • by Anonymous Coward on Tuesday October 14 2008, @11:39AM (#25370695)

        You work for Accenture, don't you.

        I remember Accenture. They'd come in with their lattes, casual dress, and sunglasses all the way to the conference room, then sit in there and eat Thai while they talked about how many agents my company could lay off and stay within handle time target.

        I hated that vendor, because I sat by the conference room.

        • For the record, NO, I don't work for Accenture. There are many MANY consulting companies out there that do exactly what you describe. My company does some consulting (and our customers are very happy with both our service and rates) but we mostly do software sales now.

          I keep my company life and /. life separate so any rants I make here doesn't reflect on the business, but if you're really interested in learning more about the company I work for, send me an email: eggoeater__nospamplease__@yahhooo.com. (re
        • Re: (Score:3, Informative)

          Escalating calls is never a technical challenge (I've done routing scripts hundreds of times that do just that), but simply a business decision.
          Most businesses don't encourage it because it's expensive. As you move up the knowledge chain, the cost of the call increases almost exponentially because the expertise you are bogarting isn't cheap.
          eg. for a tech-support call, it's incredibly difficult to weed out callers who actually know what they are talking about vs the typical moron who doesn't know what to
  • Clearspace (Score:3, Insightful)

    by colganc (581174) on Tuesday October 14 2008, @11:13AM (#25370303)
    You should check out Clearspace (http://www.jivesoftware.com/products/clearspace [jivesoftware.com]). We looked into the product when searching for collaboration software. Ultimately we didn't pick it since it didn't fit our needs quite right, however it sounds perfect for you. Builtin forums, user profiles, wikis, and a host of other things.
    • Re: (Score:2, Informative)

      We use Clearspace and love it. We also use the jabber server (Openfire) from Jive and love that as well. The combination of the two makes a great collaboration platform. Couple of things though:
      • Clearspace isn't free so I'll probably get modded down for suggesting it but I like it so bleh. You can use it with up to 5 users for free. They also will give you a trial license so you can testing it with a group of individuals and see if you like it.
      • Openfire is free. They have a pay version but the free ve
  • by Anonymous Coward on Tuesday October 14 2008, @11:14AM (#25370313)

    In the end it is the responsibility of the agent to stay within metrics. I would recommend sticking with the knowledge base you have already, but wikify it. I lobbied for a wiki at the last call center I managed, got it, and our agents' productivity skyrocketed. You don't need to go much further than that.

    If one of your techs finds a way to make X do Y faster, let her put it on the X article. She doesn't need to post it in a social forum full of "lol" and "did you see the new guy's shoes". Wikis are great for call centers, but social environments would definitely tempt agents, since they would be "company-sanctioned".

  • Anyone who would waste time on the offical company forum is already wasteing time.....on sites like slashdot.
    • Anyone who would waste time on the offical company forum is already wasteing time.....on sites like slashdot.

      True, but if you submit an Ask Slashdot that's work related, you can claim your Slashdot subscription as a business expense!

  • I worked in customer service as in-game support for an MMO. We had a massive wiki which aided us greatly in helping with player problems. Step by step instructions for solving common problems etc, explanations of how each quest worked and so on. Granted this was all a text interface, allowing multiple 'calls' to be taken at once, with a liberal use of macros. I can't comment on how effective it would be in a one on one voice based call, but it did provide a quick and easy way to find information on nearly
  • Talk shop with the person next to you? At a call center?

    Operator A: Hey man, how do you pass the time here?
    Operator B: Here, smoke this...

    • Re: (Score:3, Interesting)

      I've actually seen that used as a way to get fired on purpose at my call center.
      IIRC, it was a Monday, their rent was due Friday, and it wasn't a pay week. Under the state's law, fired employees must recieve their last paycheck within 3 days of being fired.
  • alan.c.davis@att.net (Score:5, Informative)

    by alancdavis (677086) on Tuesday October 14 2008, @11:18AM (#25370399)
    Long ago and far away I worked for DEC in the UNIX support team. We were spread out all over the world and had the normal complement of call history, system documentation and troubleshooting databases.
    When we started using IRC to share real-time information about callers problems our time-to-close went down significantly and closes-per-day went way up.
    The improvement was significant enough to get the attention of other departments and the IRC usage - along with several bots for integrating the call handling and mail response systems into the IRC channels - became wide-spread in the support group.
    This system survived the DEC/Compaq merger and on into the HP buyout.
    If I were to do the same thing again I'd use a jabber server rather than IRC but the principle is the same.
  • if your employes aren't talking then you've got one hell of a productivity risk just in that.

    Though most call centres I call are dumb and can't answer questions anyway so I doubt your productivity will be much lower than theirs.

    • by mikael_j (106439) <slashdot.pantburk@info> on Tuesday October 14 2008, @01:15PM (#25371977) Homepage

      You do realize that one reason most techs at call centers come off as dumb is because they're not allowed to solve problems that they know how to solve, or they don't have the tools to solve the problems ("You might break something, now go play with something else like a good little boy") and because they're constantly pushed to handle more calls, right?

      Guess what will get a tech employed by a call center fired, is it A) Not properly helping a user, or B) Repeatedly exceeding the AHT. The answer is, of course, exceeding the AHT repeatedly, they don't care if you get pissed about poor service, they're so desensitized to your anger that all your yelling will accomplish is to trigger an urge within them to fuck you over by doing everything by the book (because it will take you ages to get proper help and no one will give them shit for treating you that way).

      Basically, what you called a productivity risk is exactly what is the problem with call center productivity. It's all about easily quantifiable data, and "calls handled per day" is a lot easier to quantify than "customer satisfaction". Besides, who cares if your employees are bitter and turnover for 1st line techs is over 100% per year? That just means you don't have to give out so many raises (yes, the head HR guy for a previous employer of mine actually said that).

      /Mikael

  • If you want your employees to waste time in online communities, you could could just remove the myspace and facebook blocks at the proxy server...
  • Over here, instead of a web-board or something like that, management setup a chatroom on our IM server. They then encouraged everybody from front-line tech support up though the developers, sysadmins, engineers, and their managers to join. Attendance is encouraged but not mandatory, and it's been emphasized heavily that people are free to speak their minds about any subject including bashing management without reprisal -- just don't get into a flame-war. What resulted was the room became a mechanism to i
  • A simple way to ensure metrics are not negatively impacted is to integrate them into the system. Have a built in timer that tracks how much time they spend on it. If someone is spending an undue amount of time, automatically alert their manager to look into it.

    Of course the hope is that this will actually lower call times. So in that instance, I would propose a test run with a sample group and see how it impacts their metrics over a period of time and compare to the control group.

    The key thing to com

  • Easy. If the SLAs start to suffer, just increase the frequency of beatings applied to the cattle.

    If THAT doesn't work, move to phase two, tazers.
  • We are not a call center, but we are a "distributed" software engineering company, with offices in different cities.

    We use a combination of Campfire (37 Signals) for group chat, and an IM application such as iChat, Adium, Trillian, or Gaim for private one-to-one chatter. (Many IM programs will interoperate these days, but it is usually best if you can get most people on the same software. For example, iChat with the Chax plugin will talk to people with Jabber, AIM, or ICQ IM accounts, but not MSN.)

    Thi
  • Second life? (Score:3, Insightful)

    by nizo (81281) * on Tuesday October 14 2008, @11:38AM (#25370665) Homepage Journal

    As an added bonus, you get to learn which of your co-workers is a furry.

  • by michaelasi (1385445) on Tuesday October 14 2008, @11:44AM (#25370765)
    I managed a small technical support contact centre of 80 full-time and part-time agents. About half of the agents also worked from home, like your situation. When we we trialed the ability of agents to work from home we identified the need to keep the agents connected. We used MSN Messenger for a while but soon recognized that this wouldn't work long term. We implemented and IRC chat server and found this fit our needs. When we were implementing this, I admit that I had the same questions as your management staff had. The results were surprising and very positive from a management point of view: 1. Our average handle time went down 15 seconds 2. Our productivity (calls handled, time on phone) went up 10% 3. We were able to keep key employees even when they moved out of our employement area 4. Improved the first call resolution rate by 5% I also believe this was a factor in our ability to have a low employee turn over of 8% in the contact centre. Later we were able to leverage the technology to improve communication between the contact centre and other groups in the company. Announcements regarding current operations situations could be quickly conveyed to the entire team reducing the trouble shooting time during an system outage and improving communication so efforts were not duplicated. Hope this helps and good luck.
  • I'd expect that after a short period of time getting the system running, you'd see an improvement in the metrics. Help-desk support productivity is strongly enhanced by rapid access to answers - either in a knowledge base or via an interactive chat. Hopefully your management isn't overly guided by day-to-day metrics and can occasionally think more strategically.

    Not everyone knows all the questions to all the answers, but over any decent-sized operation SOMEBODY will. The idea is to leverage that "institu

  • I worked in a call center for over 3 years. I started on the phones (1.5 years), moved to Quality Assurance (1 year) and then moved to the IT team as a developer (1 year). I hope I can provide some insight.

    The call center that I worked at had something similar to what you are asking for. We had a central portal with integrated messaging, suggestions, forums etc. Each of the representatives logged into this portal when they started their shift. The portal application was designed so that any incoming c
  • by kungfool (949878) on Tuesday October 14 2008, @12:04PM (#25371047)
    Having spent eight years designing call center applications, I can tell you the one metric you'll want to point your bosses at is the potential to increase first level call resolution. You should balance any increase in call handling time with the potential for greatly reduced call escalation. The key to this is involving the second and third level escalation points in your wiki.
  • When I worked at the Egghead call center in Washington back in, I think, 1996-ish, we tried this out. It was a rough place to work at the time. The employees were miserable, management was ineffective and, at the executive level, absntee. Sales hated marketing, marketing hated tech, and everyone hated the executive team.

    We used an o-o-old version of Notes (on our 16-20Mhz Macs with 1MB RAM and a RAM doubler, 2MB if you were buddies with the tech team)...our "database integrity" guys, who researched products and played games all day, came up with the idea of posting a "product of the day" blog. It worked great, and there was good discussion; management let it blossom. Then someone in the call center started posting general questions, insight, complaints, etc, and that became more popular than the product blogs. It became a carthartic thing; people would hate on the company and customers on the company-wide Notes databases. Management, of course, shut it down, which drove morale even lower. Soon, someone set up a rogue database, and the whole thing continued, albeit without managment knowing, and REALLY started ripping on the company. Four months later, which the whole company was shut down and sold to Surplus Direct (which was later bought by Amazon), and nobody was all that surprised.

    So, I guess the point is: it can work, but figure out in advance what you want from it, and decide before implementation how far you'll let your users take it, or you run the risk of it blowing up in your face. You'll lose some productivity, but that's going to happen anyway, either at the water cooler or on Slashdot.

  • The thing is that you can immediately use the forum to find an answer by posting to lots of people at once. If you can toss it up where 30 eyes can look at it, you may get a lot better response than just looking for keywords in the db...

    But I think they're right, it's going to devolve into a bit of a productivity block...

  • Whatever you think of Best Buy, they have a successful internal community in Blueshirtnation.com [slashdot.org]. A google search [google.com] turns up quite a lot of industry praise on those guys. It was even written up the Groundswell book by Forrester.

    If you want your bosses to buy, make sure you give them plenty of examples of other companies being successful at it.

    For me, the biggest business benefit to the call center is knowledge sharing, but you have to be careful because communities need a critical mass in members to be succ

  • ... on what management values.

    In a past career at a large company, we had an extensive Usenet system running within the corporate intranet. It was handy for exchanging best practices among engineers and other employees, finding hidden experts on esoteric topics that then could be consulted within the 'standard' company channels. It was also a great replacement for the 'office water cooler' that extended throughout a company with facilities across the company. Smart managers would lurk on the general newsgr

  • "Charter was well received but there were questions from upper management about how using this type of environment could affect the call center metrics (average handle time, after call wrap up, etc)."

    I recently read (well listened to the audio book) The Goal by Eliyahu M. Goldratt. Very interesting. It pointed out that for the longest time American factories were using the wrong metrics to measure productivity. The were confused by the fact that their measurements were telling them that their efficiency

  • by mrboyd (1211932) on Tuesday October 14 2008, @01:57PM (#25372677)
    Call center is productivity oriented, probably more so than any other activities, and most call center manager can't see further away than AHT (average handling time) and conversion rate/h. It is akin to chain factory work. You have agent working from home, so I assume that they are using either their own pc for the CTI application or a company provided thin client (citrix maybe?).
    In any case, they are home, and unless you have installed tracking software and forces them to leave their webcam turned on how do you know what they are doing? Reading a book, watching tv, breast feeding the little one, etc. I guess you don't and rely on your production report to award incentive to your agents and that so far it worked. Your company has already relinquished a lot of control to shave on the expense of renting and furnishing a hangar in suburbia so another forum is not going to change much on your production ratio issue.

    Point 1: Some of them are probably already browsing other website and chatting with their friends online giving them an opportunity to do it in an environment controlled by the company can only be a benefit. They'll spend more time focused on their work and the company.

    Point 2: Use other metrics to convince upper mgt, what is your current agent turnover? Can you reduce it by fostering a sense of community into your work-alone-at-home-for-a-soulless-company employees? By how much? What is the cost of training a new one?

    Point 3: Are you an inbound CC (where quality matters) or are you selling predatory housing loans and credit card (where volume matters)? Can a "community" effect produce an across the board effect of raising the quality of your services without cost. I.E do you expect your agent to learn trick of the trade from one another which will increase either their quality of services or their conversion rate?

    Point 4: Most agents don't like their job so expect a lot of ranting on your forum. Don't forget to clarify the posting policy with management and your agents or you'll be in trouble when one of them gets fired for complaining too loudly on the forum and sinks everyone else moral, shoot the turnover sky high and the productivity way low.

    I have never heard of a company monitoring the coffee room with camera and mics to hear the dirty jokes made on management so I really believe you should lobby for some partial anonymity. I let you figure out how to implement the "partial" part. And yes you should check with the lawyers... :)
  • I am interpreting the O.P.'s information request as a request for endorsements for a product suitable for building an online community for a call center and not a request for an already active online community for a call center. I am also assuming that the call center is for an ISV. Here are a few recommendations that are my favorites.

    • My favorite open source product for this sort of thing is GForge [gforge.org]. It's got lots of call center friendly features and is also a hit with the coders.
    • The full featured yet non-open source version of GForge is SFEE [collab.net].
    • Please don't mod me down, post nasty replies, or take away my karma points but may I feebly and humbly suggest my own product Code Roller [code-roller.com]? It's not open source yet but it is free (as in beer). Code Roller is not currently a perfect fit for call centers but has lots of great features that are conducive to managing the full life cycle for software development.
    • by pilgrim23 (716938) on Tuesday October 14 2008, @11:21AM (#25370437)

      I work in Tech Support. A small company, about 800 desktops, and a 4 desk tech support center. About 10 years ago I quit smoking. What this has to do with the subject is interesting:
        Back when I was a gasper I would meet by the designated smoking place with the other poor souls. Smokers at that time represented an excellent cross section of the company from the receiving dock to the corporate office. When I showed up for my quick smoke the conversation would always roll around to the computer headache of the day. Hardware, Network, slow response from the branch office, printers that always hang on a word macro, whatever. And 3 or 4 other people would jump in "Hey we have the same problem!"
      This gave me a quick "pulse" of problems that a call log, staff meetings, or all the other tools of the bureaucratic trade never provided. I miss that input.

      • My girlfriend worked as a graphics artist at a medium sized advertising agency (that got gobbled up by Ogilvy), that did a lot of Web stuff. She smokes, and regularly met people from other departments and exchanged ideas and gossip about "what was coming next." The higher management realized that this had positive benefits. Mangers in the advertising business are not necessarily very "intelligent", but they are very "smart" or "sharp", in the "sly" sense of the words. One manager was giving a briefing

        • hey, you can say that you were in a top level management position and oversaw a quarter of all company operations & personnel, or that you were personally responsible for a prodigious 25% increase in office productivity as soon as you joined the company.

          • Actually, he increased productivity by 33%. Before he joined, each employee's average productivity was 33% of the total, so his joining changed it to 133% of the previous total. The next employee will only increase it by 25%.
    • by eln (21727) on Tuesday October 14 2008, @11:27AM (#25370515) Homepage

      the company could promise people dont use it as a place to vent their frustrations with customers.

      Are you trying to imply that call center drones have anything else to talk to each other about? In my experience, pretty much every conversation in a call center revolves around frustrations with the customers. If you don't spend enough time letting off steam by bitching about the customers, you'll eventually just bottle all that frustration in until you show up to work one day with a shotgun.

      Luckily, I quit the call center business before I got to the shotgun stage. Lousiest 6 months of my life.

      • Re: (Score:3, Insightful)

        If set up properly, this kind of forum could actually be used to reduce how pissed you have to get at customers. Depends what's being supported really, but if it's something that goes beyond the level of "reboot your router, wait two minutes, and you should be online again", having a forum where people can post up problems, solutions, and additional feedback can make finding a solution faster and easier, potentially resulting in increased customer satisfaction (lower overall turnaround for solutions, resul

      • I've seen the 'shotgun thing' myself... Well, almost.

        This guy had been working there forever when I started. He loved this dog he had. One day, he comes in and says in monotone (no emotion) "I shot my dog." We stare. He continues, "I put my gun to the back of its head and pulled the trigger. I quit." And he walks out.

        Call center stress is amazing. I felt some of it, but thankfully, never to that degree that it affected me like that. I was only in that job for 6 months, though.

        Even if all the 'commu