A Practical AI Intake for City Halls

Start with the queue you already have

The useful inventory is a week of real work, not a strategy memo. Sit with the person who answers the main line and mark the questions that repeat. In a small Texas city those clusters are usually familiar: trash and bulk pickup days, water bill amounts, permit status, council agendas, facility rentals, and "who do I call about a pothole." Some of those already have a correct answer on a web page nobody can find. Some require a clerk to look in a system. Some require a judgment the city should not hand to software.

Write three columns. Column one is the question in the resident's words. Column two is where the true answer lives today: a PDF, a utility billing system, a permit system, a shared inbox, or someone's memory. Column three is what must stay human. Payments, eligibility, code enforcement, personnel matters, and emergency dispatch belong in that third column until your counsel says otherwise. A pilot that begins in column three is the wrong pilot.

Liberty ChainGuard is an SBA-certified Service-Disabled Veteran-Owned Small Business (SDVOSB) in Ingleside, established in 2025. The intake is how we learn whether a later audit is worth anyone's time. Owner Hobie Cunningham reads it. We are building past performance, so the follow-up will not cite other cities as if they were clients.

A one-page audit before any seats

Before a vendor demo, a city can answer the questions below in a single working session. If the answers are fuzzy, the next step is to fix the queue, not to sign a subscription.

1. Who answers the repeat questions today, and what else is on their desk?
2. Which system is the record for that answer? If two systems disagree, which one wins?
3. How often does the answer change? A trash calendar changes rarely. A permit status changes daily.
4. What would a wrong answer cost? Embarrassment, a missed inspection, or a resident sent to the wrong office are different risks.
5. Is there already a written script, a FAQ, or a front-desk binder? If yes, that text is the draft knowledge, not a blank model.
6. Who is allowed to approve a reply that leaves the building?
7. What will you stop doing if the pilot works? If the answer is "nothing," you are adding a tool, not removing work.

The AI integration page describes the same idea for small businesses and public agencies: map the steps, name the system of record, and recommend a narrow workflow. If the content is not ready, we say that before anyone buys seats.

Records, privacy, and the reply that gets filed

City work is public work. Emails, texts, and portal messages can be records. A chatbot transcript can be too, depending on how you use it and what your retention schedule says. Staff should assume that a casual prompt is not private. Do not paste a resident's account number, a medical detail from a city clinic, a job application, or a law-enforcement narrative into a consumer chatbot to "see what it says."

A safer pilot uses a limited set of approved paragraphs, points residents at the official page or the official queue, and keeps a person on anything that changes an account. If software drafts a reply, the employee who sends it is still the sender. The draft is not the record until someone files the message the city actually transmitted.

Public information requests are their own process. Staff can use tools to sort documents they have already gathered. The tool does not decide exemptions, and it does not answer the requestor on its own. Your city attorney or public information officer owns that call. LCG will not take it from them.

What the five-minute intake is for

The AI customer-care intake takes about five minutes. It asks what kind of organization you are, where customer-service and admin work is slow, and what you want to improve. A city can use it the same way a clinic or a contractor would: to give Liberty ChainGuard enough detail to recommend a workflow audit, a small pilot, or a not-yet path.

Bring the three-column list if you made one. If you have not, the form is still enough to start. After you submit, we follow up with a practical recommendation. That follow-up may include IT products when the bottleneck is the phone system, the inbox, or the PCs at the front counter. Those products are sourced through the channels on our partners page, under the rules in the vendor-neutral guide. IBM portal enrollment and completed sales foundations inform product conversations. They are not a reseller badge, and they are not a municipal AI platform.

A sensible first pilot

If the audit says a pilot is reasonable, keep it smaller than the org chart. One queue. One owner. One written set of approved answers. A human review step on every message until the error rate is something the city manager can describe out loud. A stop condition: if the tool invents a fee, a deadline, or a department, the pilot pauses the same day.

Good first queues are the ones where the answer is already published and the cost of a mistake is a second phone call. Facility hours, agenda locations, which form to use, and where to pay a bill online fit that description when the city page is current. Permit approvals, utility adjustments, and anything that spends public money do not.

Measure one number you already track, such as how many times staff retype the same directions in a week. If you cannot count it, you cannot tell whether the pilot helped. A demo that impresses a council workshop and does not change that count is a presentation, not an implementation.

What this firm will not claim

• No city seals, no "trusted by" list, and no implied municipal contracts.
• No promise that AI reduces headcount. The aim is a shorter manual queue for the people you already have.
• No legal opinion on records retention or the Public Information Act.
• No security product bundled in just because a model was mentioned. Firewalls and endpoints are separate quotes.
• No past-performance story from before the firm existed. Established in 2025 is the true start.

Identifiers, if a purchasing packet asks: UEI RP1XYZMDYGC7, CAGE 13ZA3, Service-Disabled Veteran-Owned Small Business (SDVOSB). The capability statement and the SDVOSB buyer page carry the same facts. Certification does not make the intake a set-aside, and the intake does not make the certification a case study.

Questions we hear

Will this intake automate city hall?

No. The intake asks where repetitive questions and paperwork already sit. Liberty ChainGuard may recommend a workflow audit, a small pilot with a human review step, or a decision to wait. We do not claim a city deployment, because we do not have one to cite.

Can staff paste resident records into a free chatbot?

Do not. Utility accounts, permit files, personnel records, and anything a resident would not want forwarded belong in the city's system of record. A pilot should name which fields may leave that system, and a person should remain responsible for what gets filed.

Does an AI draft answer a public information request?

No. Texas public information requests follow the city's process and the Public Information Act. A draft can help staff assemble records they already retrieved. It does not decide what is releasable, and it does not replace the public information officer.