When IT Stood Up the Phone Lines: The Pandemic Quarter My Team Kept $14M of Pipeline From Hanging Up

When the offices went dark, the phones did not.

In March 2020, every LogMeIn office shut at the same time. The part of that story that gets told is the one about moving people home — and I have written about that ten-day, 4,000-person scramble elsewhere. This is the other half: not the workforce we moved, but the revenue channel we kept open. Once everyone was home, my team stood up the company’s inbound sales and care lines — expanded the capacity, acquired the licenses, provisioned and trained the people on them, and ran the operation by hand — while call volume spiked straight up.

The lines we stood up carried $4.9M of EMEA pipeline and $9.5M of North America pipeline that quarter, with $2.24M closed-won in EMEA. Call abandon rates fell from 27% to 8% in EMEA and from 63% to 5% in North America. I did not generate that pipeline — the sales and care people who took the calls did. What my organization did was make the channel exist and stay open on the worst possible week to stand one up, and then keep it open for a quarter. The business could not have monetized that demand without it. That is the line I want to hold, because it is the one the org chart hides.

The quarter in numbers

• Pipeline on the lines IT stood up: $4.9M EMEA + $9.5M North America — roughly $14M combined
• Closed-won (EMEA): $2.24M; EMEA pipeline up 57% and closed-won up 111% over the January-to-February run rate
• Inbound sales calls answered: 29,000 in EMEA (up 26,000 year over year) + 40,000 in North America (up 33,000)
• Abandon rate: 27% to 8% (EMEA) and 63% to 5% (North America)
• Staffing IT provisioned onto the lines: 50+ in EMEA, 100+ in North America; the team itself on 15-hour emergency shifts

The spike nobody had a runbook for

The remote-work story is the one everyone rehearses now, so let me set the scene people skip.

In March, demand for remote-work software did exactly what you would expect in the week the world sent everyone home: it spiked hard. For a company that sold meetings, support, and phone systems, that surge landed as a wall of inbound calls — prospects who needed to buy today, customers who needed help now. My team ran the unified-communications platform underneath all of it. We were the first to flag the EMEA traffic climbing, and the first to flag North America.

Here is the uncomfortable part. The people who normally answer those calls were also the people who had just been sent home, onto unfamiliar softphones, in the same forty-eight hours. The sales floor and the care floor did not scale on command. The phone system did — if someone expanded the capacity, stood up enough licensed seats, trained the bodies who would fill them, and watched the whole thing in real time. So that is what we did.

What “stood up the lines” actually meant

This was not a slide. It was an operation.

In EMEA we set up 50+ people on the inbound sales lines and provisioned them through our remote-meeting tooling — onboarding, training, and the FAQ sheets we wrote in real time because none existed. In North America we put 100+ people on the lines via bulk upload, acquired the additional licenses the surge required, and triaged the net-new users and volunteers as they came on. We designed the user guides and data sheets, published them internally, and cleared setup problems across every region so a salesperson on a home connection could actually take a call. The full IT team ran the response on fifteen-hour shifts through the cutover.

Then we watched the one number a buyer trying to reach us actually feels: the abandon rate — the share of callers who hang up before anyone picks up. Every abandoned call that quarter was a customer who needed remote-work software during a pandemic and could not get through. In EMEA we took it from 27% to 8%. In North America, where the volume was heavier and the starting point worse, we took it from 63% to 5% — from roughly two of every three callers hanging up to about one in twenty.

The volume those reclaimed lines carried: 29,000 inbound sales calls in EMEA from March through June, 26,000 more than the same months a year earlier, and 40,000 in North America, up 33,000 year over year. The pipeline followed the answered calls. EMEA pipeline rose 57% over its January-to-February run rate; closed-won rose 111%.

I want to be precise about credit, because the register matters. The sales and care people closed. My organization built and held the channel that let them — on a week when standing one up should have been impossible. That is a different contribution than “kept the systems running.” The systems were running. The business still could not have reached its own buyers without an operations team willing to live on the lines until it could.

The one thing a generalist would get wrong here

If you have never run an operational IT organization through a real emergency, the instinct is to file this under heroics — a team that worked brutal hours and pulled the company through. Pat them on the back, give them the badge, move on. That framing is the mistake. It is the exact mistake that keeps IT priced as a cost center.

Here is the position I will sign that a generalist cannot. I call it Revenue-Constraint IT: when an IT organization controls the operational constraint that gates time-sensitive demand, it is not adjacent to the revenue channel — for that window, it is the channel. Walk the logic. The demand was real and time-boxed: buyers were deciding that week, and a call that abandoned was a sale that went to whoever picked up first. The bottleneck on capturing it was not sales talent or marketing spend; it was whether the phone system could absorb the spike and route it to enough trained people without dropping two-thirds of the callers. That bottleneck sat inside one organization’s span of control. Mine. Move the abandon rate and a large share of the recovered pipeline follows, because every answered call was incremental demand that would otherwise have evaporated.

