codeforpdx / codeforpdx/tenantfirstaid

Re-design User Flow and Entry Experience by Adding Clear Route to Both AI Chat and Letter Generator

Open
#237 1 comment 0 reactions 2 assignees View on GitHub

@leekahung is already working on this.

Since Dec 12, 2025.

UX design
Dominant language
Python
Stars
13
Forks
21
Avg merge
6d 7h
Merged PRs (30d)
3

Description

OVERVIEW

This issue restructures the entry experience into a unified, user-friendly flow that starts on the landing page and reduces confusion between the AI Chat and Letter Generator. We will implement a lightweight intake (e.g., state/city, housing type/context, type of the housing issue) with clear explanation as of why location is requested. After intake form, users will see an explicit choice between AI Chat bot and generating a Letter to the Landlord. This creates a consistent “start here” path while still allowing tool access from the menu. The entry point from the menu buttons will adopt the same intake form with slight modifications (see Feature Chat + Letter issue for more details)

Scope

tool-choice flow, routing logic

ACTION ITEMS

  • Define and create START entry logic with two options: AI Chat Bot and Letter Generator
    • Expand the type form with Qs and answer choices
      • City in Oregon State
      • Type of Housing
      • Particular Housing Issue
  • Provide guidance/instructions/explanation (why are we asking about your state/city? why housing type matter)
  • Before they enter the AI chat bot or letter generator, add disclaimer about privacy (maybe pop-up) to reinsure the user that we don't store their private data
  • For AI chat bot, clarify that example prompts are just examples, and explain users can enter their own question
  • If Oregon-only access is required, implement scope gating (need to clarify with the customer)
    • Ask which state they live in first, and if not Oregon, add block or provide friendly restriction message.
  • Add disclaimer that users can move between tools: they can start with chat and generate letter later OR they can start with letter and use chat for questions if needed.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.