Not Everyone is Worth Supporting

Balancing Support Costs and Customer Value

Providing help to a customer is never free; every ticket, every call, and every email comes with a price tag. The most effective organizations treat support like any other expense that can be measured and managed. They know that a small group of high‑value customers can offset the cost of caring for a larger, less profitable segment. That balance is critical: if the cost of supporting a customer exceeds the profit the customer brings, the business loses money on each interaction. Making that distinction early on keeps a company profitable and its support budget in check.

Take Amazon as an example. If you call their customer service line, you often end up with a long hold or a brief wait. Why isn’t Amazon offering an easy 800 number for every shopper? The answer lies in their razor‑thin margins. Email support costs less to maintain than live phone lines, so Amazon funnels the bulk of its help requests to the inbox. The company keeps its costs low by limiting the ways customers can reach them, and by ensuring that every call that does go through is handled efficiently. That strategy works because Amazon’s average profit per transaction is large enough to absorb the cost of occasional phone support, but it would be disastrous for a retailer with slimmer margins.

Decisions about how much support to provide, and who receives it, are often made on a website. Yet most corporate sites lack a single person with the real authority to decide what content stays online and what goes. When no one owns the page, compromises creep in. A department may add a feature or a page just to keep the lights on, another might push a promotional banner because it feels trendy, and a third might preserve legacy content because nobody has the bandwidth to delete it. The result is a site that is a patchwork of updates, half‑finished features, and stale pages. The audience, in turn, sees a promise that can’t be met, because the support structure that should back it up is fragmented.

That fragmented approach shows up in two ways. First, the site over‑promises. A marketing team may claim “24‑hour support” while the technical team can only deliver a backlog of a few days. Second, the site under‑delivers. If users click on a link that is supposed to show product specs and instead see a 404 page, the trust erodes quickly. Every missing piece of support is a missed chance to keep a customer loyal and to collect data that could help the business grow. The net effect is a loss of revenue and a brand that feels unreliable.

To avoid this, companies need a clear owner for every page or service. That owner must be empowered to approve or cancel content based on real metrics: traffic, conversion rates, support ticket volume, and customer satisfaction. With a dedicated steward, the site can be trimmed to only what adds value, ensuring that the support promise is honest and that resources are not wasted on pages that never serve a purpose.

Why Unstructured Web Content Backfires

In an era where information is abundant, the problem is no longer a lack of content but a glut of it. Frequently Asked Question (FAQ) pages are a prime example of how too much information can become a burden. When a software company turns every minor glitch into a new FAQ entry, the intranet turns into a labyrinth of disconnected help topics. New employees spend hours scrolling through outdated or poorly written answers that do nothing to solve their problem. The knowledge base becomes a maintenance nightmare because each entry needs to be updated, merged, or retired, yet there is no systematic review process. As a result, users avoid the FAQ entirely, preferring to ask a coworker for a quick fix instead of wasting time searching.

Similar problems plague many government portals. Governments create thousands of pages to satisfy a sense of transparency and accessibility. They claim that “information is free” and that citizens have a right to everything. The downside is that citizens are overwhelmed by a sea of data. The pages are rarely organized around the user’s needs; they are organized around the government’s desire to archive everything. When a driver wants to renew a license, they may have to navigate through a maze of unrelated policy documents, legal notices, and generic public‑service announcements. The result is confusion, frustration, and an under‑utilized portal.

Another angle is the “freedom of information” versus “freedom from information” debate. Governments often adopt Freedom of Information laws to reveal data, but they rarely consider the cost of filtering or contextualizing that data for the average user. Information overload is a subtle form of administrative burden that can cost citizens time, mental energy, and money. An over‑crowded website, like a newspaper that prints every story in full, forces users to sift through noise to find the few headlines that matter.

Targeted content is the antidote. If a website is designed to reach a specific group of users, it can prioritize the most valuable information for that group. For example, a healthcare portal might serve a distinct version for patients, a separate one for doctors, and a third for insurers, each with tailored pages and support options. By limiting the scope, the site reduces the risk of confusion and improves the user experience. The underlying principle is the same: deliver what matters, no more, no less.

When a site becomes overloaded, the cost of managing that overload becomes higher than the benefits it provides. Each new page requires design, development, content creation, and ongoing maintenance. If those pages rarely attract traffic, the return on investment drops sharply. In the long run, an organization that invests in a lean, focused web presence saves money and builds stronger relationships with its users.

Targeted Digital Services: Delivering Value Where It Matters

People’s attention spans are finite, and that fact should shape how we build and maintain digital services. If a website offers every possible resource, users become overwhelmed, and their ability to find what they need is reduced. The paradox of abundance means that more information does not equal more value. Instead, the most efficient use of resources is to concentrate on the services that truly matter to the most important audience segments.

Start by mapping your audience. Which customer personas actually engage with your site? Which ones generate the highest lifetime value? For each group, determine the services they use most often and the problems they face most frequently. This segmentation turns an ambiguous “all‑customers” strategy into a clear “who‑does‑what” plan. For instance, a telecom provider might discover that small‑business owners use their portal for billing and support, while residential customers focus on data usage and plan changes. By knowing where the value lies, the company can allocate its support budget accordingly.

Next, prioritize the services that have the highest impact on revenue and customer satisfaction. This is not the same as offering the most popular feature; it is about measuring how each service affects churn, upsell potential, and net promoter scores. A service that resolves a common complaint quickly can reduce support tickets, free up staff time, and improve customer retention. In many cases, a single well‑executed support flow can outweigh the benefits of dozens of lower‑impact services.

Once you have a prioritized list, implement a targeted content strategy. Each high‑impact service gets its own dedicated page or portal, written in clear language and organized around the customer’s journey. Use data to decide which FAQs to keep, which tutorials to create, and which legacy pages to retire. A lightweight, clean design with intuitive navigation reduces friction. For the remaining low‑impact services, provide a brief “learn more” link that points to a comprehensive knowledge base or an external resource, but keep the main user experience uncluttered.

Finally, treat the website as a living product that needs continuous refinement. Set up a schedule to review traffic, support tickets, and user feedback for each segment. If a service no longer drives revenue or if a new customer segment emerges, adjust the content accordingly. This iterative approach keeps the site aligned with business goals and user needs.