A large customer support organization signals that a product is too complex, hard to onboard, or buggy. Instead of optimizing the support function, companies should focus on improving the product to the point where extensive human support becomes unnecessary.
Related Insights
Businesses often create multi-tiered maintenance plans, believing more options are better. However, this complexity overwhelms consumers and makes it harder for technicians to sell. A simplified, single-option plan often leads to higher adoption rates because it's easier to understand and pitch.
The obsession with removing friction is often wrong. When users have low intent or understanding, the goal isn't to speed them up but to build their comprehension of your product's value. If software asks you to make a decision you don't understand, it makes you feel stupid, which is the ultimate failure.
The best filter for automation vs. human support is the customer's emotional state. High-stress scenarios, even if procedurally simple, demand human empathy to maintain brand loyalty. Reserve automation for low-sensitivity, routine queries.
When a customer asks a simple question, providing an overly detailed answer is counterproductive. This "waterboarding by help" frustrates the buyer, who just wants their specific problem addressed. At best it wastes time; at worst, it actively convinces them not to purchase.
While customer feedback is vital for identifying problems (e.g., 40% of 911 calls are non-urgent), customers rarely envision the best solution (e.g., an AI voice agent). A founder's role is to absorb the problem, then push for the technologically superior solution, even if it initially faces resistance.
When products offer too many configurations, it often signals that leaders lack the conviction to make a decision. This fear of being wrong creates a confusing user experience. It's better to ship a simple, opinionated product, learn from being wrong, and then adjust, rather than shipping a convoluted experience.
Saying yes to numerous individual client features creates a 'complexity tax'. This hidden cost manifests as a bloated codebase, increased bugs, and high maintenance overhead, consuming engineering capacity and crippling the ability to innovate on the core product.
Vendors often create overly sophisticated partner programs, believing more features add more value. However, complexity hinders adoption because partners lack the time to understand intricate systems. Simplicity is not just a preference; it is a prerequisite for effectiveness. A straightforward program will always outperform a complex one.
Customers don't differentiate between sales and support; they just want answers. AI makes it economically viable to handle both inquiry types through a single point of contact. This resolves the common issue of customers calling sales lines for support issues simply because they know a person will answer.
During due diligence, analyzing support cost margins is a powerful heuristic. A company can claim to have a great product, but if its gross margins on support are low, it reveals underlying flaws. The goal should be to improve the product to "eliminate the reason for the call altogether."
