Sixteen agents. One quality supervisor. In 2004, that was the ratio vCustomer reported for its support operation. The industry comparison offered alongside it was 35 agents per supervisor. Here was a company selling the economics of offshore work while putting more people into checking the work. For anyone who has endured an exquisitely unhelpful customer service call, the arithmetic has a certain appeal.
- The work: customer care, technical helpdesks and back-office operations for enterprises.
- The operating bet: use technology to reduce friction, then invest in the people delivering the service.
- The deal: Mahindra Satyam bought the international BPO operations for $27 million in 2012.
A communications engineer finds a queue
Sanjay Kumar had worked at Microsoft and then Teledesic, the satellite communications venture. In 1998, a visit to GE’s facility in Gurgaon helped him recognize the opportunity in Indian business process outsourcing. He founded vCustomer in 1999. The need was already there: companies had sold products, and customers needed help making them work.
The early operation handled email support. Iomega, the data storage company, became its first client in 2000. Chat and voice followed. That progression matters. An email gives an agent time to investigate; a telephone call requires answers while someone waits. Adding a channel changes the demands on the entire operation.
The telephone becomes software
By July 2001, Cisco was naming vCustomer among users of its IP Contact Center solution. Internet Protocol voice offered a different way to organize a distributed business. Instead of treating each location as a separate island of telephone equipment, vCustomer could centralize voice infrastructure and address support and scaling in one place.
A contemporary Cisco case study described the advantages: voice and data could share an infrastructure, maintenance became simpler, and packet routing could work around connection fluctuations. These were useful properties for a company whose customers and agents occupied different continents. The distance remained. Some of the machinery required to manage it became easier to control.
For a buyer, the service was an outsourced operation: people answering inquiries, solving technical problems and handling business processes. The technology helped those people do the job. It also placed vCustomer in competition with both other outsourcing suppliers and a client’s own support department. Moving work outside the company had to justify the handoff.
at vCustomer
reported industry comparison
Saving money takes investment
In February 2004, president Sujit Baksi described the quality investment and an internal technology subsidiary, vCLabs, that developed products and automation for BPO operations. His explanation connected margins to the tools behind the agents. Lower technology costs could coexist with closer supervision.
“We have invested heavily in quality”Sujit Baksi / February 2004
By May, vCustomer was discussing a $10 million to $12 million investment in infrastructure, training and switches during 2004-05, funded through internal accruals. Revenue for the financial year ended March 2004 was reported at $32.5 million, up from $15 million the previous year. Those figures describe an operation putting money into its next stage of growth.
The business mix also complicates the familiar picture of an offshore call center. Voice supplied 65% of business; web-based email and chat supplied 15%; back-office operations supplied 20%. Management wanted a larger back-office share and was considering acquisitions that could bring that work or broaden its geographic reach.
The people inside the network
There was a physical workplace behind this supposedly virtual service. The architects of vCustomer’s Delhi office described a brief covering agent workstations, laboratories, meeting rooms, cafeterias and a server facility. A V-shaped recess made the reception area an architectural pun. In the cafeteria, agents were invited to put graffiti on the walls.
The human side had operational consequences. In a 2008 interview, Kumar described employee satisfaction surveys twice a year and said most senior positions were filled through internal job postings. These were management’s stated practices. They addressed a straightforward service problem: when experienced employees leave, the company loses knowledge that a network upgrade cannot replace.
Kumar also discussed pressure from a rising rupee and weakening dollar, and the difficulty smaller providers faced without the financial cushions of larger firms. An offshore service business lives between currencies as well as time zones. A contract can keep delivering the same work while its economics change.
A broader brief, then a bigger owner
In November 2007, vCustomer announced plans to serve large Indian companies with customer management solutions, including customized interactive voice response, CRM and business intelligence tools. A Mumbai facility was planned alongside existing Delhi and Pune operations. The proposition was expanding toward helping enterprises manage customer interactions across channels.
Its later company description combined sales outreach, customer support and technical helpdesks with a cloud Customer Interaction Platform and work-at-home delivery. Retail, consumer technology and communications were central markets. Microsoft appeared in Cisco’s account; HP was named in contemporary reporting. These were businesses with products that generated a continuing need for assistance.
On March 7, 2012, Mahindra Satyam announced the $27 million purchase of vCustomer’s international operations. The buyer emphasized retail and consumer technology expertise and stronger technical support capabilities. Mahindra Satyam subsequently merged with Tech Mahindra. The acquired US subsidiary, vCustomer Services LLC, merged into Tech Mahindra (Americas) in 2015.
What survives the headset
The useful lesson is an operating choice. Bring communication channels together, automate repetitive work, and preserve enough supervision to catch problems as volume grows. This is an interpretation of vCustomer’s history, rather than a promise that its particular ratios suit every support team.
The conditions matter: dependable connectivity, teachable processes and enough repeatable demand to support training and infrastructure. Currency shifts and staff turnover can consume expected savings. For a manager evaluating outsourced support, vCustomer’s story suggests a better opening question than the price of an agent: what system will help that agent resolve the customer’s problem?