Residents cannot take their custom elsewhere
A person unhappy with a shop can walk to another shop. A resident who needs the council usually cannot. They need a bin collected, a form processed or a road mended. The council is the only place to ask.
That makes first contact important. A clear answer saves a second call. A vague answer often turns into a complaint. It may become an email to a councillor or a post on a local community page.
Councils also make public promises. Many publish service standards for how fast calls are answered and enquiries are replied to. Residents read those promises, and some quote them back.
Contact centre staff deal with a huge range of subjects in one day. Good systems help them as much as good training does.
Residents fund these services through local taxes, so they expect a clear answer and a fair hearing. A good first reply also cuts repeat contacts, which frees staff time for harder cases.
We help you see whether daily practice matches what is written down.
Following one resident enquiry from start to finish
Each check starts with a simple scenario agreed with you. It might be a missed bin collection, a bulky waste booking, a parking permit question or a pothole report. We avoid anything sensitive, such as benefits, social care or child protection.
The shopper first looks on your website. Can they find the right page? Is there an online form, and does it work on a phone?
Next they try another route. That could be the telephone line, an email or webchat. They note the wait, how the call is answered and whether they are told what happens next. The shopper writes notes straight after each contact, while the details are fresh.
Where it suits, they visit a customer service point or library hub. They ask the same question and see whether the answer matches. Afterwards we record whether the resident hears back, and when. We note the time of every step, so you can see exactly where a resident waited.
What we measure against your own standards
We start with the standards you have published. If you promise that calls are answered within a set time, we time them. If you promise a reply to emails within a number of working days, we track that too.
We then score the universal checks. These cover website experience, ease of making contact, response time and telephone manner. They also cover welcome, understanding of the enquiry, clear explanation, trust and professionalism, and follow-up.
For councils we add local checks. Is the right team named? Is a reference number given? Is the resident told plainly when nothing can be promised?
Is the language everyday English or council jargon?
We also look at access. Is there an easy-read option? Can a deaf or hard of hearing resident find a way to get in touch? We record what is offered and how easy it is to find.
Councils rarely sell anything, so the check on securing the sale changes. We ask a different question: does the resident leave knowing exactly what happens next?
Things worth checking in your own service
These are prompts, not accusations. Every council is different, and one shop shows one occasion only.
Check whether the web page and the telephone menu give the same answer. Check whether a call is passed between teams without anyone saying why. Check whether a resident has to repeat their address three times.
Look at the online form. Does it confirm that it was sent? Does anyone reply? A form that sits in a shared inbox is hard to spot from the inside.
Look at what happens when the first person cannot answer. Does the resident get a named team, a direct number or a call-back? Or are they sent back to the start?
Look at call-back promises and out-of-hours messages. Are they kept?
Look at the date a page was last updated, and whether links to documents still work. Finally, check that help for residents who cannot use the internet is easy to find.
What the council receives
You receive a scored report. Each score is backed by an observation, such as a call time, a page name or a reference number. We use notes and screenshots. We never make covert recordings.
The report lists strengths, weaknesses and a prioritised action plan. The plan separates quick fixes from bigger changes. A wrong web page is a quick fix. How enquiries move between teams is a bigger change.
Evidence sits beside each score, so a service head can check the facts. Where something worked well, we say so, because staff should know what to keep doing.
A short summary page is written so that it can be shared with service heads, scrutiny groups or members.
We never name or rank individual staff. There are no league tables. Findings show one customer journey on one occasion, and they are a prompt for improvement, not a verdict.
A retest later measures whether the changes helped.
Who it suits and how to start
This suits customer services managers, heads of service, digital teams and anyone preparing for a service review. Parish and town councils can use a smaller check on one or two services.
We ask you to confirm that staff have been told, in general terms, that mystery shopping may take place. They do not need to know when.
You can ask for a free first-impression report on one route to see how we work. Your phone line is a popular choice.
Most councils begin with a small check on one service and widen it after reading the report. A retest can follow a staff briefing or a website change.
To test one particular service, try Custom Questions. You write up to 10, 20 or 30 of your own questions and choose how many shoppers to use. Email us and we will send you a quotation.