The Call Center Study Nobody Talks About
In 2007, Adam Grant ran a study at a university call center. The callers were raising scholarship funds. They were burning out. Response rates were low and morale was lower.
Grant did one thing: he brought in a scholarship recipient — someone whose education had been funded by the very money these callers were raising — and had that person speak to the team for five minutes.
That's it. Five minutes. One conversation. One person in the room.
The callers who heard from the scholarship recipient increased their effort by 142% and their revenue by 171% over the following month. The control group, which received no visit, showed no change.
Nothing else was different. Same scripts. Same training. Same manager. The only variable was proximity to someone whose life the work had actually touched.
Why This Should Trouble Every CSR Professional
Most corporate volunteer programs are designed to maximize throughput. Hours logged. Employees deployed. Tasks completed. The question driving design is almost always: how do we get more people to do more things?
That's the wrong question. And the call center study shows why.
If a five-minute conversation can produce a 171% increase in results, the bottleneck was never effort. It was meaning. The callers always had the capacity to work harder. What they lacked was a reason to care — a direct, felt connection to the person on the other end of the chain.
Proximity is that connection. And most volunteer programs are systematically designed to prevent it.
The Design Flaw
Here's how most corporate volunteer programs work: employees show up, perform a task — sorting food, building beds, tutoring students — and leave. The task is completed at arm's length from anyone whose life it affects. Volunteers rarely meet the people they're helping. When they do, the interaction is brief, structured, and often scripted to stay positive.
This isn't an accident. It's a design choice — usually made for reasons of efficiency, liability, or comfort. And it's the primary reason most corporate volunteer programs don't produce the transformation they promise.
The theory of change assumed by most programs is this: doing good things makes people feel good, which makes them better employees. But that theory skips the most important step. It assumes that action alone produces meaning. The call center study shows it doesn't. Meaning requires contact. It requires proximity to the human consequences of your effort.
What Proximity Actually Does
Proximity works by making abstract stakes concrete. When a volunteer meets a person their work has affected — or could affect — several things happen simultaneously:
Identity becomes salient. The volunteer stops being an employee doing a task and becomes someone whose actions have consequences for another person. That shift in self-perception changes behavior.
Motivation internalizes. External motivation (showing up because your company asked you to) gives way to internal motivation (showing up because you care about the outcome). Internalized motivation is more durable and more powerful.
Effort scales naturally. Once volunteers understand what's at stake for a real person, they don't need to be pushed to work harder. They push themselves.
This is why the scholarship recipient's five-minute visit produced a 171% revenue increase. The callers didn't learn anything new. They didn't receive better training or a higher commission. They simply became able to see, clearly, who their work was for.
The Implication
If proximity is the primary design variable in volunteer program effectiveness, then every program design decision should be evaluated against one question: does this bring volunteers closer to the people their work is for, or does it push them further away?
Most programs, evaluated honestly against that question, fail.
The good news is that proximity can be engineered. It doesn't require scrapping existing programs. It requires changing one thing: how you structure the moment of contact between the volunteer and the person whose life the work touches.
That's what the Brief-Guide-Debrief cycle is designed to do. But before we get there, we need to understand what happens when the Debrief doesn't happen — which is the subject of Part 2.