Back to DocuFlow

Rules that run themselves, and say why

A queue used to have one knob: always review, auto-approve, or a confidence threshold. Automations replace the knob with rules. When a document reaches a point in its life, if its conditions hold, do a list of things, in order, and write down what happened.

When, if,
then

Seven triggers cover a document's life, from arriving to waiting too long. Conditions read document attributes, extracted fields, reference data, an expression or a question for a model. Eighteen actions approve, reject, hold, route, assign, tag, set fields and deadlines, notify, deliver, or call a URL with the authentication it needs.

Automations

Auto-approve clean prior auths

OnExtraction finishedPrior authorizationsmatched 1,284 of 1,902
RuleActivity 1,902

If

Leave this empty to act on every document that reaches the trigger.

AllAnyof these must be true
  • Lowest field confidenceis at least90 %
  • and
    Validation errorsis at most0
  • and
    Health planis in data setPayer plans

Then

Actions run in order. One that cannot run is recorded and the rest continue.

  1. ApproveApprove the document without a reviewer.
    NoteEvery field at or above 90%, plan on file, no rule errorsShows on the document's timeline so the decision is explainable.
  2. TagAdd or remove tags.
    Add
    straight-throughTag and press Enter
  3. Run a destinationDeliver the document through one of the queue's destinations.
    DestinationSalesforce · Case decision
Activity1,902Auto-approve clean prior auths
  1. UHC_precert_MRI_lumbar.pdf41 ms

    Conditions

    • Lowest field confidenceis at least90%· was94%
    • andValidation errorsis at most0· was0
    • andplan.nameis in data setpayer-plans· wasAetna Choice POS II

    Actions

    • Approved: every field at or above 90%, plan on file
    • Tagged straight-through
    • Delivered to Salesforce · Case 00188213
  2. fax_20260918_0912.tif12 ms

The desk around
the rules

Deadlines count only the hours your calendar is open, holidays included, so a Friday evening fax is not overdue by Monday morning. Work is assigned by turn or to whoever has the least open, and a breach tells the people who manage the queue.

Business hoursCentral Time
DayOpen
Mon8:00 AM – 6:00 PM
Tue8:00 AM – 6:00 PM
Wed8:00 AM – 6:00 PM
Thu8:00 AM – 6:00 PM
Fri8:00 AM – 5:00 PM
SatClosed
SunClosed

Holidays

Thanksgiving DayNov 26

Notifications⇧N

Notifications

AllUnread 2

Today

  • SLA breached: aetna-pa-whitfield.pdfPrior authorizations · due 18 minutes ago18 minutes ago
  • Priya Raman mentioned you@Dana can you confirm the plan name on this one?40 minutes ago
  • Assigned to you: UHC_precert_MRI_lumbar.pdfRound-robin · Prior authorizations2 hours ago
Command palette⌘K
W29188esc

Documents

aetna-pa-whitfield.pdfMember IDW2918847301
Needs review
whitfield_mri_referral.pdfMember IDW2918847301
Approved

Actions

Show all documents matching “W29188
Queue · Work managementPrior authorizations

Service level

How quickly documents in this queue should be handled, from the moment they arrive.

72hours

Assignment

Who picks up new work.

Analyticslast 14 days

Auto-approved

76%

3,412 of 4,488 approved

Median processing

14.2 s

p95 41.8 s

Documents per day

By final status

approvedneeds reviewrejectedfailed

Included

Dry runevaluate a draft against recent documents, changing nothing
Eleven templatescomplete rules that open turned off
Ordered per triggera catch-all can stop the rules below it
Loop guardat most eight actions on one document per rule per hour
Outbound authbearer, basic, header, query, HMAC or OAuth2 client credentials
Best efforta failing rule never stops a document from being processed

Bring the forms your team still retypes

A working session on your own documents: one queue, your fields, your rules, and a count of what would have gone straight through.