Could the capacity have come from somewhere else? In theory — a BPO overflow vendor, the telephony provider’s services team, existing sales-ops. Slower, worse, and not on a forty-eight-hour clock without dropping most of the callers. The team that already operated the platform was the only one that could do it on that timeline, at that quality. That is not a support contribution dressed up in revenue language. It is the highest-leverage incremental lever the company had that quarter that sat inside a single org’s control — and the pandemic just made the wiring visible. In a normal quarter, the same organization is doing the same thing — removing friction between demand and the people who close it — and getting filed under overhead because nobody can see the counterfactual. In March 2020 the counterfactual was loud: a 63% abandon rate, in dollars.

What I took out of it

A few lessons have outlived the quarter.

The org chart is not the operating model. On paper, “IT” and “the sales channel” are different boxes. In the emergency, the box that controlled the constraint controlled the outcome — regardless of what the box was named. The leaders who saw that early stopped asking IT to support the response and started asking it to run the part it was best positioned to run. That same instinct lets an IT organization stop being framed as a cost center in the calm quarters too: lead with the outcome you move, not the system you maintain.

Measure the number the customer feels, and put that on the QBR slide. We could have reported uptime — the platform held, ten-million-plus audio minutes delivered across the year. All true, and all beside the point during the surge. The number that mattered was the one a frustrated buyer experienced: did a human pick up before I hung up? The portable move is to name the metric on the customer’s side of the glass — the equivalent of abandon rate for your own shop — and report that, not the green dashboard your team already trusts. Pick the buyer’s number and the business stops needing a translator to understand what IT just did.

Build the playbook in the calm so you can improvise in the storm. We had spent years building toward a voice platform we knew cold — standardizing and migrating offices onto it, work still underway when the surge hit. We were not learning the system from scratch; we were flexing one we were already deep into. The crisis did not create the capability. It cashed in the fluency we had quietly built before anyone needed it. The work that looks like overhead in Q1 is the work that becomes the revenue channel in Q2.

If you want the portable version, here is the test I now run on my own org. Is the demand real and time-boxed? Does the constraint that gates it sit inside my span of control? Does moving that constraint move revenue? Is there a second source that could do it on the same clock? When the answers run yes, yes, yes, no — you are not supporting the revenue channel. You are it, whether the org chart has caught up or not.

None of this requires the emergency. The pandemic was a forcing function, not the lesson. The lesson is that an IT organization is a place where business constraints get removed, and removing the right one at the right moment is worth real money — sometimes the most leverage in the building that quarter. Run it that way on the quiet days, and you will already be standing in the right place when the offices go dark.

The best IT organizations do not wait for the title. They are the ones who, on the week it counts, already operate like the business runs through them — because it does.

Common questions

What happened to LogMeIn’s sales and care lines when the offices closed in March 2020?
When every LogMeIn office shut at the same time in March 2020, inbound call volume for remote-work software spiked sharply. The IT/unified-communications team stood up and ran the inbound sales and care lines — expanding system capacity, acquiring the additional licenses, provisioning 50+ people in EMEA and 100+ in North America onto the lines, and writing the training and FAQ material in real time — so that a workforce which had just gone remote, plus net-new volunteers, could keep taking calls. The full IT team ran the emergency response on 15-hour shifts through the cutover.

How much pipeline followed the phone lines IT stood up during the pandemic quarter?
The lines the IT organization stood up and ran from March through June 2020 carried $4.9M of EMEA pipeline and $9.5M of North America pipeline — roughly $14M combined — with $2.24M closed-won in EMEA. EMEA pipeline was up 57% over its January–February run rate and closed-won was up 111%. The sales and care reps closed the deals; IT built and held the channel that let them reach the buyers.

How much did call abandon rates improve?
Abandon rate — the share of callers who hang up before anyone answers — fell from 27% to 8% in EMEA and from 63% to 5% in North America. In North America that meant going from roughly two of every three callers hanging up to about one in twenty, across 40,000 inbound sales calls answered (up 33,000 year over year).

Why does this make the case that IT can be a revenue channel rather than a cost center?
The constraint on capturing time-sensitive pandemic demand was whether the phone system could absorb a sharp call spike and route it to enough trained people without dropping callers — a constraint that sat inside the IT organization’s span of control, with no alternative that could match it on a 48-hour clock at the same quality. When IT controls the operational constraint that gates demand, moving the abandon rate moves a large share of the recovered pipeline with it. For that window, IT is the revenue channel itself, not a function adjacent to it — what Christian Merkel calls Revenue-Constraint IT.