Platform

How OrqForge orchestrates enterprise work

Unstructured input becomes a governed outcome. Role agents produce deliverables. Orchestrators delegate down the org chart. Specialists work in parallel, stay in sync, and report back until a human approves publish.

Multi-channel AI triggers converging on a central OrqForge orchestration hub

How it works

Work moves like a real operations team

One operating model for any process your organisation runs.

Work arrives. An orchestrator assigns specialists. They work in parallel, stay in sync, and report back. You add stages only if that process needs them. Humans approve before anything publishes.

See how work flows →

How it works

From messy intake to approved outcome

Work arrives from Teams, email, or a webhook. An orchestrator picks it up, assigns specialists, and they work in parallel. Results fold back to the parent. When the deliverables are ready, a human approves before anything publishes.

  1. 1

    Agentic AI

    Role agents produce deliverables

    Each agent is trained for a job: analyse input, draft a report, open a ticket, write code. They use scoped tools, reason through the work, and hand off a result worth reviewing.

    Learn more →
  2. 2

    Chain of command

    Orchestrators assign the work

    When intake arrives, an orchestrator triages it and delegates to direct reports. Specialists run in parallel. Stream owners and human reviewers sit where accountability matters.

    Learn more →
  3. 3

    Synced missions

    The team stays in lockstep

    The mission tree shows who is working, who is waiting on whom, and what just folded back. Specialists report to the orchestrator. Humans sit at the gates that matter.

    Learn more →

On a typical run, the orchestrator assigns work while specialists produce deliverables at the same time. Status, handoffs, and fold-back stay visible. Stages are optional if a process needs extra structure.

Chain of command

Who owns the work

When intake arrives, someone has to decide what happens next and who does it. Orchestrators sit at the top of the mission tree. They delegate to specialists with scoped tools. Human reviewers wait at the gates that matter.

  • Managers and specialists

    Orchestrators coordinate. Direct reports execute. Work flows down the hierarchy without skipping a layer.

  • Parallel assignments

    One orchestrator can delegate to several specialists at once. Each picks up its own work immediately.

  • Human accountability gates

    Stream owners assign reviewers. Material outcomes route through accountable humans before publish.

How specialists work in parallel →
OrqForge agent hierarchy with orchestrator coordinating specialist agents in a mission tree

Delegation in action

Specialists work in parallel and report back

When an orchestrator delegates, specialists start at the same time. The mission tree shows who is working, who is waiting on reports, and how results fold back without skipping layers.

  • One delegation event can start multiple specialists at once
  • Each specialist reports back to the parent with a self-contained result
  • Full reasoning visibility per agent so supervisors intervene early
  • Delegation lineage retained for audit and replay
Mission tree showing delegated agent branches with live status
app.orqforge.com/runs/run-2026-0847

Agent network

  • Process Orchestrator Monitoring
  • Evaluation Agent Working
  • Adjuster Agent Working
  • Intake Agent Complete
  • Fraud Detection Disabled

Reasoning, Evaluation Agent

Analysing attached files for visible damage patterns…

Estimating repair bracket based on impact zone and policy limits.

Missing: supporting estimate, policy excess confirmation.

→ Passing partial assessment to Adjuster Agent.

Optional governed stages

Stages when a process needs extra structure

Stages are not required. Many teams run agents as a synced team: assign, work in parallel, fold back, review. When a process needs triage, planning, or finer audit grain, you can enable up to eleven governed stages.

Enable only what that workspace needs. Disabled stages never appear on the run.

  1. 1

    Ingest

    Optional. Capture the inputs this role needs, from channels or from upstream agents.

  2. 2

    Triage & Plan

    Optional. Classify and gather context before execution when the work is messy.

  3. 3

    Execute

    Specialists produce deliverables in parallel and fold results back to the orchestrator.

  4. 4

    Review

    Human or AI gates before publish, configured per role and workflow type.

  5. 5

    Publish & Learn

    Optional extra structure. Deliver outcomes and improve from completed work.

The stages you can enable

Use them when a process needs extra structure. Many teams run agents without this.

1

Lobby

