Skip to main content

Real-World Example

Jane receives a collection notice and starts a response. Until the response is completed or converted into an account action, the My Accounts page should keep it visible under Notice Responses so Jane can return and finish.

Visual Flow

How It Should Work

  • It should surface notice response records that still matter to the consumer.
  • It should let the consumer continue the response from the right step when possible.
  • It should keep notice response counts and account status aligned.
  • It should include returned notice responses when a payment-declined account is tied to a declined or closed notice response.
  • It should show sender details when available and fall back safely when the sender target has been removed.
  • It should allow the consumer to delete a returned notice response only when the identity keys match.

How It Should Not Work

  • It should not lose a partially completed response after the consumer leaves the page.
  • It should not show another consumer notice image or sender details.
  • It should not keep completed responses as unresolved action items.
  • It should not mix returned notice responses into the normal Declined / Closed Negotiations tab.
  • It should not break the current portal session if the returned notice response being deleted is also the authenticated consumer row.

Developer Notes

  • This tab maps to notice_responses.
  • Notice response work spans StartNoticeResponseController and the Livewire step components.
  • Returned notice response cleanup soft-deletes only eligible returned responses. If the deleted row is the authenticated consumer, the app reuses or creates a replacement consumer row so the portal remains usable.
  • app/Enums/ConsumerStatus.php
  • app/Http/Controllers/Consumer/StartNoticeResponseController.php
  • app/Livewire/Consumer/NoticeResponse/Index.php
  • app/Livewire/Consumer/MyAccount.php
  • app/Livewire/Consumer/Traits/MyAccounts/StartOver.php
Last modified on June 1, 2026