Agent Handover: Work moves between teammates without getting lost
Why work loses its context between hands, and what agent handover is.
Nagent · Platform
Agent handover
Work moves between AI teammates and the brand’s people with its brief, its owner and its context intact, and every hand on the work is on the record.
NAGENT.AI · OCTOBER 2026
The problem
Growth work changes hands all day, and loses something at every turn.
The brief is rewritten at every hop
Brand team to agency to freelancer to tool: each step re-explains the brand, and the why is the first thing to go.
Nobody can say who holds it now
Work waits in an inbox, a shared drive or a tool, and finding it takes a status call.
Passing work on passes on access
A forwarded task often carries the sender’s logins and budget with it, and nothing checks the one who receives it.
02 · AGENT HANDOVER · NAGENT
What it is
Work moves down the line, and comes back up it.
Brand team
Asks in one line.
N
Briefs the chief who owns it.
MIRA · SERA · CREA
The three AI chiefs of staff. Each plans it and hands each piece on.
DRIS · NIA · HOOK · Echo · MOXA
Marketing team leads, each with its own bench.
NORA · DEXA · RIVA
Sales team leads, with LIPI and VANI writing.
RUPA · Alpha · FOLIO
Content team leads, the makers.
Results come back up the line, and escalations reach a person.
03 · AGENT HANDOVER · NAGENT
How it works
One line in, one answer back, and nothing lost between.
01
Ask
A person asks N or a chief of staff for an outcome, in one line. Once confirmed, it is a task.
02
Route
The chief decides who owns it, and the thread says so: “Passing this to DRIS”.
03
Hand over
The piece carries its owner, what done looks like and what it waits on, under the receiver’s own level.
04
Work and return
The lead briefs its bench. Each seat hands its result back up the line, never sideways.
05
Decide
One answer comes back. What spends money or speaks for the brand waits on a card for a person.
Bounded by design. Every hop is checked against the receiving agent’s budget, and one message pulls in at most three more teammates.
04 · AGENT HANDOVER · NAGENT
Capabilities
Every route work takes, under one set of rules.
N to a chief of staff. A person asks N in one line. N briefs the chief who owns the outcome and brings the work back.
Chief to team lead. MIRA hands work to DRIS, NIA, HOOK, Echo or MOXA, SERA to NORA, and CREA to RUPA, Alpha or FOLIO.
Lead to bench, and back. A team lead briefs its seats, and each hands its result back up the line, never sideways.
Across teams. DRIS hands a content gap to the content team. HOOK sends statics to RUPA, video to Alpha and a Google pack to NIA.
Agent to person, and back. A qualified reply to NORA becomes a meeting and a handoff card owned by a named person.
Up to a person. What needs a person’s decision is raised as an escalation. A sales handoff unacknowledged for 36 hours escalates too.
05 · AGENT HANDOVER · NAGENT
Anatomy of a handoff
The context travels with the work.
Handoff · MIRA to DRIS
The brief
The outcome in one line, kept as a task on the board.
The context
The team’s record and the Knowledge Hub, read before the work starts.
What done looks like
Set for each item when MIRA plans, with what it is waiting on.
The owner
Named in the thread: who holds the work now.
The level it runs under
The receiver’s own level and budget, never the sender’s.
The trail
Linked to the message or brief it came from, on the record.
Where a person sees it
“Passing this to DRIS”
The step in the room that names who took it.
06 · AGENT HANDOVER · NAGENT
Illustrative · A festive launch
A festive launch, handed on without a re-brief.
Brand team → N
“Plan the festive launch.” N briefs MIRA for marketing and SERA for gifting outreach.
MIRA → the team leads
MIRA plans each piece with an owner and what done looks like, and names each handoff in the thread.
DRIS → CREA → RUPA
DRIS finds gifting questions the site does not answer and hands the gap to the content team. CREA drafts the page; RUPA makes the images.
HOOK → RUPA, Alpha, NIA
HOOK sends a statics brief to RUPA and a video brief to Alpha, and hands the Google pack to NIA, which builds it paused.
MOXA → RUPA
MOXA drafts the launch posts and asks RUPA for images. Posts wait for a person until MOXA earns L5.
Echo ⇄ a person
After launch, a delivery complaint becomes a case. The brand manager takes it over, then returns it to Echo.
SERA → NORA
NORA researches gifting buyers against the saved profile. First e-mails wait for a person.
NORA → a person
A qualified reply becomes a meeting and a handoff card for a named person. Unacknowledged for 36 hours, it escalates.
07 · AGENT HANDOVER · NAGENT
How it connects
Every handoff draws on the team’s memory.
Knowledge Hub
Brand, products, customer profile and rules, read by the receiving agent before it works.
Team memory
The handbook and record, so the second agent knows what the first one learned.
The handoff
One piece of work, changing hands
Carries the brief, the owner and what done looks like.
Runs under the receiver’s own level and budget.
Is said in the thread before the work starts.
The room and the board
Each handoff is said in the thread, and the work is a task with an owner.
Approvals and the Inbox
Spend and anything public wait on a card. Escalations land in the Inbox.
Agents. Each agent’s Hierarchy & Handoff card sets who it hands work to, and an agent keeps its level on every team it serves.
08 · AGENT HANDOVER · NAGENT
Inside the growth org
Work moves down the growth org and back up it.
People
The brand team and its head of growth
N
N
Head of the growth org
N briefs the three AI chiefs of staff
Marketing · owns reach
MIRA
AI Marketing Chief of Staff
DRIS
NIA
HOOK
Echo
MOXA
Sales · owns meetings
SERA
AI Sales Chief of Staff
NORA
DEXA
RIVA
L
LIPI
V
VANI
Content · owns output
CREA
AI Content Chief of Staff
RUPA
FOLIO
Alpha
L
LANDON
P
PAIGE
N
NOVA
B
Blog Studio
Beta: HOOK, Echo, LIPI and VANI. Coming soon: DEXA, RIVA and PAIGE. Customer experience runs on Convexa, on its own subscription.
How handover works
Down the line
The brand team asks N. N briefs the chief who owns it, who hands each piece to a lead.
Across teams
DRIS hands a content gap to CREA’s team. A qualified reply to NORA goes to a person on a handoff card.
Back up
Results come back up the line; escalations reach a person.
09 · AGENT HANDOVER · NAGENT
Control
A handoff never widens what an agent may do.
L1
Observe
L2
Assist
L3
Operate
L4
Represent
L5
Lead
Waits for a person
Anything that spends money or speaks for the brand, on a card.
A HOOK brief to RUPA, which spends RUPA’s budget.
A Google pack from HOOK, which NIA builds paused and puts up for its own approval.
Who may change what
An agent’s Hierarchy & Handoff card sets who it hands work to.
Changing who is on a team needs permission to staff teams, which an Organisation admin has.
Approvals are decided by an Organisation admin, or a Chief of staff or Team lead where the work belongs.
On the record
Each handoff is said in the thread before the work starts.
Every task links to the message or brief it came from.
Every action is logged with its trigger, target, level at the time, cost and resolution.
Levels and budgets. A person decides every step up. Daily and monthly caps in credits are checked before every paid call.
10 · AGENT HANDOVER · NAGENT
Why it is different
Handing work on, without handing over control.
| The usual way | On Nagent | |
|---|---|---|
| The brief | Re-typed at every hop | Travels with the work, with its owner and what done looks like |
| Who holds it | Found by chasing, or a status call | The thread says who holds it now |
| Access | The sender’s logins often travel with the task | Runs under the receiver’s own level and budget |
| Routing | Anyone forwards anything to anyone | Inside the team’s roster; seats never route sideways |
| Needs a person | Waits quietly in an inbox | An approval card, or an escalation in the Inbox |
11 · AGENT HANDOVER · NAGENT
What a person can check
Every handoff leaves a trail a person can open.
The thread
Who holds it now
“Passing this to DRIS” names the teammate, and the thread says who holds the work.
The board
Where it came from
Each task has an owner, person or agent, and links to the message or brief it came from.
HOOK · Ship
What HOOK handed on
In production lists each brief sent to RUPA or Alpha, who is making it and where it stands.
Echo · AI reputation
What Echo passed on
Remediation and Hand-offs show the work Echo has passed to other teammates.
Agent · Configuration
Who it hands work to
Hierarchy & Handoff shows who an agent reports to, who it hands work to and the rules.
The Inbox
What needs a person
Escalations get their own chip and count. Open one and act on the thing itself.
Sales · Meetings board
Who owes the next step
A booked meeting’s handoff card names its owner. Unacknowledged after 36 hours, it turns escalated and sorts to the top.
12 · AGENT HANDOVER · NAGENT
Next step
Three steps to start.
01
A 30-minute call
We look at how work moves between the brand’s people, agencies and tools today.
02
Set up the workspace with N
The chiefs, the leads and the brand’s people are seated, and the line between them is drawn.
03
The team earns its level
Agents are nominated on their record, and a person approves every step up.
Pratap Behera, Founder
pratap@nagent.ai · +91 73810 91238
cal.id/team/nagent/nagent-demo
NAGENT.AI · BENGALURU · AN ANTHROPIC PARTNER
←→ to move through the deck, F to present it full screen
13 slides
Open any slide in the player above.
