Three steps, and none of them are technical
You do not write prompts, learn a tool, or explain anything to a chatbot. You pick the job you already have and answer a few questions about it.
Pick the task, not the technology
Helpers are named after the job — a code-violation notice, a grant narrative, a council agenda summary. There are 1900 of them across 19 departments. You are choosing from a list of your own work, not writing a prompt.
Describe your situation in your own words
Fill in a few plain-language details — the address, the date, what happened, who it is for. Type it or speak it; field staff usually speak it. There is no syntax to learn and nothing you can phrase wrongly.
Review, correct, and send
You get a structured draft in your city's register, ready to edit. You are the author of record: check the names, dates, and figures, change what you want, and use it. Save the helper to your library and the next one takes a minute.
See it before you pay for it
Every helper in the library is browsable, with a sample of what it produces. Read a few from your own department first.
Your city's data is encrypted, isolated, and never used to train AI
Everything you upload or generate is encrypted in transit with TLS 1.2 or higher and encrypted at rest with AES-256. Each city's content is isolated to its own tenant, so no other organization can read it. Your documents and drafts are never used as training data by us or by our AI providers, and retention periods are set by your administrator.