1. TL;DR — Defeating a salesperson drops no XP
Imagine having a serious consultation with a large recruiting service. The adviser gives a surprisingly sensible conclusion:
“You do not need to change jobs right now. Build stronger results where you are, and come back when a move makes sense.”
Good advice. Trust goes up.
About a month later:
📞 “How are things going? Would you like another consultation?”
In another channel, you talk with one person and receive a call the next day from someone else:
📞 “Would you be interested in this other service?”
The customer has one thought:
I talked to you yesterday.
Inside the company, these may be separate departments, products, KPIs, and dialing lists. To the customer, however, they are one company.
Now add a workplace manager whose rule is:
“Answer every phone call!”
Every sales call is answered. Better yet, the manager does not simply decline. The manager starts a debate:
“What value would your service actually create?”
Maybe it is an impressive debate. As operations design, it is a strange sport.
You do not gain corporate XP for defeating a salesperson.
If phone handling consumes roughly 100 hours per year, that is about 12.5 eight-hour workdays or 2.5 forty-hour workweeks. A 100-hour improvement opportunity is sitting in plain sight while the organization reviews salespeople one call at a time.
This article treats the problem not as “annoying people,” but as a system of information sharing, functional silos, synchronous interruption, KPIs, and process design.
2. “Do not change jobs yet” followed by Want another meeting?
The original adviser may have delivered excellent customer experience. A recruiting business earns money when people move, so telling someone not to move yet can signal that the adviser is optimizing for the user rather than the immediate transaction.
The breakdown happens later, when another touchpoint behaves as if that context never existed.
We should not claim that the company “has no shared data.” We cannot see its internal architecture.
Several mechanisms are possible:
- The consultation record lives in another system.
- The record is centralized but not visible to another team.
- It is visible, but dialing-list logic does not use it.
- “Low current intent” does not suppress marketing for another service.
- Each team optimizes its own KPI, while no one owns the question, “Should the company contact this person now?”
A common failure mode is therefore not missing data, but data that has no power over workflow.
A CRM can say “not looking to move,” yet the morning dialer can still generate a hundred names.
The CRM exists. The note exists. The call exists. What was missing was the stop condition.
3. The customer sees one company; the organization sees twenty departments
Silos are dangerous precisely because each unit can look rational from the inside.
- Career advisers optimize consultations.
- Another service optimizes activation.
- Sales optimizes contacts.
- A call center optimizes dialing volume.
Each dashboard can turn green while the customer sees this:
Yesterday: one-hour conversation
Today: another service pitch
Next month: “Want another consultation?”
Customer: Did you delete my save file?
McKinsey argues that customer experience is inherently cross-functional and that dominant functional silos can optimize individual touchpoints without optimizing the end-to-end journey.[4]
A Salesforce vendor survey likewise reported substantial CRM fragmentation and respondents associating silos with worse customer/prospect experience.[5] That does not prove the architecture of any particular recruiter; it shows the pattern is common enough to be a recognized operating-model problem.
Customers do not buy the org chart.
“Different department” may be internally accurate and externally irrelevant.
4. A phone call is an API that forces a human into synchronous mode
Email can wait. Chat can be muted. A phone call is different.
When it rings, the request is effectively:
Allocate your attention to me now.
And the first words do not tell you whether the call is important.
“Hello.”
“This is X from Y.”
Still potentially important.
“I’m calling to introduce our new service—”
Now it is clearly sales, but the interruption has already happened.
Interruption research identifies a resumption lag when people return to a primary task and shows that rushed resumption can increase errors.[1] A 2021 systematic review and meta-analysis found that interventions designed to reduce interruption costs improved primary-task accuracy overall and reduced resumption lag.[2]
A well-known experiment also found an important nuance: interrupted participants sometimes finished faster, but reported more stress, frustration, time pressure, and effort.[3]
So “the work still got finished” does not mean the interruption was free. People may be sprinting to recover the lost ground.
A three-minute sales call can cost more than three minutes.
5. “Answer everything!” — the 100-hour manual webhook
Let us create a fictional composite character: Director Answer-Everything.
📞 Ring.
Director: “Answer it!”
Employee: “Hello?”
📞 “We would like to propose a utility-cost reduction service—”
Employee: “It was sales.”
Director: “Get back to work!”
Who interrupted the work?
“Answer every call” sounds polite and risk-averse. Operationally, it converts every external event into a human interruption.
A webhook would normally have filters:
- current supplier → pass
- candidate/customer → pass
- urgent issue → pass
- unknown number → identify first
- obvious cold sales → terminate at the edge
The answer-everything policy has no condition:
if phone_rings:
interrupt_everyone()
At 100 hours a year, that is 12.5 eight-hour days or 2.5 standard workweeks.
Not all of those hours are waste. Important calls exist. The improvement task is not “abolish phones”; it is to stratify the 100 hours and remove low-value interruptions.
That is basic quality improvement.
6. Debating every salesperson: the corporate esport nobody asked for
Director Answer-Everything has another skill. A salesperson calls, and instead of declining, the boss begins the boss fight:
“What value does this create?” “What is the ROI?” “Why is this better than our current method?”
Sales responds:
“Let me first explain our strengths—”
Round one begins.
Fifteen minutes later:
“We don’t need it.”
WINNER: nobody.
If the product is genuinely under consideration, those questions are valuable. If the findings are recorded as market intelligence or supplier evaluation, it can be real work.
But if purchase probability was near zero and the only output is “I defeated the pitch,” the process is hard to defend.
| Metric | Result |
|---|---|
| Debate quality | Maybe high |
| Call duration | Long |
| Lead time | Worse |
| Primary-task interruption | Yes |
| Reusable deliverable | Almost none |
| Value added | Near zero |
| Audience | None |
| XP drop | None |
The salesperson is not a raid boss. There is no treasure chest.
7. Translate “100 hours” into business units and it stops being funny
“Phone calls are annoying” is an opinion.
“About 100 hours per year” is an improvement problem.
At that scale:
- about 12.5 eight-hour person-days
- about 2.5 forty-hour workweeks
- possible additional resumption time after each interruption
- multiplied cost when several employees become involved
The useful metric is not call duration alone. Consider:
total call minutes + unnecessary-call rate + duplicate contacts per customer + resumption lag + loss to interrupted core work.
Cutting 100 hours to 50 does not merely save time. It returns 50 hours to procurement, engineering, recruiting, customer service, training, improvement work, or whatever the organization actually exists to do.
It is like fixing a compressed-air leak in a factory: each hiss seems small; the annual total is not.
8. Better design — do not become better at rejecting sales; prevent low-value calls from reaching humans
For an individual, a spam-call blocker is rational. For an organization, reflexes should become rules.
8-1. Turn customer state into control logic, not a decorative note
Fields such as:
career_intent = lownext_contact_after = 90 daysmarketing_phone = nopreferred_channel = emailrecent_substantive_contact = yes
should actually change dialing eligibility.
A useful record does not merely describe reality; it changes system behavior.
8-2. Add cross-department suppression
If Team A had a substantial conversation yesterday, Team B should not automatically cold-call today. Recent-contact suppression, shared contact reasons, and an end-to-end journey owner can prevent locally “correct” behavior from becoming globally absurd.
8-3. Make asynchronous contact the default
Low-urgency information should start with email, app notification, or another asynchronous channel. Reserve calls for emergencies, scheduled conversations, real-time coordination, or people who prefer calls.
Do not force humans into synchronous mode without a reason.
8-4. Replace “answer every call” with “do not miss valuable calls”
Those are different policies.
The first maximizes input. The second preserves valuable input while filtering noise.
Reception, caller databases, spam screening, IVR, voicemail, SMS, and callback rules can create multiple filters.
8-5. Do not win the sales call
If adoption is clearly unlikely:
“No thank you. We do not need sales calls. Goodbye.”
End.
In operations, a good exit condition is sometimes more valuable than being right for fifteen minutes.
9. Conclusion — do not defeat the salesperson; defeat the waste
The funny part is that each person may be locally reasonable.
The original adviser gave good advice. Another team may simply have followed its list. The workplace manager may have wanted to avoid missing important calls and may have believed in rigorously evaluating proposals.
Add the local optimizations together, however, and you get:
Call yesterday’s customer again. Make everyone answer cold sales. Debate the caller for fifteen minutes. Lose roughly 100 hours a year.
As a system, it becomes comedy.
The improvement target is not “learn to destroy sales pitches more efficiently.” It is:
Who should receive which call, for what reason, at what time? Where should low-value calls be filtered? How should customer state change company-wide behavior?
Final QC scorecard:
Debate quality: high
Process capability: low
Lead time: long
Value added: near zero
Recommended countermeasure: defeat the waste, not the salesperson
That is where the XP is.
