Plans
Three plans, sized by the work.
Every plan is a custom agent, built in house and kept current, sized by how many systems, how much judgment and how many rules the work carries.
The plans
Relay, Navigator, Sentinel.
Relay
One system, clear rules, no judgment calls
- Systems
- Document AI
- Rule depth
- Autonomy
- Scope
- One application, the same path every time
- Inputs
- Forms, spreadsheets and exports
- Decisions
- Each field filled by a written rule
- Regulated data
- Not included
- Verification
- Every field checked before it saves
- Schedule
- Scheduled runs
- Audit
- Run receipts
Navigator
Several systems, regulated data, some judgment
- Systems
- Document AI
- Rule depth
- Autonomy
- Scope
- Several systems in one task
- Inputs
- Scans, PDFs and faxes too, read by AI
- Decisions
- Judgment calls, with unsure items sent to a person
- Regulated data
- Handled under a BAA where health information is involved
- Verification
- Every field checked before it saves, on every screen
- Schedule
- Scheduled runs
- Audit
- Receipts, with the reason for every decision
Sentinel
Complicated tasks, many systems, detailed rulebooks
- Systems
- Document AI
- Rule depth
- Autonomy
- Scope
- Many systems, many paths
- Inputs
- Documents that vary widely, checked against each other
- Decisions
- Detailed rulebooks, with every kind of exception named
- Regulated data
- Handled under a BAA where health information is involved
- Verification
- Every field checked, and records matched across systems
- Schedule
- Scheduled autonomous runs, around the clock
- Audit
- Full audit trail, evidence kept on your workstation
Every plan includes
Built, run and kept current, on every plan.
10 engineering hours a month
For upkeep and changes.
Remapping when your software updates
From those hours.
Health checks with alerts
Launches with the alert path.
Connection loss recovery
A weekly 30 minute check in
One point of contact on each side.
The six week launch
Support by severity
The standard is below.
Larger changes scoped first
A new workflow or system is a scoped build, never a surprise invoice.
Support standard
Response targets by severity.
| Severity | What it means | Relay | Navigator | Sentinel |
|---|---|---|---|---|
| Critical | The agent has stopped and work is not moving | 2 hours, around the clock | 1 hour, around the clock | 30 minutes, around the clock |
| Standard | Running, but a step needs attention | Next business day | 4 business hours | 2 business hours |
| Change | A new rule, field or screen | Scheduled into the monthly hours | Scheduled into the monthly hours | Scheduled into the monthly hours |
Response means a person is working on it, and because the agent stops instead of guessing, a critical issue delays work but never files anything unverified.
What the monthly hours cover
Changes that keep the agent current.
Rule changes
A guideline changes, the rules are updated and dated, and the record shows which version ran.
Dated rule changes · Reasons recorded
New fields and small new steps
Another field to read, another screen to confirm, inside the same workflow.
Remapping after software updates
The agent is taught the changed screens again and tested before it runs on its own.
New screens mapped · Tested again
Report changes
A new column, a new recipient, a new schedule.
Run record reviews
Receipts and reasons read with you, exceptions explained.
Evidence capture · Audit trail
A new workflow or system
Scoped and agreed first, as its own build.