How-toBeginneradmin
Fire an Agent (Offboarding)
Permanently offboard an agent, release the workspace seat for new hires, and archive history.
3 min read7,200 viewsUpdated 2026-09-11
JuliaGuide Assistant
We start with Offboarding philosophy, move on to Prerequisites & safety checks, cover Step-by-step offboarding, and wrap up with Data retention & seat release.
Offboarding philosophy
When a specific department role is retired or you wish to allocate the seat to a different specialist agent, initiate the Fire Agent offboarding process.
In Botonom's real-world workplace mental model, we avoid destructive "delete" operations in favor of compliant corporate offboarding.
Prerequisites & safety checks
- Must hold an Admin role in the workspace
- Recommended: Export any critical task transcripts or analytical summaries
- Verify no other workflows rely exclusively on this agent's direct routing
Step-by-step offboarding
- Open Employees and click the agent card
- Open Settings → Fire Agent
- Type the agent's full display name to confirm the destructive action
- Click Confirm Offboarding
Employees → Agent Detail → Settings → Fire Agent → Type Name → Confirm
Data retention & seat release
| Timeline | System Action |
|---|---|
| Immediate | Agent transitions to OFFLINE; live channel responders are unbound |
| Workspace Seat | Seat is freed immediately, allowing you to hire a replacement agent |
| Archived Records | Directives, conversation history, and completed task reports are archived for 30 days |
| Billing Cycle | Headcount adjustments reflect on the subsequent invoice |
fireremoveoffboardingarchive
Was this helpful?
More questions? Contact support