Gather conversation context in Teams or chat before this agent takes ownership.

2

Ingest

Accept the inputs this role needs: email, attachments, webhooks, or handoffs from upstream agents.

3

Triage

Classify work against the workspace taxonomy and route to the right confidence lane.

4

Planning

Ask structured questions when this agent needs more context before it can execute.

5

Hierarchy

Break work into owned items and delegate to direct reports. No layer skipping.

6

Execute

Produce this role deliverable: document, report, code, ticket, or system action.

7

Post-Execute

Shape raw output into a coherent deliverable ready for review or downstream handoff.

8

Review

Pause for human or AI approval before anything material leaves this agent.

9

Publish

Deliver results to SharePoint, Jira, email, or the next agent in the chain.

10

Learn

Capture corrections and patterns so this role improves. Governed, never silent.

11

Complete

Close this agent run with retained evidence and the full handoff lineage.

Workspaces and organisation structure

Workspaces mirror your internal organisation, customer boundaries, product lines, business units, or process domains. Within each workspace, role agents are bound to specific accountability: which tools they use, which review path applies, and which workflow types they handle.

Input sources

  • Teams chat: agents installed as Teams bots; users converse and hand off work
  • Email inboxes: shared or user mailboxes with rule-based routing
  • Meeting recordings: transcripts processed automatically after meetings end
  • Webhooks: Azure DevOps, Jira, and custom integrations
  • Scheduled jobs: heartbeats, reports, and recurring checks
  • Manual ingest: operators submit content through the platform

Product

Agent interfaces

Workspaces, hierarchy, triggers, and live mission status. See every interface on the product tour.

Agentic flow builder
app.orqforge.com/workspaces/demo-insurance
AI Trainer 19 messages
I've reviewed your process docs. I'm proposing 6 roles across intake, evaluation, adjustment, and publishing. Enable orchestrator, intake, and evaluation for the first rollout?
Yes, enable those three plus adjuster. Keep fraud detection disabled for now.
Done. Taxonomy updated: intake, evaluation, adjustment_report. Review gates set to draft mode.
Attach documents or describe changes…
Send

Configure workspaces, roles, taxonomy, and review paths in a guided session. Days, not years.

Agent hierarchy
app.orqforge.com/workspaces/demo-insurance/org

Agent hierarchy

Example workspace · 6 roles · 3 tiers

Live
1

Process Orchestrator

Stream owner · Ops Lead (human)

Draft execution

  • Intake Agent

    Teams · Email · Webhook

  • Classification Agent

    Taxonomy routing

2

Delivery Orchestrator

Parallel specialist coordination

  • Damage Evaluation

    Scoped tools · Evidence pack

  • Adjuster Agent

    Structured output · Review path

  • FNOL Agent

    First notice · Complete

3

Review Coordinator

Human accountability gate

  • Stream reviewers

    2 assigned · Draft mode

Chain of command: orchestrators, specialists, scoped tools, and human accountability gates.

Multi-channel triggers
app.orqforge.com/workspaces/demo-insurance/triggers

Multi-channel intake

Meet teams where they work, same orchestrator for every trigger

T

Microsoft Teams

Active

Bot installed · 3 workspaces

@

Email listener

Active

shared-inbox@example.com · Rule-based routing

W

Webhook

Active

Azure DevOps · Jira · Custom

⏱

Scheduled jobs

Configured

Daily heartbeat · Weekly reports

Enterprise pattern

Imperfect input from any channel → classified → orchestrated → reviewed → published to your systems.

Teams, email, webhooks, and schedules. Every intake path reaches the orchestrator first.

Workflow runs
app.orqforge.com/workflows

High-volume intake run

intake_flow · Example workspace · Active · 12m 34s

3 agents in parallel

Process Orchestrator

Delegated assessment + adjuster

Awaiting reports

Evaluation Agent

Drafting structured assessment

Working

Adjuster Agent

Checking policy limits in parallel

Working

Intake Agent

Folded context back to orchestrator

Complete

Live mission status: who is working, who is waiting on reports, and what just folded back.

See the platform in action

Book a session tailored to your processes, roles, and review requirements.