Hi,
Looks like you've configured this on the Campaign, as opposed to Calling List. This is fine. You can configure it on one of multiple objects, with Calling List taking priority (see
here for the objects where it can be configured.)
Given you've done it on the campaign, you dont need to do anything for the calling list.
Is it not working for you?
Regards,
------------------------------
Jason Mclennan
Commonwealth Bank of Australia
------------------------------
Original Message:
Sent: 10-01-2018 15:49
From: Koli Sandeep Kumar
Subject: Dynamic Disposition Codes for Outbound
Hi Jason,
can you help with this, please.
Thank you!
------------------------------
Koli Sandeep Kumar
Original Message:
Sent: 09-21-2018 05:56
From: Koli Sandeep Kumar
Subject: Dynamic Disposition Codes for Outbound
Hi Jason,
Can you please help on this request.
Thank you!
------------------------------
Koli Sandeep Kumar
Original Message:
Sent: 09-19-2018 06:54
From: Koli Sandeep Kumar
Subject: Dynamic Disposition Codes for Outbound
hi Jason,
Can you help with the below. thank you very much for the feedback...kindly help on this.
I have got as far as this step below what do you need enter in the calling list ? I have add the annex tab as indicated.
- Now we need to configure the campaign object with a reference to the transaction list we created in the above step. I normally recommend configuring this on the calling list as it gives you the most flexibility. So on the annex of your calling list add the following:
[userdatalist]
IW_OverrideOptions=list_iws_override_BMW_VOUT
------------------------------
Koli Sandeep Kumar
Original Message:
Sent: 09-16-2018 18:43
From: Jason Mclennan
Subject: Dynamic Disposition Codes for Outbound
So the thing is you need to link this to your campaign, not your agent.
- Check the application configuraiton matches the below:
- The below assumes you have left the
interaction.override-option-key
for IWS/WDE at it's default value of IW_OverrideOptions
- the
user_data_section_name
option for OCS has a value of userdatalist
- Create a transaction list object, that will reference your new Business Attribute object containing your disposition codes. I'm going to call it list_iws_override_BMW_VOUT. It should contain the following option as a minimum (which is the reference to the dispositon list:
[interaction-workspace]
interaction.disposition.value-business-attribute=Wrapcode_BMW_VOUT
- Now we need to configure the campaign object with a reference to the transaction list we created in the above step. I normally recommend configuring this on the calling list as it gives you the most flexibility. So on the annex of your calling list add the following:
[userdatalist]
IW_OverrideOptions=list_iws_override_BMW_VOUT
What should happen now is:
- OCS will attach the KVP
IW_OverrideOptions=list_iws_override_BMW_VOUT
to any calls made from this list.
- IWS will interpret this KVP when the call arrives and read the list_iws_override_BMW_VOUT transaction list for the override options.
- IWS will use the disposition override and read the Wrapcode_BMW_VOUT Business Attribute values and present those to the agent.
Good luck
------------------------------
Jason Mclennan
Commonwealth Bank of Australia
Original Message:
Sent: 09-14-2018 06:04
From: Koli Sandeep Kumar
Subject: Dynamic Disposition Codes for Outbound
Hi Jason,
Can you please help on this as we are using interaction workspace 8.1 is this still the same?
I have created the outbound wrapcodes list Wrapcode_BMW_VOUT we are just unsure how to link them to the agents.
Thank you!
------------------------------
Koli Sandeep Kumar
Original Message:
Sent: 09-13-2018 00:29
From: Jason Mclennan
Subject: Dynamic Disposition Codes for Outbound
Unless your using a very very old version of IWS, functionlity should be the same as WDE. I've updated teh original answer a little to hopefully clarify a few things, but if there's any questions, feel free to post them.
------------------------------
Jason Mclennan
Commonwealth Bank of Australia
Original Message:
Sent: 09-12-2018 04:43
From: Koli Sandeep Kumar
Subject: Dynamic Disposition Codes for Outbound
Hi Jason,
If we use IWS, what changes we need to do or check.
Please let us know on this.
thank you!
------------------------------
Koli Sandeep Kumar
Original Message:
Sent: 07-13-2018 01:59
From: Jason Mclennan
Subject: Dynamic Disposition Codes for Outbound
Assuming your using WDE:
- Create your separate Business Attributes objects for each campaign as required.
- Create one or more Transaction List that contains your WDE Disposition options, maybe something like this, lets call it WDE_Camp_A_Dispositions:
[interaction-workspace]
interaction.disposition.is-mandatory=true
interaction.disposition.is-read-only-on-idle=false
interaction.disposition.key-name=CALL_OUTCOME
interaction.disposition.use-attached-data=false
interaction.disposition.use-connection-id=true
interaction.disposition.value-business-attribute=Camp A Outbound Dispositions
- In the annex of the Campaign or CallingList, set the userdatalist\IW_OverrideOptions option to a value of the name of Transaction List you've created (ie. WDE_Camp_A_Dispositions)
The presence of the IW_OverrideOptions KVP wil override the agents default configuration.
------------------------------
Jason McLennan
Commonwealth Bank of Australia
Original Message:
Sent: 07-12-2018 15:32
From: Steve Steffner
Subject: Dynamic Disposition Codes for Outbound
I am trying to enable Disposition Codes for Outbound Dialing (OCS) and have a requirement to serve up a different set of Disposition Codes to the agent based on which campaign the call they received originated from. The ultimate goal is to limit the agent from seeing and applying non-applicable codes based on the purpose of the campaign. Seems this should be straight forward, but I have yet to identify a workable solution for agents that belong to multiple campaigns. Any suggestions or feedback?
Thanks!