How decisions are made
A Falnor workflow does not act blindly. Every decision follows a defined path - with inputs considered, rules applied, approvals enforced, and every step recorded for review.
What inputs are considered
Before any action is taken, the system gathers and considers five categories of input. No decision is made on a blank prompt.
Case context - records, rules, and history gathered from your systems
Business rules - the policies that shape what can happen automatically
Approval thresholds - amount, risk, or sensitivity triggers that require a human
Prior decisions - what has already been approved or checked in this case
System state - what is true right now across the systems involved
How business rules and approvals interact
Every step follows one of four paths. The path is determined by the inputs, the business rules, and the approval thresholds you set - not by the model guessing.
Automated path
The step runs automatically when it is within agreed boundaries, confidence is high, and no approval threshold is triggered.
Review path
The step pauses and routes to a person when confidence is low, the case is novel, or policy requires review.
Escalation path
The step escalates when something is wrong - a system is down, data does not match, or the case falls outside the workflow’s scope.
Approval path
The step requires a human sign-off when the action is irreversible, above a threshold, or affects a customer’s account.
How every step is recorded
Every decision is traceable. When your team asks what happened and why, the record is in your systems - readable without us.
- What inputs were considered - context, rules, and state at the time
- What path was taken - automated, review, escalation, or approval
- Who approved - if a human was involved, their identity and timestamp
- What action was taken - the specific system change or communication
- Why - the reasoning that led to the decision, in plain language