A public works or utility department that is weighing an agent for its office and dispatch work should be putting questions to the vendor before anything is connected. Residents read the notices the department sends, council members forward the complaints, and the people who answer for the content are the department's own supervisors. These are the questions worth asking, each with the answer to look for.
Who reads a notice before it goes out?
The right answer names a role inside the department, such as the dispatch supervisor for route change notices or the billing supervisor for utility replies. A vendor who says the agent sends after a confidence check has described a system that decides on its own. Drafts should wait in a queue for a person, and the person's approval should be recorded.
What can the agent open, and what is closed to it?
Ask for the list of systems and folders the agent reads. A sound answer is narrow: the service request queue, the work order system and the route schedule, for example, with billing records opened only for the billing reply task. Ask who in the department approves each connection and how a connection is withdrawn. Records retention staff and the IT group should see this list before the first connection is made.
What does the agent do when it is unsure?
The answer to look for is that it flags and asks. An agent that fills a gap with a plausible guess will eventually tell a resident the wrong collection day or the wrong amount. Ask to see how an unclear service request, a missing address or a conflicting work order appears to the supervisor, and whether the agent says what it could not determine.
How is every draft kept?
Public records requests reach public works offices regularly, so ask what is kept: the source request, the draft, the reviewer's edits, the final notice and who approved it. Ask where those records live and whether the department can export them in a form its records staff already use. A vendor with no clear answer has not built for a department that answers to the public.
How does the department change what the agent does?
Rate structures change, routes are reorganized, and policy on billing disputes is revised. Ask who in the department can update the agent's instructions, how a change is reviewed before it takes effect, and how the old version is kept. The answer should involve the department's own supervisors, not a ticket to the vendor for each change.
What does the vendor not claim?
Ask the vendor to state what the agent does not do: it does not decide eligibility for a payment arrangement, it does not dispatch crews on its own, and it does not speak for the department in any public statement. Ask also about the vendor's own status. A private company should say plainly that it is not a utility, a regulator or part of any government, and should not describe itself as an approved or endorsed provider unless that is documented and true.
How is a rollout sequenced across the department?
The usual answer starts with one function, such as service request routing in dispatch, with staff comparing the agent's drafts to their own work before anything is relied on. It then extends to billing replies, route notices and fleet scheduling, one function at a time, with each supervisor deciding when their area is ready. A vendor who proposes switching on every function at once has not considered how a department with several supervisors actually adopts new work.
Reading the answers together
Taken as a set, the answers describe who is accountable. If every answer ends with a named person in the department, the agent is a drafting tool inside the department's own chain of responsibility. If some answers end with the vendor or with the software itself, the department has found the gap before it became a headline.