Skip to main content

Real-World Example

Alex invites Example Recovery to connect his water account. A company user chooses Add in Negotiations → Consumer Requests. The account appears as Offer Delivered, and Alex can review it in New Offers after signing in. He receives an email when his email preferences allow it. For several requests, use Add All or Reject All. Added rows stay visible; rejected rows leave the table.

Visual Flow

How It Should Work

  • Review the consumer, company, account name, number, balance and submission date.
  • Manage requests from the main company account. Complete required setup and membership payment before adding accounts.
  • Add: use the saved account details, existing consumer profile and company offer terms. No file upload is needed. Bill type, sub-account and expiry remain empty.
  • Add All: add every unadded request across all pages, including requests accepted before direct addition was available. Add All and Reject All run in the background in small groups. Refresh the table and sidebar count while processing finishes, just as with Notice Responses.
  • If a bulk action stops, completed groups stay saved. Refresh the list and retry the remaining requests.
  • Show Added once complete, keep the row visible and reduce its pending badge once.
  • Reject / Reject All: remove unadded requests from the table and keep history. Reject All covers every page. Neither bulk action is limited by table search.
  • Count new hosted accounts against the membership allowance. If additional accounts are allowed, apply the configured weekly account charge; a saved payment method is required. Otherwise, ask the user to select fewer accounts or upgrade.
  • Send the saved account-added email when consumer permissions allow it. Delivery can complete after the account is added.
  • Count only requests waiting for a decision in the sidebar. Refreshing, retrying or changing pages must keep counts correct.

How It Should Not Work

  • Do not add the same account, notify the consumer or charge for it twice because an action is repeated.
  • Do not reject a request while it is being added or use Reject to remove an already added account.
  • Do not mark queued work as complete or a queued charge as paid.
  • Do not start a payment plan or accept an offer on the consumer’s behalf.
  • Do not show another company’s requests or mix requests into Notice Responses.
See Invite Creditors for the consumer’s two-step flow.
Last modified on November 1, 2026