September 22, 2026
City hall answers at 9pm: Celeste for local government
Trash schedules, permit steps, park reservations, and 311-style intake, answered from what the city already publishes, at the hours residents actually ask.
Residents contact their city at 9pm, on Sunday, on a holiday, because that is when the question occurs to them. When is bulk pickup on my street. What do I need for a deck permit. How do I reserve the pavilion. Why is my street closed Thursday. City hall answers at 8am Monday through Friday, and the gap between those two schedules is most of what residents mean when they say it is hard to get an answer from the city.
Celeste closes that gap on the city’s website chat and email, using nothing the city has not already published.
The city already wrote the answers
Municipalities are prolific publishers: collection calendars, permit checklists, fee schedules, park rules, meeting calendars, code enforcement procedures. What residents lack is not information, it is retrieval at the moment of the question. Ingest the published material and the agent answers what it says: which cart goes out this week, what the deck permit requires before you apply, what the pavilion costs on a Saturday, and where in the process a permit application sits if you connect the permitting system as a read-only tool, scoped to the applicant’s own application after they verify who they are.
When a question is not covered by anything published, the agent says so and routes it to the right department instead of improvising municipal policy, and the miss is logged as a named knowledge gap. That gap list, read monthly, is a plain-language report of what residents ask that the website does not answer, which is a document most cities have never had.
311-style intake that arrives structured
The pothole report, the streetlight out, the missed pickup: these are intake, and intake is where an agent saves the most staff time. The agent collects location, description, photos, and contact, and, with the city’s service request system connected as a tool, files a real request with a tracking number the resident can ask about later. Filing a request is a write, so it follows the product’s write rule: the city classifies the action before the agent may execute it, and until then requests arrive as held drafts a clerk approves in one click.
Some messages must reach a person immediately, and the city decides which. “Water main,” “sewage,” “downed line,” “gas” go on the escalation keyword list, and a message containing one is barred from an automated reply and held with the trigger flagged. For genuine emergencies the drafted answer is the one every dispatcher would give: call 911. The agent never rates an emergency as routine, because that judgment was never delegated to it.
Determinations stay with the government. Whether a variance will be granted, whether a citation will be dismissed: the agent explains the published process and never predicts the outcome.
Piloted like a sidewalk, not a stadium
A city does not turn this on for everything at once. Start with one department’s queue, public works and parks are natural picks, in shadow mode, where the agent drafts silently against real resident email while staff read what it would have said. Schedules and how-to questions graduate first; intake filing when the held drafts have proven clean; anything the clerk wants held stays held.
What a city buys here is the after-hours window, which is where residents actually live, plus a front counter that stops absorbing the same six questions and can attend to the residents standing at it. See how it works or the product; the trial runs silently against a real inbox first, so staff can grade a month of drafts before a single reply sends.