![]() |
|
#1
|
|||
|
|||
|
My problem:
I have configured callbacks on a queue and have them working correctly, but.. When the callback is used I can find no way to configure the account code to be passed through to the PBX with the number to call. - We have many queues so cannot configure this on a global basis. - We are using Outdial campaigns for other applications and these are configured with the account code, is it possible to link a callback to a campaign Thanks Jim |
|
#2
|
|||
|
|||
|
Hi Jim
You say callbacks are working correctly, but then indicate the number for the PBX to call is not being passed to the PBX. Is the problem specifically to do with account codes only? I am not sure the Zeacom will understand the PBX account codes - We stopped using them because they're so open to abuse. A more common way in the UK is to put phones into seperate tenancy which have different route selection lists. What is the phone system and model number? cheers |
|
#3
|
|||
|
|||
|
Account codes can be generated in several ways so I'll assume you're using the official NEC account code methodology instead of some sort of string appended to the number to dial.
The only real way of entering account codes for a callback as described is to put an account code key on your queue agent's phone. Once the call is connected your agent will need to press the account code button and then enter the account code manually. The feature code is F0085. Use command 90 xxxx,YY F0085 to program it on a dterm where xxxx is the extension number and yy is the button number to put the feature on. |
|
#4
|
|||
|
|||
|
godlike:
Yes the problem is just with trying to get an account code associated with the callback automatically. The calling number is generated correctly. ShayneB: I will investigate your suggestion further, though it still requires manual intervention on the part of the CSR. |
|
#5
|
|||
|
|||
|
Quote:
|
![]() |
| Tags |
| account, callback, zeacom |
| Thread Tools | |
| Display Modes | |
|
|