AI team

Reads a new settlement agreement and suggests the case setup details — settlement amount, payment rules, tax split, deadlines, escalator terms — each with the exact wording from the agreement. Your team approves or corrects every suggestion before anything is saved, and unanswered obligations become ready-to-send questions for counsel.

The front door for claim documents from every channel — mail, fax, email, and the QR portal. Each document in a claim batch is read, given a unique claim number, checked for duplicates and identity mismatches against the class-member list, and nothing is filed without your approval. Requests to be excluded (opt-outs) are recognized too — they're logged in their own bucket and never given a claim number.

Lucy reads the case's support mailbox, sorts every message into a queue and drafts the replies and opt-out plans. Nothing is sent and no member record changes until a person approves it, and every step is written to the case's audit trail.

Lucy Live is the chat channel. It is nearly ready in its own service; its control plane moves into ApexOS after Lucy E-mail settles.

Lucy Voice layers on Lucy Live and arrives with it.

Drop in the class list from counsel — the messy file is fine. Every row gets an ID before anything is touched, names and addresses are standardized, SSNs are validated and masked, duplicates and discrepancies are caught and escalated (never deleted), and workweeks are calculated from the class period. You approve the cleaned list before it is adopted, and every flagged row waits for a person.

QSF setup, check reissue, positive pay, tax forms and digital payments are mapped from the disbursement team's meetings and not built yet.

Upload an address workbook and every row is formatted under a profile. Describe a formatting change in plain words and the assistant proposes the profile; you preview the prepared rows, apply it and download the workbook.

Downloads the latest USPS address-change files, opens them into the mailroom inbox, and keeps the same folder and file output used by the current process. Each parsed batch waits for a person to confirm it.

Upload a template and a workbook, confirm the field mapping, and download the merged PDFs or the e-mail audience. Nothing is held after the merge finishes.

The staff roster and pending access requests. An administrator changes a person's departments through one approval per change, and turns sign-in off or on directly.

Law firms ask for attorney-portal logins from the portal sign-in page. Review each request here, then approve or deny it. An approval creates the sign-in account, updates Dynamics, and sends the firm their welcome email — only after you confirm. Approved sign-ins can later have their password reset or the account deleted, with the same confirmation.

Turns captured operating knowledge into a searchable wiki. It proposes new entries from meeting notes and uploads, and a person reviews every change before it is published.