Each field comes back with the box it was read from and a confidence built from the model, the OCR and how well the two agree. A second model can check the first one's work. Your reviewer confirms with Enter and moves on, instead of retyping a form into another form.

Intake rules decide what gets in at all. They read the sender, subject, body and attachments of an email, or the name, folder and age of a file, and anything the fields cannot say you can ask a model. Try it runs the rules against the real folder and imports nothing.

Rules run after every extraction: patterns, ranges, dates, expressions across fields, a call to your own endpoint, and matches against reference data you upload or sync. A near miss arrives with the closest real value, one click away.

When a document reaches a point in its life, check its conditions and act: approve it, route it, assign it, set a deadline, send it to a system of record. Every evaluation is logged with the values it compared and what each action did.

Is this urgent? Which queue does it belong to? What is the referring NPI? A condition or an action can be a question in your own words. The model's answer and its reason go into the run log, and below the confidence you set, nothing happens.

A Salesforce source watches one object and pulls the files attached to matching records, classic attachments included. A destination writes what was extracted onto any object you map, finds parent records by searching for them, and can put the original file back on the record.

Deadlines that count business hours and holidays. Assignment by turn or by lightest load. Notifications for mentions and breached SLAs. A command palette that searches inside extracted values, and throughput counted in the database so it stays true at any volume.

When reviewers keep fixing the same field, DocuFlow proposes a short instruction for it, and nothing reaches the extraction prompt until someone accepts it. Evaluate scores any change against a golden set of approved documents, field by field, before it ships.

Each call is filed against the work that caused it: extracting a claim, a rule asking a question, a reviewer asking the document. See spend by day, model, queue and document, and open any run to read it call by call.

Permissions are module and action pairs, granted to people, teams and API keys across the workspace or inside one queue. A clinical reviewer can approve prior authorizations and never open a claim. Every change is logged with who made it, when, and from where.

Send an Idempotency-Key and retry as often as the network makes you: the first answer is replayed for 24 hours. Every response carries a request id and your remaining budget, every error a stable code to branch on, and every webhook a signature.

A queue is one kind of document: its fields, its rules, where it comes from and where its data goes. Prior authorizations and claims run beside credentialing packets and vendor invoices, each with its own reviewers, deadline and threshold.