Built for agency communications and program staff
Upload your documents in the morning.
Answer residents from them by the afternoon.
Agency Assistant lets staff build an assistant without writing code. You set its instructions and tone, upload the ordinances, FAQs, program guides, and fee schedules it should answer from, and it can search and summarize them immediately, citing the document and section behind every answer. Before anything reaches the public, staff test it against realistic personas and a named approver publishes it. After it goes live, every conversation shows you what residents asked and what your documents did not cover.
- No engineering required
- Every answer cited
- Tested against personas
- Published only with approval
What it changes for your office
Residents ask the same questions every day. The answers are already written down.
Every agency has a shelf of documents that answer most of the questions it receives: the code, the fee schedule, the program guide, the FAQ page. Residents cannot find the right paragraph, so they call, and staff read it to them. Agency Assistant puts those documents behind an assistant your own staff configure, test, and control, so residents get the agency's answer and staff get time back for the questions that need a person.
For the program staff who own the answers
You decide what the assistant knows by deciding which documents go into its file store. When a fee changes or a new guide is adopted, you upload the new version and retire the old one, and the assistant answers from the change at once. Nobody has to file a ticket with IT.
For the communications office
You write the instructions that set the assistant's tone, its limits, and what it says when it does not know. You test it the way the public will use it, including people who are confused, upset, or trying to take it off topic, and you see every result before anything is published.
For the department director
You approve each version before it goes live and can roll back to an earlier one in a single step. After publishing, you see what residents ask most, where the documents fall short, and how the assistant handled every conversation, so you can show exactly what it said and why.
The product
Autessa Agency Assistant, what your team works in.
Instructions and Tone
Staff write the assistant's instructions in plain language: who it serves, what it may discuss, how formal it should be, which languages it answers in, and what it says when the documents do not contain an answer. The instructions are part of the version, so a change to them is tested and approved the same way as a change to the documents.
Document File Store
Documents are uploaded into a file store inside the application itself, and the assistant can search and summarize them as soon as they finish processing. There is no separate training step and no engineering work. Each document carries its title, its effective date, and its owner, and a document that has been replaced can be retired so the assistant stops citing it.
Persona Testing
Before a version is published, staff run it against a set of personas that stand in for the people who will use it: a first-time permit applicant, a frustrated resident, a contractor in a hurry, a Spanish speaker, and someone trying to take it off topic. Each conversation is shown in full with its citations, and a staff member marks it passed or failed with a note. A version cannot be sent for approval until its tests have been reviewed.
Topic Analysis
Once a version is live, every conversation is analyzed for its topic, whether it was answered from the documents, and the resident's sentiment. Staff see what people ask most, which questions the assistant could not answer, and which topics have no document behind them. That list becomes the plan for what to write or upload next, and the next version is tested and approved before it replaces the current one.
In practice
The details that decide whether an assistant can speak for an agency.
Three of them, handled the way an agency already handles anything published in its name: where the answers come from, how a version is reviewed, and what happens when something goes wrong.
On sources
It answers from your documents and says when it cannot
The assistant answers from the documents in its file store and cites the one it used. When the documents do not contain an answer, it says so and points the resident to a person, as its instructions direct, rather than filling the gap with a guess.
On publishing
Nothing reaches the public without a named approver
Every change to the instructions or the documents creates a new draft version. The draft is tested against the personas, the results are reviewed, and a named approver publishes it. The system never publishes a version on its own.
On mistakes
Any version can be rolled back in one step
If a published version gives a wrong answer, an approver can restore the previous version immediately while the problem is fixed. Each conversation records the version that answered it, so the agency can see exactly who received the wrong answer.
Below: a draft version waiting for approval, with its test results and the changes since the last published version.
Defensibility
When an answer is questioned, you can show exactly what was said and why.
An assistant that speaks for an agency will eventually be asked to account for itself. A resident says they were told the wrong fee, a council member asks what the assistant says about a contested ordinance, or a records request asks for every conversation on a topic. The question is not only whether the answer was right. It is whether the agency can show what the assistant said, which document it relied on, and who approved the version that said it.
Agency Assistant keeps that record as it works. Every conversation records the version that answered, the documents it cited, and the instructions in force. Every version records who drafted it, the persona tests and their review, and the person who approved it. The log is append-only and stays in your own Autessa Private Cloud, with keys your agency holds, so what you produce later is what was recorded at the time.
One version of the assistant, from a new fee schedule to a published release.
The unanswered questions from the same period, grouped into the documents that would answer them.
Build one with your own documents.
Bring the documents your staff answer from most often and a list of the questions residents ask. We will set up Agency Assistant with them, run it against personas your team chooses, and walk you through the results before anything is published.
FAQ
Questions we are glad to answer.
Do we need engineers or a training process?+
No. Staff write the instructions and upload documents into the file store inside the application. The assistant can search and summarize a document as soon as it finishes processing, without a separate training step.
What does it do when the documents do not have the answer?+
It says that it does not know and directs the resident to a person, using the contact information in its instructions. The question is recorded as unanswered so staff can see which documents are missing.
What are personas, and do we choose them?+
Personas are simulated residents used to test a version before it is published, such as a first-time applicant, a frustrated caller, a Spanish speaker, or someone trying to take the assistant off topic. Your staff choose and edit the personas, and review every test conversation.
Can we undo a version that was published?+
Yes. An approver can restore any earlier version in one step. Every conversation records the version that answered it, so you can see who received an answer from the version that was rolled back.
Where does our data go?+
Agency Assistant runs in your own Autessa Private Cloud, an environment your agency controls, with keys your agency holds. Your documents and conversations with residents are not used to train models for anyone else.