Over the weekend at a holiday party I had a discussion about a retail store that was interesting. I worked in retail for a long time so I know a good bit about how they operate.
The discussion was in regard to answering the phone. The store has a policy that the phone can't ring more than 3 times. So what they must do is someone, anyone, must answer the phone and put the customer on hold. They then route the call to the correct person.
In practice this creates some problems as most calls are for the commercial sales person in the store (the B2B sales guy). There's only one of him, so all the overflow calls are answered by the cashiers, often while they have a customer in front of them or by managers being dragged off the floor to get and hold a call.
A person at the party who is often frustrated by cashiers being interrupted while they're checking out suggested that the store should hire a person dedicated to answering the phone. For the most part retail stores don't do this. The primary reason is that they know there are times where the cashiers are just sitting there, the managers aren't with customers, the receiving guy has finished up and could probably pick up a call, etc.
They simply don't want to pay an extra person and on top of that they want to maximize every second of the employees they have. This makes good sense in theory, but in practice it's more complicated.
The crux of the issue of course is that the phone systems don't route to available cashiers (staff) they simply ring throughout the store. The managers don't want to be bothered and normally have tons of work, so they almost always direct cashiers or front end staff to answer the phone (though remember the calls are rarely if ever for them).
This leads to multiple customer frustrations. The cashier has to stop processing the sale of the customer in front of them to answer the phone, put the call on hold and notify the B2B sales guy. The customer on the phone is always answered by someone who can't help them and in addition they're often forgotten, mis-routed, etc because once the cashier turns it over or puts it on hold their job is done. The transfer of responsibility for the customer is nebulous at best and so it's not uncommon for the person to sit there having simply been forgotten.
In my opinion what they don't understand is there is value in sometimes paying people to do nothing. There's value in someone sitting there ready to help a customer when one comes in rather than having that person running around doing other "stuff" every time there's a moment free or interrupting them with other tasks when they're already busy.
In this example, a dedicated phone person with good skills could be a useful addition. It free's up the cashiers to help in store customers get checked out fast or answer questions they have.
Another valuable asset of this person is that they would own the call. If they put it on hold they could be keeping the person updated on the status of the B2B sales guy (oh he'll be off in a minute, etc) and ensuring the B2B guy remembers the call is there.
A third upside is that some of your customers end up getting a great experience. Shorter lines up front get people in and out, occasionally the phone person can answer a question without it getting to the B2B guy if he's busy, etc.
This is why with HelpSpot I don't worry about optimizing each second, especially for support. It's OK if once in a while there's some down time, it just means those requests that come in during that time will get a nearly instant response and a great experience. That's probably not the case if the support people are programming an intranet in their down time.