How to dissociate agents from department in Zoho Desk

Dissociating agents from a department in Zoho Desk is accomplished through a single authenticated API call that removes one or more agents from the specified department without deleting the agents themselves.

Why this matters

When your support team restructures — merging departments, reassigning specialisms, or offboarding staff — you need a clean way to remove agents from a department so they stop receiving tickets routed there. Leaving stale agent-department associations can cause mis-routed tickets and inflated queue counts. This operation is reversible: agents can be re-associated at any time using the corresponding POST endpoint. ^[6]

---

Step-by-step

Step 1. Identify the department_id for the department you want to modify. You can retrieve this from your Zoho Desk admin panel or by querying the departments list endpoint. Keep this value handy — it forms part of the request path. ^[1]

Step 2. Identify the agent IDs you wish to remove. These are the unique identifiers for each agent record in Zoho Desk. You will pass them as part of the request payload (the p parameter) when making the call. ^[1]

Step 3. Construct and send a DELETE request to the following endpoint, substituting your real department ID:

DELETE /api/v1/departments/{department_id}/agents

Include your OAuth bearer token in the Authorization header and pass the agent identifiers in the request parameters. ^[1]

Step 4. If you are using the Python SDK wrapper, the call looks like this:

result = client.delete_dissociate_agents_from_department(
    department_id="<your_department_id>",
    p={"agentIds": ["<agent_id_1>", "<agent_id_2>"]}
)

The method sends the DELETE request to /api/v1/departments/{department_id}/agents and returns the API response object. ^[1]

Step 5. Check the HTTP response status. A successful dissociation will return a 2xx status code. If you receive a 4xx error, verify that the department_id is correct and that your OAuth token has the necessary Desk scope permissions. ^[1]

Step 6. To confirm the change, you can re-associate agents to a department at any time using the POST /api/v1/departments/{department_id}/agents endpoint — the mirror operation to what we just performed. ^[6]

---

Common pitfalls

• Wrong department ID format. The department_id must be the numeric or string identifier returned by Zoho Desk's API, not the human-readable department name. Passing a display name will result in a 404 or 400 error. ^[1]
• Missing or incorrect agent IDs in the payload. If the p parameter is empty or malformed, the API may return a success response but perform no actual dissociation. Always confirm agent IDs before sending. ^[1]
• Scope mismatch. Your OAuth token must include the appropriate Desk API scope that permits write operations on department membership. A read-only scope will cause the request to be rejected. ^[1]
• Confusing dissociation with deletion. This endpoint removes the *association* between an agent and a department — it does not delete the agent's account. The agent remains active in Zoho Desk and can be re-added to any department. ^{[1] [6]}

---

What to check

• Confirm the agent no longer appears in the department's agent list by navigating to Setup → Departments in Zoho Desk and reviewing the member roster.
• Verify ticket routing rules that reference the affected department — any automation or round-robin rules that targeted the removed agent may need updating.
• Test with a single agent ID first before bulk-dissociating multiple agents, to ensure your payload structure is correct and the API responds as expected. ^[1]

---

*Beam Help is an independent expert support resource for Zoho products and is not official Zoho support. For licensing or account-level issues, please contact Zoho directly.*