Product: Section 2b: Guest Intake Profile | USER STORY | Contact Information

## 🧩 Overview
We need to allow guests to specify their preferred contact method (text or email) and provide the corresponding contact information. This will ensure they can receive and respond to communications from the program coordinators in a way that is most convenient for them, improving engagement and response rates.

## 🧠 Problem Statement
Guests currently have no way to choose how they prefer to be contacted or provide up-to-date contact details. This can lead to missed or delayed communications from coordinators, affecting the efficiency and responsiveness of the program.

## 🙋‍♀️ User Story
As a Guest,
I want to specify my preferred contact method (text or email) and provide the relevant contact information,
So that I can monitor and respond to program communications in the most convenient way.

## 🎯 Acceptance Criteria (Definition of Done)

- [ ] Guest can choose a preferred contact method from a dropdown or radio buttons (email or text).
- [ ] Guest can input a valid email address or phone number, depending on their selected contact method.
- [ ] System validates the contact information format (e.g., valid email format, 10-digit U.S. phone number).
- [ ] If the input is invalid, the system displays a descriptive error message and disables saving until corrected.
- [ ] Valid data is saved and accessible via backend/database.

## 🔍 Context / Background

- Design reference: [Guest Wireframe - Contact Information](https://www.figma.com/design/BNWqZk8SHKbtN1nw8BB7VM/HUU-Main-File---11%2F2024?node-id=16750-1149&t=9HUcBpMOpOt8fCAD-4)
- This aligns with our broader goal of streamlining communication between guests and program coordinators.
- Related initiative: Guest Profile Experience enhancement
- Part of the shared housing application project under Hack for LA

## 🖼️ Design Notes (Preliminary)

- Is this feature ready for design work? ✅Yes
- Consider leveraging existing input validation components from the design system.
- Layout and UX patterns should align with the Guest Intake Form.

## 📌 Scope Considerations (In/Out Scope)
[Feature List](https://docs.google.com/spreadsheets/d/1uM287TOz20jnXPS4kRe0Dt5GlhnPbNRYBHHOxcamCJ0/edit?gid=343529642#gid=343529642)

- #### In Scope:
- Contact method selection
- Input and validation of contact information

- #### Out of Scope (future or separate stories):
- Notification preferences
- Multi-channel fallback logic
- Admin/coordinator tools for updating guest contact details

## 🛑 Constraints / Risks / Workflow Dependency

- Must adhere to contact data privacy and handling practices.
- May require coordination with backend and auth services for updating user records securely.
- Consider accessibility needs (screen reader-friendly inputs, error messages).

## ✅ Action Items

- #### Assign and Prep
- [ ] Product Manager: Understand, draft User Story and self-assign
- [ ] Product Manager: Conduct the necessary research (if applicable), clarify any questions
- [ ] Product Manager: Work with PM team/lead to clarify any questions about the User Story
- [ ] Product Manager: Work with Product Team Lead to assign the appropriate size & complexity
- [ ] Product Manager/Lead: determine if work should be split into multiple issues, if so, create issue(s) and link them in this issue (if applicable) or create as standalone.

- #### Draft and Review:
- [ ] Product Manager: Change Issue Status to "In Progress"
- [ ] Product Manager: Draft User Story
- [ ] Product Manager: Change Issue Status to "For Review/Feedback Needed"
- [ ] Product Manager: Add Label "Ready for: Design Peer Review"
- [ ] Product 1st Level/Peer Review: Review and provide comment(s); tag assignee
- [ ] Product 1st Level/Peer Reviewer: Update status to "Questions/Clarification" if needed
- [ ] Product Manager (Assignee): Update status to "In Progress" and resolve comments
- [ ] Repeat steps as needed
- [ ] Product 1st Level/Peer Reviewer: Update to "For Review/Feedback Needed" and label "Ready for: Product Lead"
- [ ] 2nd final/Product Lead: Review and provide final feedback
- [ ] Resolve remaining comments

## 🔗 Related Tickets

- Design Ticket: [link]
- Engineering Ticket: [link]
- QA Test Plan: [link]

## 📎 Resources & References

- Existing Research: [Link]
- Brand Guidelines / Design System: [Link]
- Previous or Related Designs: [Link]
- Mockups/Designs: [Guest Wireframe - Contact Information](https://www.figma.com/design/BNWqZk8SHKbtN1nw8BB7VM/HUU-Main-File---11%2F2024?node-id=16750-1149&t=9HUcBpMOpOt8fCAD-4)