Feedback & Notification Fix¶

Source: Call 35 (3-18) Priority: Tier 1 — must fix before 3/25 visit KB Requirement IDs: #154-#155

The Problem¶

Dr. Bawa left feedback through the system and Chris didn't receive it. This is a trust-breaking reliability issue. If stakeholders can't be confident their feedback reaches the team, they'll stop using the feedback mechanism.

Bawa: "I had shared some feedback, did you get any of it?... I did put in a couple of comments."

Requirements¶

Feedback must be reliably received (KB #154)¶

When someone submits feedback through the app, it must: 1. Be stored in the database (verify convo_feedback or clinic_feedback table) 2. Trigger an email notification to Chris 3. Be visible in the BCC portal feedback view

Clear feedback workflow (KB #155)¶

Bawa: "What is the best way for us to communicate our feedback to you? Is that gonna be by clicking on the feedback tab and typing it out?"

Bawa and Lauryn need a simple, obvious path to leave feedback. Currently available: type or speak in the feedback tab. This needs to work reliably.

Action Items¶

Before 3/25 visit:¶

Verify feedback storage: Check the database for any feedback Bawa submitted. Did it get stored but not emailed? Or did it fail to store entirely?
Test email notifications: Submit test feedback from a patient-facing session. Verify:
Email sends on feedback submission
Email sends on user login
Email contains useful context (who, when, what they said)
Fix whatever broke: Could be email service configuration, webhook failure, or notification code regression.
Send Lauryn her own link: She needs independent access to leave feedback separately from Bawa. Create a separate feedback path so their inputs are logged individually.
Test on phone: Bawa and Lauryn will use phones/home computers due to office firewall. Verify the feedback flow works on mobile.

Current AI response delay (KB #156)¶

Bawa: "That's okay, I think it's fine."

The delay during feedback review (while AI processes) is acceptable. Not a priority to fix.