Worklists and rules

Send the accounts you already work, and the rules that decide what happens to each one.

Daybook runs on your data and your rules. You don't rebuild your data collection: send the worklists and exports you already have, and write down what you'd tell a biller. Daybook does exactly that, then moves on to the next account.

Worklists

A worklist is a set of accounts: the AR report, the denial queue, tomorrow's schedule. Send it as JSON items or as a link to an export from your PM system. Daybook maps the standard columns (payer, member, claim, balance) and keeps the rest as metadata, so every result comes back with your own ids.

{
  "name": "AR over 30 days",
  "csv_url": "https://example.com/exports/ar-30.csv?token=...",
  "rules": ["rule_01JBXJ1"]
}

Rules

A rule is when plus then. The trigger is an event or a condition on worklist items. The action is anything you can do through the API.

{
  "name": "Chase silent claims",
  "when": { "condition": "days_since_submission >= 30 and status == \"no_response\"" },
  "then": { "action": "claim_status.check" }
}

Scripts and training docs

Call scripts and training docs become the instructions Daybook follows on payer calls and in portals. Upload them in the Daybook app and reference them by id, such as the script field on Start a call. On a call started from a claim in the app, the voice agent follows the call script that fits the claim's open step.

Results

Every item reports back the way you choose: over the API, as webhooks, or as a file you pull into your PM system.