Imagine a resident calling about water running down the street. The operator takes the report, records the location and arranges a callback. But one digit in the phone number is wrong, and the street name could refer to two different places.
The team now has an urgent report and a problem finding the person who made it.
That is a hypothetical example, but it raises a practical question for councils: how confidently are critical details being confirmed before a call ends?
Names, email addresses, street addresses and callback numbers deserve particular attention. They are the details that connect a conversation to the next action.
Small details can have consequences beyond the call
An incorrect email address can mean an update never reaches its intended recipient. An incomplete location can send a crew to the wrong place. An incorrect callback number can leave an operator unable to clarify what is happening.
Where a council manages water services, the potential consequences extend beyond another phone call. In the hypothetical leak scenario, a delay could mean additional water loss, more damage to surrounding ground or property, further crew time and a larger repair. During drought, wasted water carries an additional resource cost.
The eventual cost depends on the incident. There is no defensible single price for a misheard detail. What matters is recognising the categories of exposure: wasted travel, repeat work, delayed repairs, damage and disruption to residents.
A short call that leaves the next team with an unusable address has not finished the job.
Make confirmation easier for both people
These difficulties can affect anyone. Traffic noise, a poor connection, stress and unfamiliar names can make information harder to hear. Different accents and speaking patterns can add to the challenge of a particular conversation without either person doing anything wrong.
Email addresses and long strings of digits are especially awkward to confirm aloud. Repeating them helps, but both people can still leave believing they agreed on the same detail.
Written confirmation offers another way to check. The resident can see what has been entered, and the operator can ask about a specific letter, number or missing suburb.
Where EOV6 fits
The locally tested EOV6 release candidate supports a shared text conversation and dedicated name, email and phone fields. After the caller presses Save, the operator sees the saved details following a brief refresh. Street addresses can be shared in the text conversation.
That candidate has not yet been deployed to the public site. A controlled demonstration could show how an operator and resident review these details together while still in contact.
Written information still needs checking. A resident can mistype a number, confuse the reporting address with the incident location or leave out a unit number. These features do not validate identity, addresses or phone numbers. The operator still needs to confirm the details and follow the council’s procedures. EOV6 does not guarantee that errors or delays will be prevented.
Start with a controlled demonstration
A useful first evaluation would focus on one clear workflow, such as confirming contact and location details for service requests. Use synthetic information in realistic test cases, including similar street names, unit numbers and complex email addresses.
Agree on the questions any later operational pilot would need to answer:
- How often are critical details correctly captured and confirmed the first time?
- How often do required callbacks reach the intended person?
- How often does changing a detail during confirmation introduce a new error?
- How much time goes into clarification during the call and rework afterwards?
That evaluation should compare like-for-like cases with the existing process. Include operator feedback and accessibility needs. Keep an alternative for anyone unable or unwilling to use the digital session, and ensure urgent response procedures can continue without waiting for it.
Before considering real resident information, councils would need to complete security, privacy and operational readiness reviews. These should cover collection, access, retention and deletion, plus how confirmed details enter the authorised council record.
The aim is straightforward: give the next person in the process reliable information to act on.
For councils exploring that problem, a controlled demonstration using synthetic service scenarios is a sensible place to start. See how EOV6 works.