Use cases

Read payment calls and texts with bankruptcy clients

Finds promises to pay, requests for a payment arrangement, hardship, fee disputes, missed Chapter 13 plan payments and requests to stop contact, and flags pressure from staff.

Try it on this example

Example · A call about two missed plan payments after a job loss

Channel (call, SMS, email): Call

The whole conversation, oldest message first

Hi, this is Derek from Lakeshore Debt Law accounts. I'm calling because the trustee shows your last two plan payments as missed. Yeah, I lost my job at the warehouse in August. I can pay 150 on the 15th when my unemployment comes in, can we do the rest later? If you don't pay the whole thing we'll just drop your case and you'll lose everything, honestly that's on you. Okay. I'll pay the 150 on the 15th.
  1. Does the client promise a specific payment?Yes97%
  2. Does the client ask for a payment arrangement or more time?Yes98%
  3. Does the client describe a hardship affecting payment?Yes98%
  4. Does the client dispute what they owe the firm?No91%
  5. Does the conversation show the client is behind on Chapter 13 plan payments?Yes97%
  6. Does the client ask the firm to stop calling, texting or emailing them?No93%
  7. Does staff pressure or threaten the client?Yes89%

These are real answers stored from one run on this example.

The prism behind it

Read payment calls and texts with bankruptcy clients7 questions

Fields

  • Channel (call, SMS, email)
  • The whole conversation, oldest message first

Context

We are Lakeshore Debt Law, a consumer bankruptcy firm. The text is a conversation between our accounts receivable staff and a client about the client's attorney fees or Chapter 13 plan payments, oldest message first; it may have no speaker labels. The answers set follow-ups for the accounts team and flag conversations a supervisor should read. Amounts and dates are recorded by the team, not here.

Questions

  1. Does the client promise a specific payment? Yes / No

    Yes: The client commits to paying a stated amount, or by a stated day. No: No specific commitment is made. A vague intention such as "I'll try" is not a promise.

  2. Does the client ask for a payment arrangement or more time? Yes / No

    Yes: The client asks to split, reduce, delay or reschedule a payment. No: No such request appears.

  3. Does the client describe a hardship affecting payment? Yes / No

    Yes: The client mentions job loss, reduced hours, illness, a death, a new expense or another reason they cannot pay. No: No hardship is described.

  4. Does the client dispute what they owe the firm? Yes / No

    Yes: The client says an amount is wrong, was already paid, was never agreed, or that the service was not provided. No: The client does not dispute the amount.

  5. Does the conversation show the client is behind on Chapter 13 plan payments? Yes / No

    Yes: The client or staff says a trustee or plan payment was missed or is late, or a motion to dismiss was mentioned. No: Nothing shows missed plan payments, or the case is not a Chapter 13.

  6. Does the client ask the firm to stop calling, texting or emailing them? Yes / No

    Yes: The client asks to stop some or all contact, in any words. No: No such request appears.

  7. Does staff pressure or threaten the client? Yes / No

    Yes: Staff threaten to drop the case, to report the client, or other consequences not stated as firm policy, or use insulting or shaming language. No: Staff explain the balance, the options and the policy plainly. Stating a real consequence calmly, such as that a missed plan payment can lead the trustee to ask for dismissal, is not pressure.

Lens columns

promise_to_pay, promise_to_pay_probability, arrangement_requested, arrangement_requested_probability, hardship, hardship_probability, fee_dispute, fee_dispute_probability, plan_payments_behind, plan_payments_behind_probability, stop_contact, stop_contact_probability, staff_pressure, staff_pressure_probability

Run it on your own text

Add this prism in the app, change any question, and test it on a file of your own.

Ask for an invite