Compensable

Governed cadences

The stalled docket, worked.

Reactivation for claimants who went quiet. Document-chase for unreturned releases. Retainer-chase to signature. Every step checked against the floor before it fires.

Cadence spec · doc-chase v2sample

enroll: claimants where docs.outstanding > 0

step 01 · day 0 · call — request releases

step 02 · day 2 · sms — e-sign link

step 03 · day 6 · call — final reminder

stop: inbound reply · docs received · opt-out

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, lease-based scheduling that won't double-fire even across multiple workers. But firing is never its call: every touch is submitted to the governance gate, and a touch that fails any check is held with the reason written down.

Outbound governance ledgersample
TouchGateResult
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 touch is held. Unknown means no.

Scheduler · claimant-local timesample

touch 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 enrollment immediately, across channels. Frequency caps bound touches 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 · sha256:2b7d…90e1

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.