Giving feedback

Written By Kevin Ruth

Last updated 3 months ago

When someone flags that the AI is citing an outdated requirement, we can fix it quickly. Giving feedback, especially early on when you are first using the tool, is critical for us to learn and tune the AI assistants to maximize how helpful they can be.

Why feedback matters

  • It helps us fix wrong answers before they mislead someone

  • It surfaces gaps in the code we haven't documented yet

  • It shows us where permit types or scenarios confuse the AI

  • It tells us what to prioritize next

How to give feedback

In the chat assistant

Below each response, you'll see an icon with a question mark in a speech bubble which will open up a feedback form. It is just as important to flag perfect answers as it is to give us feedback; knowing where the AI is working helps us benchmark each iteration of the Assistants we ship.

You can also rate the overall session, instead of individual responses, by clicking the "rate" button in the chat window.

In the email assistant

Whether you're using the Outlook plugin or the web app, look for the feedback button in the sidebar after generating a draft. You can flag missing information, note what went wrong, and add details in the text box.

Feedback in the web app uses the same form as the chat assistant
Feedback in the Outlook Plugin appears under the "Generate Draft" button

General product feedback

You can use the magenta widget in the bottom right hand corner of the screen on Permit Guide to submit any product feedback or visit our help center.

What to include

Helpful feedback tells us:

  • What was wrong - "The setback number was incorrect"

  • What was missing - "It didn't mention the fire code requirement"

  • What you expected - "I expected it to reference [specific code section]"

  • Context - "The address is in a critical area"

Examples of good feedback

Specific:

"The response said 5-foot setback but R-10 requires 10 feet for side yards."

Missing information:

"It answered the zoning question but didn't address that the property is in a critical area overlay."

Source issue:

"The citation is from an old version of the code. The current requirement changed in 2024."

Where feedback goes

Your feedback is logged and reviewed. Department leadership can see it too—this isn't going into a void.

Don't hesitate

Even small feedback helps:

  • "Formatting was hard to read"

  • "Took too long to respond"

  • "Great answer, very helpful"

If something feels off, say something. We're listening.