Your AI employees can now work as a team: introducing Agent Orchestration

Nitish kumar — Wed, 02 Sep 2026 18:29:32 +0000

Until now, a DeskFerry agent was a very good solo employee. You described a job in plain English, it connected to your tools, and it ran that job on a schedule or trigger. That worked well for one job at a time.

But real work isn't one job. Qualifying a lead is research, then scoring, then CRM hygiene, then outreach, then follow-up. Each of those is a different skill, with different tools and different failure modes. Cramming all of it into a single agent meant one giant prompt, one giant blast radius, and a lot of "why did it do that?"

As of September 1, that changes. Agent Orchestration is live in DeskFerry.

What it does

Orchestration lets one agent coordinate others. You give a brief to a lead agent, and it breaks the work down and delegates each piece to a specialist agent you've already built (or lets DeskFerry build the missing ones for you).

Concretely, agents can now:

Delegate. A lead agent hands a sub-task to another agent and waits for the result, the same way a manager assigns work.
Share context. The research agent's findings are available to the outreach agent without you copying anything between them. Memory is scoped to the workflow, not trapped in one agent.
Hand off mid-flight. A support triage agent can escalate a ticket to a billing agent with the full thread attached, then step back in when billing is done.
Run in parallel. Independent steps (enrich five leads, check three inboxes) fan out and come back together.
Pause for humans where it matters. Approvals work exactly as before, but now you can put the checkpoint at the team level — approve the final email, not every intermediate step.
What it looks like

You still describe the outcome, not the plumbing:

Every weekday at 8am, pull new HubSpot leads, research each company, score them against our ICP, draft a first-touch email for anything above 70, and post the drafts to #sales for approval before sending.

DeskFerry turns that into a small team: a coordinator, a researcher, a scorer, and a writer. Each one is a normal DeskFerry agent — you can open it, edit its instructions, swap its model, or reuse it in a different workflow. The scorer you built for inbound leads can be the same scorer your partnerships agent calls next month.

Why we built it this way

We looked at two approaches. One was a visual canvas where you draw boxes and arrows between agents. The other was letting you describe the team the way you'd describe it to a new hire. We chose the second, because the whole point of DeskFerry is that you shouldn't need to become a workflow architect to get work done.

Under the hood, the coordinator is doing the planning, but everything it decides is visible. Every delegation, every handoff, and every intermediate result shows up in the run log, so when something goes sideways you can see exactly which agent made which call.

What it means in practice
Smaller, more reliable agents. A specialist with one job and three tools is much harder to confuse than a generalist with fifteen.
Reuse. Build a skill once, call it from anywhere.
Less babysitting. The coordinator handles retries and routing so you don't get paged for a single flaky step.
Try it

Orchestration is available now. Open any existing agent, and you'll see a new option to let it delegate to other agents, or start fresh with a multi-step brief and let DeskFerry assemble the team.

If you're on a trial, this is included. If you're not, the trial is free and doesn't auto-convert.

We'd love to hear what you build. Drop your workflows in the comments, or tell us where orchestration falls short — that's the feedback that shapes what ships next.

DEV Community: Deskferry

Your AI employees can now work as a team: introducing Agent Orchestration