Compensable

Governed follow-up

The stalled docket, worked.

Recovery follow-up sequences (we call them cadences): reactivation for claimants who went quiet, document-chase for unreturned releases, and retainer-chase to signature. Every step is checked against The Floor before it's sent.

Compensable · follow-upsample datasample
The sequence register: live follow-up sequences with enrollment counts, step timing, and draft states

A call that can't be proven allowed doesn't get placed.

How it works

Sequences with a conscience and a scheduler.

The cadence engine owns timing: retries, step advancement, scheduling that won't double-text a claimant even under heavy load. But sending is never its call: every call and text is checked by The Floor, and an attempt that fails any check is held with the reason written down.

Outbound governance ledgersample
AttemptCheckResult
16:02:11REACTIVATE✓ CLEARED
16:02:14DOC-CHASE✓ CLEARED
16:02:19RETAINER✓ CLEARED
16:02:23REACTIVATE⏸︎ HELD

held: QUIET_HOURS · TX Bus.&Com. §301.051 · resumes 09:00 CT

audit chain sha256:9f2c…41ab → verified

Curfews are computed in the claimant's local time at the stricter of the federal window and the state's own telemarketing statute. The state table carries its citations. If the timezone can't be resolved, the attempt is held. Unknown means no.

Scheduler · claimant-local timesample

call due 20:40 CT · claimant in TX

federal window: 08:00–21:00 ✓

TX Bus.&Com. §301.051: until 21:00, Sun rules apply ✓→✗

stricter rule wins → HELD · resumes 09:00 CT

An inbound reply, a received document, an executed retainer, an opt-out: any of these ends the sequence immediately, across channels. Frequency caps bound attempts per channel and across channels, so persistence never curdles into harassment.

Stop conditions · enrollment CLM-04185sample

14:22 · inbound sms received from claimant

→ enrollment terminated · all channels

14:22 · pending step 03 cancelled

14:22 · audit event appended · sealed, tamper-evident

Thirty minutes. Bring the stalled docket.

We'll run a live call, work a sample docket, and show you the system refusing a call it shouldn't make.