“Customer service shouldn’t just be a department; it should be the entire company.”
Tony Hsieh repeated this principle while explaining the culture of Zappos around the publication of Delivering Happiness in 2010. The company trained employees across roles in customer service because the brand promise could not be delegated to a call center. Merchandising, technology, logistics, hiring, and leadership all shape what happens when a customer places an order or needs help. Service is the cumulative result of the system, not the personality of the person who answers the phone.
The idea changes how problems are assigned. A late delivery may surface in support, but its causes may lie in inventory data, warehouse design, carrier choices, or a promotional promise. If only the service department owns the outcome, employees can apologize without authority to remove the cause. Company-wide service gives every function a line of sight to the customer and treats recurring contacts as design information. The goal is not merely to handle complaints gracefully but to reduce the need for them.
There is a risk of turning “everyone serves” into “everyone must be available all the time.” Clear roles, specialist expertise, and sustainable staffing still matter. Customer focus should not erase boundaries or encourage employees to make unsupported promises. Nor does delight require extravagant gestures for every transaction. Reliable basics, honest expectations, and easy recovery usually create more trust than occasional spectacle. A service culture needs operational discipline beneath its warmth.
Today, automated assistants and self-service tools can resolve simple needs quickly, but they also expose whether the underlying organization is connected. A bot that blocks escalation or repeats inaccurate policy makes fragmentation visible. Leaders can review customer journeys across departments, share contact reasons with product teams, and give humans authority for exceptions. Hsieh’s sentence remains a systems test: when the customer encounters the company, do its functions behave like one responsible organization or a chain of departments passing the problem along? A company-wide service review can follow one common contact from promise to resolution. Marketing sets an expectation; product and policy determine what is possible; technology exposes options; logistics delivers; finance handles refunds; support manages the conversation. Mapping the chain shows where ownership breaks and where employees compensate manually for system flaws. Fixing the upstream cause often saves more than adding another script downstream. Hsieh’s formulation is therefore not only cultural. It is an argument for end-to-end process design around the customer’s outcome rather than the company’s departmental boundaries. Shared accountability turns every contact into a chance to improve the system.
Hsieh used the line while describing Zappos around the 2010 publication of Delivering Happiness.
The company trained employees broadly in service because culture and operations, not one department, produced the brand experience.
Every function influences customer outcomes, including product, technology, logistics, policy, and leadership.
Company-wide responsibility still needs clear roles, sustainable boundaries, and disciplined delivery of the basics.
Automated support can magnify fragmentation when systems block escalation or repeat inaccurate policy.
Cross-functional ownership turns customer contacts into information for fixing causes, not merely managing symptoms.
Explore more "Quotes of The Day"
Discover more notable quotes from influential voices across politics, science, business, technology, sports, and culture. Each quote offers insight into how ideas, beliefs, and decisions shape the world around us.