Why We’re launching the Customer Support Black Hole Survey

We’ve just launched a new survey into customer support failures because existing research has made one thing very clear: responsiveness matters. But it has also left one major question unanswered – what actually happens to people when support systems appear reachable but do not meaningfully respond?

Customer support has never appeared more available.

Most organisations now present customers with multiple ways to get in touch: help centres, contact forms, ticket portals, chatbots, email addresses, live chat widgets, social media channels, community forums, account dashboards, automated update systems and escalation routes.

On the surface, that looks like progress. More doors should mean easier contact. More channels should mean better access. More automation should mean faster answers.

But ReplyResearch is launching the Customer Support Black Hole Survey because the experience described by many customers appears to be moving in the opposite direction. People are not simply struggling to find a contact route. They are struggling to get a useful response after contact has already been made.

That distinction matters.

A company can be contactable without being responsive. A support system can acknowledge a message without resolving anything. A chatbot can create the appearance of engagement while blocking access to ownership. A ticket number can prove that an issue entered a system without proving that anyone has taken responsibility for it.

The Customer Support Black Hole Survey has been created to investigate that gap.

The research already told us responsiveness matters

ReplyResearch is not starting from the assumption that customer support responsiveness is an unstudied topic. It is not. In fact, one of the reasons we felt duty bound to undertake this survey is that existing research has already established the importance of responsiveness with considerable force.

The classic SERVQUAL model, developed by Parasuraman, Zeithaml and Berry, placed responsiveness among the core dimensions of service quality. In that tradition, responsiveness is not merely speed for its own sake. It is the willingness to help customers and provide prompt service. That remains an important foundation because it treats response as part of service quality, not as an administrative afterthought. (dl1.icdst.org)

More recent customer service research continues to reinforce the same point. Salesforce’s State of Service material emphasises that customer expectations are rising and that customers “want superior service, and they want it now.” Salesforce also reports that customers are more likely to purchase again when companies meet service expectations. (Salesforce)

Zendesk’s 2025 CX Trends research, based on surveys of more than 5,000 consumers and more than 5,500 business respondents across 22 countries, highlights the extent to which customer experience is now being reshaped by AI, automation, personalisation and expectations of more human-feeling service interactions. (d1eipm3vz40hy0.cloudfront.net)

HubSpot’s service research has also repeatedly pointed to the importance of rapid response. Its State of Service material cites research showing that 90% of customers rate an “immediate” response as important or very important when they have a customer service question, while 60% define “immediate” as 10 minutes or less. (HubSpot)

Operational and benchmarking research adds another layer. Gartner describes customer service benchmarking across hundreds of customer service and support metrics, while Freshworks’ customer service benchmark reporting covers metrics such as first assignment time, first response time and response SLA performance. (Gartner)

This body of work is valuable. It has helped define responsiveness, measure parts of it, benchmark it and connect it to customer satisfaction, loyalty, service quality and operational performance.

But it also raises questions that existing research does not fully answer.

The unanswered question: what happens inside the support black hole?

The problem ReplyResearch wants to investigate sits between several established ideas: reachability, contactability and responsiveness.

Reachability is often treated as the ease with which customers can get through to a contact centre or support channel. Contact-centre reachability metrics are useful because they help organisations understand whether customers can access the system in the first place. (VCC Live)

Contactability is related but not identical. In customer communication and marketing contexts, it often concerns whether an organisation can successfully contact or communicate with a customer, using accurate data, appropriate channels and effective communication practices. (dunnhumby)

Responsiveness goes further. It asks whether the organisation is willing and able to help, respond promptly, take ownership and move the issue towards a useful outcome.

The gap we are investigating is what happens when the first two appear to exist but the third does not.

A customer may be able to find a contact form. They may receive an automated acknowledgement. They may be given a ticket number. They may be told that their issue has been escalated. They may receive a chatbot response, a holding email or a promise that someone will be in touch.

And yet, from the customer’s point of view, nothing meaningful happens.

That is the support black hole.

It is not simply “slow support”. It is not simply “bad service”. It is a specific form of response failure in which the customer enters a communication system and then experiences silence, circularity, deflection, delay, automation, failed escalation or unresolved ownership.

Existing research helps us see why this matters. It tells us that responsiveness is important, that response time affects satisfaction, that service teams measure large numbers of operational indicators, and that customers increasingly expect faster, more coherent service. But it does not fully tell us what customers experience when support systems technically receive an enquiry but do not produce a useful response.

That is the missing evidence.

Why existing research raised the issue but could not close it

Much of the available research is necessarily system-facing.

It is designed to help organisations manage support operations. That is useful. Companies need to know how many tickets they receive, how quickly agents respond, how queues behave, how SLAs are met, how customers rate interactions, how many contacts are resolved at first contact and how support workloads are distributed.

But the customer support black hole is often visible only from the outside.

A dashboard may show that a ticket exists. It may show that a first response was sent. It may show that an automated reply was generated within seconds. It may show that the customer was routed to a help article, transferred to another department or moved into a pending state.

What it may not show is whether the customer actually received help.

This is where the distinction between response and responsiveness becomes important.

A response can be procedural. Responsiveness is substantive.

A response can say, “We have received your enquiry.” Responsiveness means the organisation understands the issue, accepts ownership where appropriate, communicates clearly and moves the matter towards resolution.

A response can be generated automatically. Responsiveness requires the system to be accountable for the customer’s need.

A response can be fast and still be useless.

