> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/bot-commands/transfer.md). # /transfer ## Transfer Command ### Overview The `/transfer` command hands a claimed ticket from one staff member to another. The new person becomes the claimer, and if your claiming mode changes channel access, the access moves with the claim. Run it inside the ticket. ### Usage ``` /transfer ``` * **user** *(required)*: The staff member to transfer the ticket to. ### Description * **The claim moves, not the ticket.** `/transfer` changes who owns this ticket. It does not move the ticket to another panel, option, or category. * **A notice is posted.** The ticket gets a "Ticket Transferred" message naming who it went from and to. * **Access follows the claim.** Under `Enabled - Private on Claim` or `Enabled - Read Only for Others`, the previous claimer's access is replaced by the new claimer's. ### Requirements All of these must hold, or the command tells you which one failed: * **The ticket must already be claimed.** Transfer moves an existing claim. If nobody has claimed it, the target should use `/claim` instead. * **Ticket claiming must not be disabled** in the server's Ticket Claiming Mode setting. * **The target must be the server owner or hold a support role** — server-wide, or one set on a panel option. Only roles count here: a member whose access comes solely from Discord's Manage Channels or Manage Server permission **cannot** be a transfer target, even though they can run `/transfer` themselves. Put your staff on a support role and this never comes up. * **The target cannot already hold the claim.** ### When to Use It * Shift handover: passing open tickets to whoever is coming on duty. * Escalation to a specialist who handles billing, appeals, or bug reports. * A staff member is going offline with a ticket still claimed. ### Permissions * You can use this command if you have Manage Channels or Manage Server, or you are the server owner, or you hold an authorized support role. Administrator also works because it includes those permissions. * The bot needs `Manage Channels` to update the ticket's access. ### Example ``` /transfer user: @BillingLead ``` Moves the claim to @BillingLead and posts the transfer notice in the ticket. ### Related {% content-ref url="/pages/MqZDT5VpVYFrSkwydTDr" %} [/claim](/docs/bot-commands/claim.md) {% endcontent-ref %} {% content-ref url="/pages/Blu3D3m8EWaNtKWG4Qa9" %} [Claiming a ticket](/docs/tickets/claiming-a-ticket.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ticketking.xyz/docs/bot-commands/transfer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.