“We are monitoring the system and making sure that any resource and any expertise required for anything that we see is checked every two hours, 24 hours a day,” he said.
Some of the people who called in to express their frustration identified themselves as software engineers and accused Cubic and the MTC of failing to properly test next generation Clipper before releasing it to the public.
“These were entirely preventable failures. I’m a software engineer and computer infrastructure engineer with a decade of experience. This launch to me speaks to a lack of technical oversight from the Metropolitan Transportation Commission,” said Evan Tschuy, a founder of the site Hiking by Transit.
The severity of the glitches is causing a significant number of calls to Clipper’s customer service center to go unanswered. Between Dec. 10 and Jan. 15, the customer service center received some 47,000 calls to agents, nearly four times the amount the call center was originally contracted to handle, according to MTC staff. With a daily average wait time of around 15 minutes — down from over an hour when the upgrade first launched — 23% of Clipper customers are hanging up before reaching a customer service agent.
Patrick McGowan with WSP USA Services, Inc, which handles customer service for next generation Clipper, said there are 46 full-time staff currently working at the Clipper call center, and that the company planned to hire 10 additional part-time staffers to handle the increased call volume they are experiencing.
Representatives from some transit agencies suggested that Cubic should be held financially liable for lost revenue due to the ongoing glitches. But Mulligan, with the Golden Gate Bridge Highway & Transportation District, lamented the damage the fiasco had caused to his riders.
“We have a relationship with them, and you broke that relationship, and my customer service staff can’t fix it,” Mulligan said.