Have agents associate different devices with RMCM user?

[jconyers]

Would it be possible for agents to associate which device is associated with the RMCM user in CUCM? We have agents that sometimes work from their desk phones, other times from Jabber over VPN, other times using CTI Remote Destination devices. Since the RMCM user can only be associated with a single device and single line we wanted to make it easier for agents to be able to switch between the devices they are working on which sometimes changes multiple times a week. Right now, the only way I know of to associate a device is to have an administrator (me or helpdesk) associate their other device with the RMCM user. But we don't want to constantly changing this when the agents decide to move between locations/scenarios. So, is there a way that the agent can do this somehow when they change their phone control in Jabber between deskphone, use my computer, or use a new number (CTIRD)? We want to make this as easy for the agents as possible, as well as little maintenance for the administrators. Ideally, something that happens in the backend when the phone control is changed in Jabber, so that the agent doesn't even know it is happening. Or possibly doing this in the Self Care portal could be an option. Any thoughts or suggestions would be appreciated.

[iptuser55]

We have the same issue but for now we give the user two end user accounts in cucm  so they log on differently depending on the device they have to use

We are also looking for an easier method 

[Sean Lynch]

I agree with iptuser55; as unconventional as this sounds, at this time there is no way around the single-line limitation for a configured resource.  You will need to configure separate agent accounts, associated with a different device using unique line for each scenario.  As unconventional as this is, the agents will have to remember which device to login with, for the specific scenario (remote/jabber, on premise EM Profile or static config on the end user station).  This is problematic when agents do not log out, so that will be a training / coaching / supervisor enforcement concern.

Example:

User Name

 agent1a

User First Name

 Bob

User Last Name

 Smith

Device

 csfAgent1a (with Line x1000)

Then:

User Name

 agent1b

User First Name

 Bob

User Last Name

 Smith

Device

 emProfileAgent1b (with Line x1100)

...etc.

Keeping multiple sets of agent skills consistent for the end user will be challenging.  

The reports will probably be a nightmare to reconcile with work force management and business KPI's; but using a consistent agent First Name and Last Name could/should help there.

Best wishes.  Hope this helps.

-Sean