On this page
Somebody needs to know whether they can still register their child for the spring session. They look at the website for four minutes, find a page from last year and a PDF that will not open properly on their phone, and close the tab. The need has not gone anywhere. It is now going to arrive as a phone call at nine the next morning.
This is the part of website performance that almost never gets measured, because the cost lands somewhere other than where it was caused. The website records a short visit and an exit. The call centre records a call. Nothing connects the two, and so the failure is funded as a staffing problem rather than a content one.
Where does the cost actually land?
On your staff, almost always. A resident who cannot find something phones, emails or arrives in person — and each of those costs materially more to serve than the page would have cost to fix. The rest give up, which costs nothing visible and the most of all.
The asymmetry is the point. Fixing a page is a one-off cost paid once by one person. Not fixing it is a recurring cost paid by every resident who needs it and every staff member who takes the call, for as long as the page stays wrong.
The five things a resident does next
- They phone. The most common, the most expensive per contact, and the only one that shows up in a budget line somewhere.
- They email, which is cheaper per contact and slower to resolve, and often takes two exchanges because the first message lacked context.
- They walk in, which is the most expensive of all and usually means the question mattered and the deadline was close.
- They ask on social media, where your team answers in public, repeatedly, under a post about something else.
- They ask a neighbour, a community group or whoever answered last time — and receive a confident answer that was accurate two years ago.
Why it is invisible in your analytics
Standard website reporting is built to measure what happened on the website, and this failure happens after somebody leaves it.
- A short visit reads as efficiency. Somebody who left in forty seconds because they gave up looks identical to somebody who found their answer in forty seconds.
- A high exit rate on a service page is often reported as normal, because the page is the end of a journey. Sometimes it is the end; sometimes it is abandonment.
- Nothing links a session that ended at 4:40pm to the call that arrives at 9:10 the next morning.
- Residents who never reached the right page cannot be counted on it.
- Satisfaction surveys are answered by people still engaged enough to answer a survey.
Where failure costs the most
Not all unfindable content is equally expensive. These are the pages where a failure turns into something worse than inconvenience.
| Content | What failure causes | Why it ranks high |
|---|---|---|
| Registration and application deadlines | A missed window | Cannot be recovered after the fact. The resident loses the service outright. |
| Eligibility rules | A wasted application, or none at all | People who are eligible and assume they are not never appear in any figure. |
| Closures and cancellations | A wasted journey | Felt immediately and personally, and the most likely to become a complaint. |
| Payments and penalties | A late fee | Turns a findability problem into a financial one for the resident. |
| Emergency and safety information | Harm | The one category where the cost is not measured in time at all. |
| Consultations and public notices | Lower participation | Quietly undermines the legitimacy of the decision that follows. |
How to find your own failures
All of these can be done this week, by one person, without a budget.
- Ask the front desk which page they send people to most.If staff have memorised a path, residents cannot find it on their own.
- Read your zero-result search queries.Each one is a resident telling you plainly that something is missing.
- Try your top three tasks on a phone, on mobile data.Most residents are on a phone. A PDF that opens fine on a desktop can be unusable on one.
- Ask somebody outside the organisation to find one thing while you watch.Say nothing for three minutes. It is uncomfortable and it is the most informative three minutes available to you.
- Check what your own website returns for the phrase people actually phone about.If the first result is a committee minute, that is the problem in one line.
What to fix first
- Anything with a deadline attached. A missed window cannot be undone later.
- Anything the front desk gives directions to by memory.
- Anything that only exists inside a document, particularly one that does not open well on a phone.
- Pages named after a department rather than the thing a resident wants.
- Pages last reviewed before the service changed, which residents will act on regardless.
- The homepage route to your three most-used services — because residents who cannot see it will search, and your search box carries the consequences.
Where SmartBot fits
An assistant catches a share of this at the moment it happens. A resident who would have closed the tab asks the question instead and gets an answer from your published content, including outside the hours when phoning was never an option anyway.
The second effect matters more over time. The questions it could not answer are a record of the failures you would otherwise never hear about — the ones that ended in somebody giving up quietly. That list is the closest thing to a direct measurement of this problem that most agencies will ever have.
Frequently asked questions
How do we quantify this for a budget conversation?
Count contacts rather than estimating. Tally for one week how many calls and emails were about something already published on your website. That number, multiplied across a year, is the cost of the findability problem — and it is a figure from your own operation rather than an industry average.
Our bounce rate is low. Does that mean the site works?
Not on its own. Somebody who found their answer immediately and somebody who gave up immediately produce similar numbers. Pair the metric with something that reveals intent, such as search queries or front desk contacts.
Is this a design problem or a content problem?
Usually content and naming rather than visual design. Pages named after departments, answers buried in documents, and text written for colleagues rather than residents account for most of it. A redesign that leaves those intact rarely changes the call volume.
What about residents who will never use the website?
They remain a genuine group and the phone must stay available for them. The aim is not to push everybody online; it is to stop sending people to the phone who would have preferred not to be.
Where does accessibility come into this?
Directly. A page or document that assistive technology cannot read is unfindable in the fullest sense, and the residents affected are the least likely to have a convenient alternative route.
How often should we check?
Watch somebody attempt one real task each month. It takes fifteen minutes, needs no tooling, and will consistently find things that quarterly reporting misses entirely.
Where to go next
Ask your front desk one question this week: which page do you give people directions to most often? Whatever they name is a page residents cannot find on their own, and it is costing you a call every time. That is the first fix, and you will not need a report to justify it.