> ## Documentation Index
> Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Notice Responses

> Review consumer responses to mailed collection notices that are routed through EcoMail Hub.

## Real-World Example

Jane receives a mailed collection notice from ABC Collections before ABC Collections has sent her a digital offer through the network. Jane logs into the consumer portal, uploads an image of the notice, selects the matching creditor profile from the EcoMail Hub directory, enters the account number and balance, and submits a settlement offer.

The system validates Jane's identity against the notice details, checks for duplicate accounts, and routes the response through EcoMail Hub. If ABC Collections is an active member, the response should appear in Creditor Portal -> Notice Responses and the sidebar badge should increase. If ABC Collections is not yet active, the response should stay held in EcoMail Hub until creditor portal delivery is available.

When ABC Collections reviews the delivered response, the creditor user can either add the account or return it to sender. The uploaded notice, account details, response type, routing history, and final outcome must remain historically tracked.

## Visual Flow

```mermaid placement="top-right" actions={true} theme={"system"}
flowchart TD
    A["Consumer starts Notice Response"] --> B["Upload mailed notice image"]
    B --> C["Validate consumer identity against notice"]
    C --> D{"Identity match?"}
    D -->|No| E["Reject submission"]
    D -->|Yes| F["Select or create creditor profile"]
    F --> G["Enter account number and balance"]
    G --> H["Run dedupe and routing checks"]
    H --> I{"Duplicate account?"}
    I -->|Yes| J["Stop duplicate workflow"]
    I -->|No| K["Submit response type"]
    K --> L["Route through EcoMail Hub"]
    L --> M{"Creditor active member?"}
    M -->|Yes| N["Deliver to Creditor Portal Notice Responses"]
    M -->|No| O["Hold in EcoMail Hub"]
    N --> P["Sidebar badge increases"]
    classDef default fill:#F8FAFC,stroke:#64748B,stroke-width:1.5px,color:#0F172A;
    classDef actor fill:#E0F2FE,stroke:#0284C7,stroke-width:2px,color:#0C4A6E;
    classDef system fill:#F8FAFC,stroke:#64748B,stroke-width:1.5px,color:#0F172A;
    classDef decision fill:#FEF3C7,stroke:#D97706,stroke-width:2px,color:#78350F;
    classDef risk fill:#FEE2E2,stroke:#DC2626,stroke-width:2px,color:#7F1D1D;
    classDef outcome fill:#DCFCE7,stroke:#16A34A,stroke-width:2px,color:#14532D;
    class A actor;
    class B,C,F,G,H,K,L,N,O system;
    class D,I,M decision;
    class E,J risk;
    class P outcome;
    linkStyle default stroke:#94A3B8,stroke-width:2px;
```

## Overview

Notice Responses allow consumers to digitally respond to mailed collection notices from inside the consumer portal, even when the creditor has not yet sent a digital communication through the network.

Consumers can:

* Upload a collection notice.
* Associate the notice with a creditor profile.
* Submit account details.
* Create a response such as Pay Balance, Settlement Offer, Payment Plan Offer, Dispute, or Other No-Pay Reason.

Notice Responses are routed through EcoMail Hub and delivered based on creditor membership status.

## Business Purpose

This feature converts mailed collection activity into structured digital negotiations and disputes without requiring the creditor to initiate first contact through the network.

The system acts as:

* A consumer intake workflow.
* A creditor identity matching workflow.
* A negotiation automation workflow.
* A response-routing system.

## Consumer Workflow

### Upload Notice

The consumer uploads a photo or image of the mailed collection notice. The notice must match the consumer's verified PII:

* Last name.
* Last four digits of SSN.
* Full SSN validation rules where applicable.

Failed identity matches should reject the submission.

### Select Creditor Profile

The consumer selects a creditor profile from the EcoMail Hub directory.

| Code | Type                  |
| ---- | --------------------- |
| AM   | Active Member         |
| PM   | Pending Member        |
| YP   | YouNegotiate Prospect |
| CP   | Consumer Prospect     |

Profile data can include creditor name, address, email, website URL, and phone number. If no creditor profile exists, the consumer may create a new profile entry. New consumer-created profiles are classified as `CP` (Consumer Prospect).

### Enter Account Information

The consumer enters:

* Account number.
* Current balance.
* Additional account reference information.

The system performs account deduplication, account ownership validation checks, and creditor routing checks. Only non-duplicate accounts continue processing.

### Submit Response Type

| Response Type       | Description                                   |
| ------------------- | --------------------------------------------- |
| Pay Balance         | Consumer agrees to pay the full balance.      |
| Settlement Offer    | Consumer proposes a reduced payoff.           |
| Payment Plan Offer  | Consumer proposes installment terms.          |
| Dispute             | Consumer disputes the account.                |
| Other No-Pay Reason | Consumer reports inability or refusal to pay. |

