Platform

How OrqForge orchestrates enterprise work

Unstructured input becomes a governed outcome. Role agents produce deliverables. Orchestrators delegate down the org chart. Each agent moves through the stages you enabled for that role, in parallel, 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.

Intake arrives from Teams, email, or a webhook. An orchestrator triages and assigns specialists. Each agent runs the stages configured for its role while others work in parallel. 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 each agent moves through the stages you enabled for that role. 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

    Agentic pipelines

    Each agent runs governed stages

    Every role follows up to eleven stages you configure: ingest, triage, execute, review, learn, and more. The orchestrator can be planning while one specialist is in execute and another waits in review.

    Learn more →

On a typical run, the orchestrator triages and delegates while specialists ingest inputs, produce deliverables, and route outcomes to review. All of it visible, all of it retained for audit.

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 each agent runs its stages →
OrqForge agent hierarchy with orchestrator coordinating specialist agents in a mission tree

Agentic pipelines

Eleven stages on every agent

The process orchestrator might run triage, hierarchy, and delegate while a specialist runs ingest, execute, and review at the same time. You enable only the stages each role needs.

Stage progress, elapsed time, and bottlenecks show per agent. Supervisors see what is running, not a black box.

  1. 1

    Ingest

    Each agent accepts the inputs its role needs, from channels or from upstream agents.

  2. 2

    Triage & Plan

    Classify and gather context before execution. Per agent, not once for the whole run.

  3. 3

    Execute

    Specialists produce deliverables in parallel, each on its own pipeline track.

  4. 4

    Review

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

  5. 5

    Publish & Learn

    Deliver outcomes and improve from every completed agent run.

The eleven stages, configurable per agent

Enable only what each role needs. Every stage is visible, inspectable, and retained for audit.

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 full stage history and retained evidence.

Delegation in action

Delegation spins up parallel work

When an orchestrator delegates, each specialist starts its own pipeline. The mission tree shows who is working, which stage each agent is in, and how work flows down without skipping layers.

  • One delegation event can start multiple agent pipelines at once
  • Each role runs only the stages you enabled for that workflow type
  • Full reasoning visibility per agent so supervisors intervene early
  • Stage history and 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.

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 pipeline visibility. 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 governed pipeline 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

Execute
Lobby
Ingest
Triage
Plan
Hierarchy
Execute
Post-Exec
Review
Publish
Learn
Done

Assessment report

Execute · 8m 12s · 24.1k tokens

Process orchestrator

Execute · Delegating · 12m 34s

Each role agent runs its own pipeline with live stages, elapsed time, and status.

See the platform in action

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