I think the transfer would have to be done to a DID which then selects an Inbound Call flow which assigns the appropriate skill and transfers to the queue.

Since the DID is configured in genesys Cloud, the call would stay internal without looping out to the carrier.

There are ways to use the Number Plan to take a shorter number (2,3,4 or whatever digits) and convert to the DID.

The Inbound Call Flow could be set up with prompts for the agent to choose the skill, in which case the agent would do a Consult transfer, make the selections, then complete that consult transfer once the call is routing/routed to the queue (which could mean the agent gets connected to another agent in the queue before completing the transfer, which should be fine).

I think the transfer would have to be done to a DID which then selects an Inbound Call flow which assigns the appropriate skill and transfers to the queue.

Since the DID is configured in genesys Cloud, the call would stay internal without looping out to the carrier.

There are ways to use the Number Plan to take a shorter number (2,3,4 or whatever digits) and convert to the DID.

The Inbound Call Flow could be set up with prompts for the agent to choose the skill, in which case the agent would do a Consult transfer, make the selections, then complete that consult transfer once the call is routing/routed to the queue (which could mean the agent gets connected to another agent in the queue before completing the transfer, which should be fine).

I think the transfer would have to be done to a DID which then selects an Inbound Call flow which assigns the appropriate skill and transfers to the queue.

Since the DID is configured in genesys Cloud, the call would stay internal without looping out to the carrier.

There are ways to use the Number Plan to take a shorter number (2,3,4 or whatever digits) and convert to the DID.

The Inbound Call Flow could be set up with prompts for the agent to choose the skill, in which case the agent would do a Consult transfer, make the selections, then complete that consult transfer once the call is routing/routed to the queue (which could mean the agent gets connected to another agent in the queue before completing the transfer, which should be fine).

I think the transfer would have to be done to a DID which then selects an Inbound Call flow which assigns the appropriate skill and transfers to the queue.

Since the DID is configured in genesys Cloud, the call would stay internal without looping out to the carrier.

There are ways to use the Number Plan to take a shorter number (2,3,4 or whatever digits) and convert to the DID.

The Inbound Call Flow could be set up with prompts for the agent to choose the skill, in which case the agent would do a Consult transfer, make the selections, then complete that consult transfer once the call is routing/routed to the queue (which could mean the agent gets connected to another agent in the queue before completing the transfer, which should be fine).

I think the transfer would have to be done to a DID which then selects an Inbound Call flow which assigns the appropriate skill and transfers to the queue.

Since the DID is configured in genesys Cloud, the call would stay internal without looping out to the carrier.

There are ways to use the Number Plan to take a shorter number (2,3,4 or whatever digits) and convert to the DID.

The Inbound Call Flow could be set up with prompts for the agent to choose the skill, in which case the agent would do a Consult transfer, make the selections, then complete that consult transfer once the call is routing/routed to the queue (which could mean the agent gets connected to another agent in the queue before completing the transfer, which should be fine).

I think the transfer would have to be done to a DID which then selects an Inbound Call flow which assigns the appropriate skill and transfers to the queue.

Since the DID is configured in genesys Cloud, the call would stay internal without looping out to the carrier.

There are ways to use the Number Plan to take a shorter number (2,3,4 or whatever digits) and convert to the DID.

The Inbound Call Flow could be set up with prompts for the agent to choose the skill, in which case the agent would do a Consult transfer, make the selections, then complete that consult transfer once the call is routing/routed to the queue (which could mean the agent gets connected to another agent in the queue before completing the transfer, which should be fine).

• The first option would be to offer 'transfer to flow' options which would enable an agent to pick a flow to transfer to at which point the flow logic could apply new priority, new skills, call a data action, what-have-you...the complication here is that we likely don't want to expose all scripts to agents and we'd have to work with architect to figure out what to expose, etc. 
• Option 2 is to add some settings to a queue to A) have 'default skill assignment' so that any interaction that hits the queue would pick up these skills.  While this wouldn't strip the original skills, it could at least add them upon the interaction entering the queue. 
• The last option would be to add 'transfer skills' to a queue so that every transfer FROM the queue would add or replace the existing skills for an interaction.

I think the transfer would have to be done to a DID which then selects an Inbound Call flow which assigns the appropriate skill and transfers to the queue.

Since the DID is configured in genesys Cloud, the call would stay internal without looping out to the carrier.

There are ways to use the Number Plan to take a shorter number (2,3,4 or whatever digits) and convert to the DID.

The Inbound Call Flow could be set up with prompts for the agent to choose the skill, in which case the agent would do a Consult transfer, make the selections, then complete that consult transfer once the call is routing/routed to the queue (which could mean the agent gets connected to another agent in the queue before completing the transfer, which should be fine).

• The first option would be to offer 'transfer to flow' options which would enable an agent to pick a flow to transfer to at which point the flow logic could apply new priority, new skills, call a data action, what-have-you...the complication here is that we likely don't want to expose all scripts to agents and we'd have to work with architect to figure out what to expose, etc. 
• Option 2 is to add some settings to a queue to A) have 'default skill assignment' so that any interaction that hits the queue would pick up these skills.  While this wouldn't strip the original skills, it could at least add them upon the interaction entering the queue. 
• The last option would be to add 'transfer skills' to a queue so that every transfer FROM the queue would add or replace the existing skills for an interaction.

I think the transfer would have to be done to a DID which then selects an Inbound Call flow which assigns the appropriate skill and transfers to the queue.

Since the DID is configured in genesys Cloud, the call would stay internal without looping out to the carrier.

There are ways to use the Number Plan to take a shorter number (2,3,4 or whatever digits) and convert to the DID.

The Inbound Call Flow could be set up with prompts for the agent to choose the skill, in which case the agent would do a Consult transfer, make the selections, then complete that consult transfer once the call is routing/routed to the queue (which could mean the agent gets connected to another agent in the queue before completing the transfer, which should be fine).

I think the transfer would have to be done to a DID which then selects an Inbound Call flow which assigns the appropriate skill and transfers to the queue.

Since the DID is configured in genesys Cloud, the call would stay internal without looping out to the carrier.

There are ways to use the Number Plan to take a shorter number (2,3,4 or whatever digits) and convert to the DID.

The Inbound Call Flow could be set up with prompts for the agent to choose the skill, in which case the agent would do a Consult transfer, make the selections, then complete that consult transfer once the call is routing/routed to the queue (which could mean the agent gets connected to another agent in the queue before completing the transfer, which should be fine).