## Payment Method Restriction

Notice Responses must not collect payment methods.

This restriction exists because:

* The account may no longer be owned or serviced by the noticed creditor.
* The creditor has not yet added the account into the creditor portal.
* No merchant processor relationship can be associated with the account until the creditor validates and adds the account.

As a result, Notice Responses do not allow payment execution, payment authorization, bank account attachment, debit card submission, or credit card submission.

## EcoMail Hub Routing Logic

### Active Members

If the creditor profile is an Active Member (`AM`), the Notice Response is delivered directly into Creditor Portal -> Notice Responses.

### Pending And Prospect Profiles

If the creditor profile is `PM`, `YP`, or `CP`, the Notice Response is not delivered to a creditor portal. It enters a holding state inside EcoMail Hub and remains pending until:

* The creditor becomes an Active Member.
* Onboarding is completed.
* Portal delivery becomes available.

## Deduplication Logic

Before delivery, the system checks:

* Original account number.
* Existing portal account records.
* Prior imported accounts.

Duplicate accounts must not create duplicate negotiations, duplicate notice responses, or duplicate account insertions. Only non-duplicate records proceed.

## Creditor Review Workflow

Delivered Notice Responses appear in Creditor Portal -> Notice Responses. The sidebar badge count increases when a new unhandled response arrives.

The creditor user has only two available intake actions:

| Action           | Result                                                                                  |
| ---------------- | --------------------------------------------------------------------------------------- |
| Add Account      | Creates the account in the creditor portal and initiates automated response processing. |
| Return to Sender | Indicates the creditor no longer owns or services the account.                          |

No other intake actions are available. The creditor user cannot manually approve, manually reject, or manually update the response status directly from intake.

### Creditor Review Flow

```mermaid placement="top-right" actions={true} theme={"system"}
flowchart TD
    A["Delivered Notice Response"] --> B["Creditor user reviews notice and account details"]
    B --> C{"Creditor action"}
    C -->|Add Account| D["Create account in creditor portal"]
    D --> E["Run automated response processing"]
    C -->|Return to Sender| F["Reject response and notify consumer"]
    F --> G["Close workflow"]
    E --> H{"Response result"}
    H -->|Auto-approved| I["Close response as approved"]
    H -->|Negotiation required| J["Create Open Negotiations item"]
    I --> K["Badge count decreases"]
    J --> K
    G --> K
    classDef default fill:#F8FAFC,stroke:#64748B,stroke-width:1.5px,color:#0F172A;
    classDef actor fill:#E0F2FE,stroke:#0284C7,stroke-width:2px,color:#0C4A6E;
    classDef system fill:#F8FAFC,stroke:#64748B,stroke-width:1.5px,color:#0F172A;
    classDef decision fill:#FEF3C7,stroke:#D97706,stroke-width:2px,color:#78350F;
    classDef risk fill:#FEE2E2,stroke:#DC2626,stroke-width:2px,color:#7F1D1D;
    classDef outcome fill:#DCFCE7,stroke:#16A34A,stroke-width:2px,color:#14532D;
    class B actor;
    class A,D,E,J system;
    class C,H decision;
    class F risk;
    class G,I,K outcome;
    linkStyle default stroke:#94A3B8,stroke-width:2px;
```

## Automated Processing After Account Add

Once the creditor user selects Add Account, the system creates the account and automatically evaluates the consumer response.

### Auto-Approved Responses

The following response types automatically approve after the account is successfully added:

| Response Type       | System Action |
| ------------------- | ------------- |
| Pay Balance         | Auto-Approve  |
| Dispute             | Auto-Approve  |
| Other No-Pay Reason | Auto-Approve  |

These responses bypass manual review workflows.

### Settlement And Payment Plan Evaluation

Settlement Offers and Payment Plan Offers are compared against Creditor Master Pay Term Offers. The system compares:

* Settlement percentage.
* Monthly payment amount.
* Days-to-payment rules.

| Result                          | Action                                           |
| ------------------------------- | ------------------------------------------------ |
| Meets Creditor Master Pay Terms | Auto-Approve                                     |
| Does Not Meet Terms             | Deliver into Open Negotiations for manual review |

If the offer is not auto-approved:

* The account has already been added.
* The response converts into an active negotiation.
* The negotiation is delivered into Open Negotiations, Negotiations, and the Performance Dashboard.

These non-auto-approved responses function as digital counteroffers requiring creditor review.

### Post-Add Processing Flow

