Contactability
The organisation gives you a way to make contact: a form, inbox, chatbot, phone line, portal, social account, or ticket number.
A ReplyResearch responsiveness study
Why we are investigating the customer support black hole
Customer support has never appeared more available. But more doors do not always mean more useful responses.
ReplyResearch is undertaking this survey because the black hole of unresponded enquiries is rapidly expanding. Vendors invite communication, but the response is often deathly silence or endless chains of unresolved issues. We decided it was time to point the finger. Help us do that.
01 — What is going on out there?
Support can look available while failing to respond
The modern support experience often promises accessibility. There is usually a button, a form, a chat window, an inbox, a helpdesk, or a ticket number. But accessibility is not the same as responsiveness.
Responsiveness
You receive a timely, relevant, useful response that moves the issue towards resolution.
More contact options do not necessarily create better response
02 — Why ReplyResearch felt duty bound to undertake this survey
Responsiveness failure is exactly what ReplyResearch exists to study
ReplyResearch studies how organisations respond, fail to respond, and create or destroy value through the way they handle attempts to contact them.
Support is where promises become real
Service, care, reliability, trust, and accountability are tested when someone needs a useful response.
The failure is often hidden
A company can look reachable while the person seeking help remains trapped in a process that does not resolve anything.
Isolated cases may not be isolated
One bad ticket can be dismissed. Repeated accounts can reveal a pattern.
The assumption we are testing
Are people just experiencing unlucky one-offs, or are the same support failures recurring across companies, sectors, and channels?
Why collect accounts?
To bring individual experiences together, compare them, and examine them for recurring signs of silence, delay, deflection, failed escalation, and unresolved outcomes.
03 — How ReplyResearch intends to conduct the survey
Structured accounts, reviewed for recurring patterns
The survey is designed to capture both the human experience and the operational pattern.
Collect accounts
Contributors describe what happened, who was involved, and what kind of support channel was used.
Identify the breakdown
Responses are reviewed for signs of silence, delay, circular replies, failed escalation, or no ownership.
Categorise patterns
Accounts are compared by failure type, support channel, sector, company type, and outcome.
Use evidence responsibly
Named organisations may be considered only where the evidence is strong enough to support doing so.
- Support requests ignored or abandoned
- Replies that arrived too late to be useful
- Responses that did not answer the question
- Repeated handoffs between teams or channels
- Failed escalation or unclear ownership
- Automated replies that created loops
- Customers asked to repeat information already provided
- Tickets open in theory while nothing meaningful happens
The aim is not to turn one person’s account into a public accusation. The aim is to identify patterns that can be responsibly supported by evidence.
04 — What this survey intends to find and demonstrate
Where does responsiveness actually break down?
The Support Black Hole Survey is intended to find out where customer support responsiveness is breaking down and what forms that breakdown takes.
Is this a speed problem?
Are failures mainly caused by slow replies, long queues, or response delays that make the eventual answer useless?
Is this an ownership problem?
Are customers passed between teams, bots, channels, or departments without anyone taking responsibility?
Is this a design problem?
Are support systems designed to create the appearance of response while preventing meaningful resolution?
- Whether certain failure types recur across organisations
- Whether some channels create dead ends instead of useful replies
- Whether automated support resolves problems or conceals non-response
- Whether escalation processes actually create accountability
- Whether sectors or company types show repeated response failures
- Whether companies are mistaking contactability for responsiveness
The larger question is simple: are organisations genuinely responding, or just adding more doors?
05 — How the findings are intended to address the problem
The evidence is for making the failure visible enough to challenge
The evidence collected through this survey is intended to make customer support responsiveness failure more visible, more comparable, and harder to dismiss.
Move beyond anecdotes
A single poor support experience can be waved away. A pattern of similar experiences is harder to ignore.
Show how support fails
The survey is not just about saying support is bad. It is about showing where and how the breakdown happens.
Create pressure for change
The evidence can help push these failures out of private frustration and into public accountability.
Turn what went wrong into pressure for change
That is the purpose of collecting the evidence: not to preserve individual frustration, but to make recurring support failure harder to ignore.
06 — How ReplyResearch will use the findings
From survey evidence to public analysis
ReplyResearch may use the survey findings to produce public analysis, summaries, articles, evidence briefings, rankings, comparisons, visualisations, or follow-up reports.
Identify common forms of support non-response
We will look for repeated types of breakdown: delay, silence, deflection, circular replies, failed escalation, abandoned tickets, or unresolved outcomes.
Distinguish contactability from responsiveness
We will examine the difference between being able to contact an organisation and actually receiving a useful response.
Compare sectors, channels, and company types
Where the evidence supports it, we may compare support channels, sectors, company types, and named organisations.
Develop clearer language and measures
We may use the findings to develop frameworks, definitions, or measures that help people describe responsiveness failure more precisely.
Create pressure for better support
The long-term purpose is to create pressure for better, clearer, more accountable customer support.
The survey does not promise to resolve individual cases. It does not replace a complaint, ombudsman process, legal route, or customer service escalation. Its purpose is different: to gather evidence of recurring responsiveness failure and use that evidence to make the problem more visible.
Taking part
Have you experienced the support black hole?
If you have experienced a customer support process that ignored, delayed, deflected, looped, or failed to resolve your issue, you can contribute your account to the survey.
What happens next?
The contribution page explains what kind of story we are looking for and how to request the survey link by email.
Why take part?
Your experience can help make support failure visible enough to challenge, especially when it matches patterns seen in other accounts.
This will take you to the survey intro page, where you can request the survey link by email.
Closing statement
The support black hole only works while nobody maps it
Customer support failure often leaves people isolated with the sense that their case is just one frustrating exception.
The possibility
Many of these experiences may be connected by recurring patterns of non-response, delay, deflection, and failed ownership.
The task
ReplyResearch is undertaking this survey to find those patterns, describe them clearly, and use the evidence to create pressure for change.
The reason to contribute
If support failed to respond when it mattered, your experience may be part of a much bigger story.
Add your evidence
Tell us what happened and help make support failure visible enough to challenge.