25 lines
966 B
Markdown
25 lines
966 B
Markdown
|
|
---
|
||
|
|
title: "Co-buyer/couple support on client profiles"
|
||
|
|
area: clients
|
||
|
|
status: backlog
|
||
|
|
created: 2026-04-03
|
||
|
|
---
|
||
|
|
|
||
|
|
# Co-buyer/couple support on client profiles
|
||
|
|
|
||
|
|
## Summary
|
||
|
|
|
||
|
|
Agent wants to add multiple people to one client record (e.g. a buyer couple). Add `coName` and `coEmail` optional fields to the `clients` table. Show both names on client card and document dashboard. Both names available as AI pre-fill targets.
|
||
|
|
|
||
|
|
## Notes
|
||
|
|
|
||
|
|
Real estate standard: primary buyer + co-buyer on the same contract. Simple schema addition — new Drizzle migration, update ClientCard UI, update seed data.
|
||
|
|
|
||
|
|
## Scope
|
||
|
|
|
||
|
|
- New Drizzle migration: add `coName` (text, nullable) and `coEmail` (text, nullable) to `clients` table
|
||
|
|
- Update `ClientCard` component to display co-buyer name when present
|
||
|
|
- Update document dashboard to show both names
|
||
|
|
- Expose both names as AI field pre-fill targets (e.g. `co_buyer_name`, `co_buyer_email`)
|
||
|
|
- Update seed data to include at least one couple example
|