Route a conversation to another queue
Moves the conversation to a different queue — the team that should carry it from here.
When to use it. The operator picks a queue in the transfer dialog: wrong team, needs a specialist, escalating out of hours. The customer sees nothing; only who is responsible changes.
What it does not do. It does not change the number the customer writes to, and it does not change the AI agent — that follows the number, not the queue. It also releases any individual assignee (assigned_to), because the conversation now belongs to a team rather than a person.
It sticks. The queue a conversation arrived on is decided by its number, but a transfer overrides that for the rest of the conversation: the next inbound message will not pull it back. Only moving the number itself to another queue in the designer, or the conversation closing, resets that.
The note is optional and, when given, is recorded in the thread as a system line so the receiving team can see why it arrived.
Who can call it. A workspace API token, or a per-user JWT holding loop.conversations.assign. JWTs are limited to conversations of their active queues (404 otherwise), but may transfer INTO any queue — handing work to another team is the point.
Authorizations
Use a Bearer token to access these API endpoints. Example: "Bearer {your-token}"