```mermaid placement="top-right" actions={true} theme={"system"}
flowchart TD
    A["Account added from Notice Response"] --> B{"Response type"}
    B -->|Pay Balance| C["Auto-approve"]
    B -->|Dispute| C
    B -->|Other No-Pay Reason| C
    B -->|Settlement Offer| D["Compare to master pay terms"]
    B -->|Payment Plan Offer| D
    D --> E{"Meets master terms?"}
    E -->|Yes| C
    E -->|No| F["Create active negotiation"]
    C --> G["Close Notice Response workflow"]
    F --> H["Deliver to Open Negotiations"]
    H --> I["Update Performance Dashboard"]
    G --> J["Preserve audit history"]
    I --> J
    classDef default fill:#F8FAFC,stroke:#64748B,stroke-width:1.5px,color:#0F172A;
    classDef actor fill:#E0F2FE,stroke:#0284C7,stroke-width:2px,color:#0C4A6E;
    classDef system fill:#F8FAFC,stroke:#64748B,stroke-width:1.5px,color:#0F172A;
    classDef decision fill:#FEF3C7,stroke:#D97706,stroke-width:2px,color:#78350F;
    classDef risk fill:#FEE2E2,stroke:#DC2626,stroke-width:2px,color:#7F1D1D;
    classDef outcome fill:#DCFCE7,stroke:#16A34A,stroke-width:2px,color:#14532D;
    class A,D,F,H,I system;
    class B,E decision;
    class C,G,J outcome;
    linkStyle default stroke:#94A3B8,stroke-width:2px;
```

## Return-To-Sender Workflow

If the creditor determines that the account is no longer placed, ownership changed, the account is invalid, or the creditor cannot process it, the creditor user may select Return to Sender.

The system should then reject the response, notify the consumer, close the workflow, and preserve the audit history.

## Sidebar Badge Behavior

Badge count should increase when a new unreviewed Notice Response arrives or new response activity occurs.

Badge count should decrease when the response status changes from new or unhandled, or when the creditor user reviews or processes the response.

Handled responses remain historically tracked but no longer count as new activity.

## Status Handling

Status changes must preserve audit history, communication history, and uploaded notice records. Responses must never be physically removed from tracking after handling.

## Recommended Response Statuses

| Status              | Meaning                              |
| ------------------- | ------------------------------------ |
| New                 | Newly received.                      |
| Pending Validation  | Awaiting checks.                     |
| Held                | Waiting for active membership.       |
| Auto-Approved       | Approved by rules engine.            |
| Pending Negotiation | Requires negotiation review.         |
| Returned            | Creditor no longer services account. |
| Closed              | Workflow completed.                  |

## Suggested Internal Events

| Event                       | Purpose                                     |
| --------------------------- | ------------------------------------------- |
| `notice_response_created`   | Consumer submission created.                |
| `notice_uploaded`           | Notice image uploaded.                      |
| `creditor_profile_selected` | Creditor linked.                            |
| `dedupe_completed`          | Duplicate validation completed.             |
| `response_routed`           | Routed through EcoMail Hub.                 |
| `auto_approved`             | Rule engine approved response.              |
| `negotiation_created`       | Negotiation generated from notice response. |
| `account_added`             | Creditor added account.                     |
| `response_closed`           | Workflow completed.                         |

## How It Should Work

* It should show only Notice Responses associated with the creditor.
* It should preserve all consumer response details.
* It should maintain historical response tracking.
* It should update sidebar counts accurately.
* It should route responses based on membership status.
* It should auto-process qualifying response types.
* It should deliver negotiation exceptions into Open Negotiations.
* It should prevent duplicate account creation.
* It should preserve uploaded notice images and routing history.

## How It Should Not Work

* It should not show responses for unrelated creditors.
* It should not create duplicate accounts.
* It should not lose uploaded notice images.
* It should not remove handled response history.
* It should not continue showing handled responses as new.
* It should not allow payment method collection.
* It should not deliver responses to inactive or non-member portals.
* It should not allow manual approve, reject, or status editing from the intake stage.

## Developer Notes

* Notice Response intake is separate from Open Negotiations until an account is added and a non-auto-approved settlement or payment plan offer becomes an active negotiation.
* Payment method collection must stay unavailable in Notice Responses.
* Add Account and Return to Sender are the only creditor intake actions.
* Status changes must preserve uploaded notice records, communication history, routing history, and audit history.
* Deduplication must run before account creation or negotiation creation.
* EcoMail Hub membership status controls delivery to the creditor portal.

## Related App Areas

* `app/Livewire/Creditor/ConsumerOffers`
* `app/Livewire/Creditor/NoticeResponse`
* `app/Livewire/Creditor/Dashboard`
* `app/Livewire/Creditor/Dashboard/Stats`
* `app/Livewire/Consumer/NoticeResponse`
* EcoMail Hub
* Creditor Portal
* Consumer Portal
* Open Negotiations
* Performance Dashboard