Real-World Example
Maya starts her day on the Dashboard. She opens Pending/Delivery first to see responses that still need creditor matching or delivery work, then checks Delivered/Pending, Completed/Added, Return to Sender, and YN Returned.
Each dashboard tab should show the matching notice responses, allow searching/sorting, and let Maya export the current bucket when needed.
Visual Flow
Dashboard Buckets
Status Abbreviations
The dashboard also shows creditor member/prospect counts beside the notice-response buckets.
How It Should Work
- It should show only notice responses that belong in the selected status bucket.
- It should keep search, sort, pagination, and export aligned with the selected bucket.
- It should export a CSV only when the bucket has matching responses.
How It Should Not Work
- It should not mix completed, pending, returned, and closed responses into one unexplained list.
- It should not export an empty report as if work exists.
- It should not show notice responses that have no consumer relationship.
Developer Notes
- Dashboard tabs are separate Livewire components backed by shared notice-response service rules.
- Dashboard member/prospect counts come from the creditor profile service, while notice-response bucket counts come from the notice-response service.
- Status bucket logic is more important than the tab label; avoid duplicating this logic casually.
routes/ecomailhub/index.php
app/Livewire/ConsumerResponseManager/Dashboard
app/Services/ConsumerResponseManager/NoticeResponseService.php
app/Services/ConsumerResponseManager/CreditorProfileService.php
app/Exports/ConsumerResponseManager/DashboardNoticeResponseExport.php
Last modified on May 26, 2026