Not Ready Code SCCS 1

[tellyteck1]

Hi, I have seen conflicting responses on the forum. Is it true that web client is necessary for not ready codes? If it is not necessary, how do I go about setting it up on just SCCS? Our web client isnt set up as of yet. Thank you in advance. AJK

 

[sandyml]

You can use Not Ready reason codes without Web Client. Web Client gives you the additional ability to see those codes on your Real Time displays. With just SCCS, you can run reports on the Not Ready codes, but cannot view them realtime.

You'll need to first set it up in the PBX. First, make sure you have feature package 155 (ACNT).
Then, make sure you have an ADS block configured in LD 23. Then, on the ACD queue that the phones are programmed in, answer Yes to NRAC. The agent phones need to have an ACNT key.
In Symposium, configure your Not Ready codes in the Activity Codes section -- that gives them a name for your reports.

 

[tellyteck1]

Thank you so much; you definitely have pointed me in the right direction; I will try today to get that done. Thanks again for great help

 

[tellyteck1]

Hi again, in ld 17 I cant see DCUS. In ld 23 it apparent that the ADS Data Block is not built. Is the following all that is required for the ADS Data Block? Will this affect the symposium - dont want it to go down!
TYPE ADS
CUST 0
AID YES
IDLB 4000
IDUB 9000
LOG 200
MQA YES
MQAS NO
MQAP YES
MQCF YES
MCFD

In the ACD queues I cannot see ACNT anywhere. To what prompt do I add that to? Is it correct that I shouldnt make any changes to the ACDs or the symposium might go down? If so I will do this on a scheduled outage. Thank you for all your help AJK

 

[sandyml]

Oops, good point. If you don't already have an ADS block and have to build one, do this off hours; it will log your agents out, and also your voicemail ports.
You'll find DCUS in the PARM datablock -- go to LD 22:
REQ PRT
TYPE PARM
Your sample looks ok. Is this already built?
Also in LD 22, print your features:

REQ PRT
TYPE PKG
You should see packages 155 and 311 since you are a Symposium site. If 155 is missing, you cannot do Not Ready codes.

 

[tellyteck1]

hi Sandy, I have all the packages required. Thanks for warning me about the agents getting logged out! I do not have the ADS built. So just to clarify: Make ADS, change NRAC to yes, make sure DCUS is bigger than 1, deaquire sets, make ACNT on a key on each set (correct - KEY 04 XXXX ACNT ?), and finally under Switch Admin put in activity codes. Sound correct to you? Thanks very much-appreciate it.AJK

 

[sandyml]

Yeah. In your ADS block, go ahead and set your IDLB to 1000 and your UDUB to 9999 -- that way, you won't ever have a conflict. On your V/M ports, you can disable and re-enable the cards and that will log them back in:

LD 32

REQ DISC lsc

then

REQ ENLC lsc

That will log them back in without having to reboot your Meridian Mail or Call Pilot.

Set DCUS to 1. That is all you should need (it's defaulted to NULL).

Best to deacquire phonesets before making change (no ECHG).

That should do you.

 

[tellyteck1]

Thank you Sandy - much appreciated.AJK

 

[tellyteck1]

Hi, doing the not reason ready code implementation tonight. Will the default not ready reason code still work after putting in the ADS block and configuring the ACD's? The call center has not informed agents of any new codes going in yet so they are worried that the default will not work for the weekend once we configure manual default not ready reason codes. They plan to inform the call center on Monday. Thank you for your help. AJK

 

[tellyteck1]

Never mind. I found one of sandyml's tek-tips. Thanks sandyml. The answer is of course it will work its the default when no other condition has been met!AJK