That is why first response time alone cannot answer the question ReplyResearch is asking.

Existing operational research points to hidden failures

Some operational research already suggests that support systems may hide important forms of failure.

For example, research into silent abandonment in contact centres found that customers may leave a text-based support queue without the system immediately recognising that they have done so. The study estimated that 30% to 67% of abandoning customers may abandon silently, creating both measurement uncertainty and operational inefficiency. (arXiv)

That finding is valuable because it shows how customer experience can disappear from the system’s view. The organisation may still be measuring the queue, but the customer has already given up.

Another study on contact complexity in customer service notes that complex issues routed to less experienced agents can lead to repeated contacts and multiple transfers. It also points out that defining contact complexity is itself difficult. (arXiv)

That matters because many support black hole experiences do not begin with a simple failure to answer. They begin when a system cannot properly classify, route, own or resolve an issue. The customer is not necessarily ignored immediately. They may be handled, transferred, delayed, escalated, de-escalated, reassured, re-ticketed and re-routed – while still getting nowhere.

This is the kind of lived evidence the ReplyResearch survey is designed to collect.

The problem is no longer just whether companies are reachable

The question “Can customers reach the company?” is still important.

But it is no longer enough.

Many organisations are reachable in the shallow sense. They provide a way to submit a message. They provide a channel. They provide a form. They provide a bot. They provide an address. They provide a portal.

The new question is whether those routes lead to meaningful organisational response.

That is where the customer experience often breaks down.

A company may have eight front doors and no functioning route to ownership. It may encourage customers to “get in touch” while designing systems that make it hard to reach a person. It may offer live chat that only provides scripted deflection. It may advertise support that exists only during narrow hours. It may create tickets but fail to progress them. It may respond quickly at first and then disappear. It may repeatedly ask the customer to restate information already provided. It may separate sales responsiveness from support responsiveness, answering prospects quickly while leaving existing customers waiting.

Existing research into reachability, contactability and responsiveness points towards these problems, but it does not fully map them from the customer’s point of view.

That is the spur for this survey.

Why ReplyResearch felt duty bound to investigate

ReplyResearch studies responsiveness.

That means we cannot treat customer support failure as merely an operational inconvenience or a private frustration. When people cannot get meaningful answers from organisations they depend on, responsiveness becomes a public evidence issue.

The unanswered questions are too important to leave vague.

How often are customers ignored after submitting support requests?

Which channels create the strongest illusion of help while producing the weakest outcomes?

How often do automated systems block rather than assist resolution?

How often does a fast first response hide a long period of non-resolution?

What kinds of issues are most likely to disappear into support systems?

Which sectors, company types or support models produce the most serious response failures?

How do customers experience repeated escalation, ticket closure, canned replies, handoffs and silence?

At what point do people stop believing that the organisation is trying to help?

These are not questions that can be answered by looking only at advertised contact channels. They cannot be answered by counting how many doors a company offers. They cannot be answered by first response time alone.

They require accounts of what actually happened.

That is why ReplyResearch is asking people to contribute their experiences.

What the survey is designed to find

The Customer Support Black Hole Survey is designed to gather evidence about situations where people tried to get help from a company or organisation and did not receive a timely, useful, accountable or meaningful response.

The survey is especially interested in experiences involving:

ignored enquiries
unanswered support tickets
delayed replies
circular support loops
chatbot dead ends
failed escalation
repeated requests for the same information
automated acknowledgements with no follow-through
premature ticket closure
handoffs between teams with no ownership
support portals that make progress hard to understand
companies that appear easy to contact but difficult to get help from

The purpose is not simply to collect complaints. It is to identify patterns.

A single bad support experience can always be dismissed as an exception. A wider body of evidence can show whether the same patterns are recurring across companies, sectors, channels or systems.

That is the point of the survey.

What ReplyResearch hopes the evidence will show

ReplyResearch wants to understand whether the modern support environment is producing a new kind of responsiveness gap.

Not a gap between companies that have support channels and companies that do not.

A gap between companies that are contactable and companies that are genuinely responsive.

Existing research already tells us that speed, service quality, responsiveness and customer experience matter. It tells us that organisations are investing heavily in customer service systems, AI, automation, benchmarking and operational measurement. It tells us that customers expect faster and better responses. (Zendesk)

But the unanswered question is whether the expansion of support channels has actually improved the customer’s ability to get a useful answer.

That is what ReplyResearch now wants to investigate.

The survey will help us look for evidence of repeated failure types: silence, delay, deflection, automation failure, lack of ownership, unresolved loops, false escalation and the difference between being answered and being helped.

From private frustration to public evidence

One reason support black holes persist is that they are often experienced privately.

A customer waits. They chase. They try another channel. They repeat themselves. They receive a holding reply. They are told the matter has been escalated. They wait again. Eventually, they give up, switch provider, complain publicly, absorb the loss or accept that nothing more will happen.

From the organisation’s point of view, that may become a closed ticket, an abandoned contact, a low-priority case or no visible event at all.

From the customer’s point of view, it is evidence of failure.

ReplyResearch wants to bring those experiences together so they can be examined as evidence rather than isolated frustration.

That is why the Customer Support Black Hole Survey exists.

It is an attempt to answer the questions raised – but not yet answered – by the existing research on reachability, contactability and responsiveness.

Customers have more ways than ever to knock on the door.

The question now is what happens after they knock.

Take part in the Customer Support Black Hole Survey:
https://vxs7lf2w5sl.c.updraftclone.com/what-happened-to-support/