ORCHESTRATION — Q&A
Q: Is the orchestration engine a ninth agent? No. Fincelo has 8 agents. The orchestration engine is the coordination layer that sits alongside them. It does not act on customers, is not governed by Auto / Approval / Disabled states, and carries no credit weight.
Q: How do agents coordinate without conflicting? The orchestration engine manages:
- Event routing: which agent reacts to which event
- Priority: higher priority agents go first on the same event
- Conflict prevention: cooldown locks per customer per channel (default 24 hours), plus blackout schedules
- Sequencing: some actions must happen in order (e.g. generate quote before sending)
- Rollback: if an agent action fails, the orchestration engine triggers rollback if marked rollback-capable
Q: What are orchestration rules? Configurable trigger chains. Example: “When Renewal Agent marks a contract as At Risk → Customer Intelligence Agent runs a full health assessment within 2 hours → CFO Co-pilot includes it in tomorrow’s briefing.” Rules are stored in the
orchestration_rules table.
Finance teams can create custom chains in Settings → Agents → Orchestration.
Q: What is multi-agent debate? Level 5 enhancement (roadmap, 2027). Before high-stakes autonomous decisions (e.g. write-off above ₹10L, legal referral), two agents independently assess the situation and present opposing arguments. A third agent moderates. The CFO sees the debate summary before approving. Designed to prevent AI echo-chamber.