twimco.Let’s talk ↗︎
Menu
Field notes / AI & judgment

A city assistant that speaks 70 languages still needs someone who reads the answers

Eagle Mountain, Utah, just gave residents an assistant that answers by chat or text in more than 70 languages. That number is the easy part. What matters is whether a resident asking about trash pickup in Tagalog gets the same right answer, and the same route to a person, as one asking in English.

Editorial engraving of a bright recreation-center gym where volunteers read a city assistant's answers on phones and tablets while a staff member marks a large paper grid.

A multilingual city assistant is only as good as its worst-served language. Before launch, and every quarter after, pick the ten questions residents ask most and the five languages your residents actually use, ask all fifty, and have a fluent reader check each answer for accuracy, tone and a working handoff to staff. Watch fees, deadlines and emergencies most closely. Eagle Mountain's Emmie, launched Nov 2, 2026 with 70+ languages and a staff handoff, is a good prompt to run that test on your own assistant.

Why the number on the poster isn't the test

On November 2, 2026, Eagle Mountain, Utah, introduced Emmie, an AI assistant for its residents. It was built with Citibot, a company that makes AI communication tools for local governments. Residents can chat with Emmie on the city website or text "Hello" to 855-763-6643. They can ask about city services, report issues and submit requests, any hour of the day, in more than 70 languages. On both chat and text, Emmie can pass a request to city staff when it needs a human. The city is clear that Emmie isn't for emergencies; for those, residents call 911.

Eagle Mountain has more than 80,000 residents, and the city says it wants more of them to get help in the language they're most comfortable using. That's a good goal, and Emmie is a well-scoped launch: city information and requests, a human handoff, and a plain emergency warning.

We're not reviewing Emmie here. We haven't seen its answers in any language, and the city hasn't published accuracy figures. Its launch is a useful prompt, though, because many cities and counties are buying the same kind of tool. The question for each of them is the same: what does "70 languages" mean for the resident who doesn't speak English?

Seventy languages is a capability. Five languages checked by people who speak them is a service.

Ten questions

Start with the questions your staff already answer most. Pull them from call logs, front-desk tallies and the requests that come in by email. For most cities the list looks roughly like this, but use your own:

  1. When is my trash and recycling pickup, and what happens on a holiday?
  2. How do I pay my water bill, and what's the late fee?
  3. How do I report a pothole or a broken streetlight?
  4. Do I need a permit for a fence, a shed or a garage sale?
  5. When is the next city council meeting, and how do I comment?
  6. How do I reserve a park pavilion?
  7. Where do I get a business license?
  8. What's the deadline to sign up for a program or pay a fee this month?
  9. My neighbor's tree fell on my fence. Who do I call?
  10. There's a gas smell on my street. What do I do?

Questions 2, 4, 7 and 8 have numbers and dates in them. Question 9 should end with a handoff. Question 10 should never get a chatty answer. It should send the resident to 911 or the gas company's emergency line straight away.

Decision guide

What a good answer does, by question type

ConsiderationQuestion typeA good answer
Fees and deadlinesWater bill, permits, sign-ups.Exact figures and dates, same as English
Reporting a problemPotholes, streetlights.Files the request and confirms it
Messy situationsNeighbor disputes, damage.Hands off to staff who can read it
EmergenciesGas smell, danger.Immediate redirect to 911, in that language
Decision framework for scoring answers in every language.
Seventy languages is a capability. Five languages checked by people who speak them is a service.

Five languages

Don't test 70. Test the five that matter most for your residents. Use census language data for your area, school district enrollment data and your own interpreter request logs. In many places that will be English, Spanish and three others that differ a lot from city to city.

Then find a fluent reader for each language. Ideally that's a staff member, a library volunteer or someone from a community organization the city already works with. Don't rely on another machine translation to check the first one. The point is to catch exactly the mistakes a machine would make, such as a fee rendered as a fine, a "may" turned into a "must," or a formal register that reads as cold.

Test chat and text separately. A text message reply is short, and shortening is where meaning gets dropped. An answer that's fine on the website, with links and a full paragraph, can lose the one sentence that mattered when it's cut down for a phone. If residents can reach the assistant both ways, as Eagle Mountain's can, ask a few questions in each channel.

One afternoon

Fifty questions takes an afternoon if you split it up. For each answer, the reader marks four things:

Correct. Same facts as the English answer. Same fee, same date, same office.

Clear. It reads like something a person would say, at the level of a city letter, not a legal notice.

Handoff works. When the assistant says it's passing the request to staff, does it actually arrive, and can staff read it? A handoff that lands in an English-only inbox is a dead end for the resident who wrote in Vietnamese.

Safe. Emergency questions get an immediate, unambiguous redirect in that language, with the right number.

Put the results in a simple grid, one row per question and one column per language. You're looking for patterns, not perfection. If one language gets dates wrong, or one kind of question never hands off, that tells you what to fix.

Keep the transcripts, too. They're the evidence you'll want when you talk to the vendor, and they're a baseline for the next round. Share the grid with the department heads whose questions you tested. The parks office will spot a wrong pavilion fee faster than anyone in IT, and they'll care more about getting it right in every language once they've seen it go wrong in one.

Finally, write down what you didn't test. Fifty questions in five languages is a sample, not a guarantee. Being honest about that internally is what keeps the quarterly rerun on the calendar.

How the work moves

One afternoon of testing

  1. Pick ten questions

    From call logs and front-desk tallies.

  2. Pick five languages

    From census, school and interpreter data.

  3. Ask all fifty

    On chat and on text.

  4. Fluent reader marks each

    Correct, clear, handoff works, safe.

  5. Fix sources, rerun quarterly

    Compare the grid each time.

Illustrative decision framework; use your own questions and languages.

What to do with what you find

Fix the source, not the answer. Most wrong answers come from the content the assistant draws on: an outdated fee page, a holiday schedule nobody updated, or a PDF the tool can't read. Our note on the county assistant and the old press release walks through how that happens.

Write down the words that must be exact. Fees, deadlines, program names and legal terms should have approved translations the assistant uses every time. We've written about AI translation and the words that matter.

Decide who reads the handoffs. If staff can't read a request in a language, plan how they'll get it translated and how fast the resident hears back. Publish that, so residents know what to expect.

Repeat it every quarter. Fees change, pages move, and vendors update models. Rerun the same fifty questions and compare the grid.

None of this replaces the vendor's own testing. It's the city's part of the job: the residents are yours, so the check should be too.

If you're planning or reviewing a resident-facing assistant, our government and public sector team helps cities set up the content, handoffs and testing behind it. Get in touch and tell us which languages your residents use most.

Related work: Sutton Place.

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Sutton Place ↗︎