Correspondence

Parked — not currently shipped

The Correspondence staff UI has been removed and its API/worker handlers are parked under archive/ pending a rehome onto the greenfield tenant spine. The pages below describe the intended behaviour and the parked implementation — they are not reachable in the running app today. See the module architecture note for status.

Correspondence is the staff-ops mail-intake module. Statutory and agency mail arriving in the firm's mailbox is captured, OCR'd, classified, matched to the right client, held for an operator's review, and then dispatched per clean item. It is staff-only — there is no client portal surface.

The work surface was /dashboard/correspondence (parked — see the note above).

Who does what

• Correspondence Operator — works the queue: triggers OCR, reviews extracted items, confirms or fixes the client match, and dispatches clean items.
• Correspondence Reviewer — everything an operator does, plus manages the configuration (mailbox polling, dispatch mode, the grace window, matching).

See Roles & permissions.

The pipeline

Firm mailbox (has attachment)
  → poll & download → store the PDF, create a correspondence document
  → OCR + classify → extract client rows → split into per-item PDFs
  → match the client (optionally via Odoo)
  → operator review
  → dispatch one email per clean item (after the grace window), honouring the dispatch mode

Start here

• Quick start — mailbox to dispatch — the whole arc in one read.

How to

• Review a correspondence item
• Confirm or fix a client match
• Dispatch a clean item
• Handle an exception

Troubleshooting

• OCR confidence is low
• No client matched
• Dispatch didn't go out

Reference

• Architecture & pipeline detail: Correspondence module.
• RBAC matrix · Notifications catalog