The 106 municipal hotline and AI: from 13 hours per ticket to 3.5

Look at any Israeli municipality's 106 hotline log and you will find the same list: the bin was not collected, the bin was left mid-sidewalk, the pruning was not picked up, the truck was noisy at 5am, the truck hit a parked car. What they share - they are questions of fact. Something did or did not happen on a specific street at a specific time. And yet, without documentation, each such ticket becomes a journey: operator logs it, ticket moves to the department, the department asks the contractor, the contractor asks the driver, and two days later an unverifiable answer comes back.

When the trucks carry a monitoring array with video and location, that journey shrinks to one step: the operator (or an automated flow) pulls the relevant clip by address and time, sees what happened, and gives the resident a grounded answer - sometimes within the same call. In a regional council in central Israel working this way, average ticket handling time dropped from 13 hours to about 3.5, as publicly reported - a drop of more than 70%. Our other customers measure similar orders of magnitude.

The next layer is AI: the system does not wait for a complaint. An uncollected bin, or one not returned to place, is detected automatically from the truck itself and opened as an event - before the resident calls. Some tickets simply disappear, because the problem was fixed before it became a complaint. That is the plain definition of a proactive hotline.

There is a subtler effect too: trust. A resident who gets a factual answer stops feeling brushed off, and an operator with real tools stops absorbing the frustration. The contractor relationship changes as well - instead of arguing about what happened, you discuss what to do.

For anyone considering a start: you do not need to wire the whole city in one day. One monitored collection route plus a simple hotline integration is enough to measure the change in handling times within a month, and decide on your own numbers.