Bills go out in one week. Over the following fortnight the same questions arrive tens of thousands of times. Why has it gone up. Can I pay monthly. Do I get a discount. My band is wrong. I cannot afford this.
Every one of those has a published answer and almost none of it is findable in the ninety seconds someone spends looking.
The teardown: why the spike is so large
Bills arrive simultaneously, they contain a number that has usually risen, and the explanation is written in the language of local government finance. Everyone reaches the same conclusion at the same moment, which is to contact someone.
Failure one: the increase is not explained
Why the figure changed, what the components are and which parts the council does not control. A short explanation in plain language prevents a substantial share of the contact.
Failure two: discounts are buried
Single person, students, severe mental impairment, carers, annexes, empty properties and other circumstances. These need naming in the language people use, not in scheme titles, and they need to be found from the bill itself.
Failure three: nobody explains who handles banding
Valuation is handled by a separate body in many places, and people contact the council because the council sent the bill. Explaining who does what, with a link, redirects those contacts entirely.
Failure four: payment options are not surfaced
Monthly, over ten months or twelve, by direct debit, changing the payment date. Publishing the options, and how to change, removes a large volume of calls.
Failure five: the hardship route is hidden
People who cannot pay need reduction schemes, support and a conversation, and the route must be visible and non-judgemental. Hiding it produces enforcement cases that were avoidable.
Failure six: moving home is treated as an afterthought
Moving in, moving out, closing an account and final bills. House moves generate a steady stream of identical contact all year, which is the same problem as meter reading and billing query routing for utilities.
Failure seven: everything requires a form
Some queries genuinely need one and many are answerable. A page that answers, and only then offers a form, halves the submissions.
Failure eight: contact is only possible in office hours
Bills are opened in the evening and at weekends. The question that goes unanswered on Saturday becomes a call on Monday morning when the lines are already at capacity.
What to publish
An explanation of the bill and what changed, the discounts in plain language with eligibility, the application routes, who handles banding, payment options, the hardship route and what to do when moving.
Never assess eligibility
Whether someone qualifies for a discount or a reduction is a decision for the council's team against the rules. A website explains the criteria and captures the application.
Route financial difficulty properly
Anyone saying they cannot pay needs the support route and independent advice sources, immediately and prominently, not a payment page.
Other council contact follows the same shape
It is covered in resident questions councils answer again and again and planning application questions from residents.
Discount questions are universal
Handling them consistently is the subject of how to handle discount and coupon questions with a chatbot.
Getting started
Publish the bill explanation, discounts in plain language, payment options and the hardship route, then answer at any hour without assessing anyone. SpideyChat for public bodies answers from your published pages, our plans are on the pricing page, and the chatbot ROI calculator works through the numbers.