Log interaction flow starts with empty type — no triggering action pre-filled #104

New issue

Closed

opened 2026-06-12 04:22:33 +00:00 by Mark · 0 comments

Mark commented

2026-06-12 04:22:33 +00:00

Owner

Current behavior:

PersonDetail -> Log button -> /log?personId={id} -> type empty -> user must select type manually
The Home page already passes type correctly: /log?type=Call, /log?type=Text, /log?occasion=Gift

Expected: When navigating to log an interaction in a context that implies the type, pre-fill it. Options:

Separate Log Call, Log Text, Log Email buttons on PersonDetail that navigate with type preset
A type picker inline in the Log button that then navigates with the right query param
Default the type to the persons most common interaction type when none is specified

Why it matters: Friction point - logging should be faster, not require an extra step to state the obvious.

Problem: Navigating to the Log Interaction page from PersonDetail (/log?personId=X) pre-selects the person but leaves the interaction type empty. The user has to manually pick Call/Text/Email/etc. even though the triggering action (logging a call, message, or interaction) is the entire reason they navigated there. Current behavior: - PersonDetail -> Log button -> /log?personId={id} -> type empty -> user must select type manually - The Home page already passes type correctly: /log?type=Call, /log?type=Text, /log?occasion=Gift Expected: When navigating to log an interaction in a context that implies the type, pre-fill it. Options: 1. Separate Log Call, Log Text, Log Email buttons on PersonDetail that navigate with type preset 2. A type picker inline in the Log button that then navigates with the right query param 3. Default the type to the persons most common interaction type when none is specified Why it matters: Friction point - logging should be faster, not require an extra step to state the obvious.