" /> Moving from Genesys to Nortel Symposium - Genesys CTI User Forum

Author Topic: Moving from Genesys to Nortel Symposium  (Read 6361 times)

Mark

  • Guest
Moving from Genesys to Nortel Symposium
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Has anyone considered moving from Genesys to Nortel Symposium 100%?

I would like to hear if anyone thinks Symposium is a better product or why some think Geneys is a better product that Symposium and why?

Thanks

Chris

  • Guest
Moving from Genesys to Nortel Symposium
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Having gone the opposite way (from Symposium to Genesys), I can honestly say that Symposium is the superior product, at least for use with a Nortel switch. Symposium aquires the TN, rather than the two AST keys that Genesys does. That means you get much better integration and more functionality. For example, since Genesys can only monitor the two AST keys, and one of them is the incalls, it can't tell the difference between ACD calls delivered to the extension and any other type of call. Symposium can out of the box distinguish between call types. This means that you can have an agent's phone hunt to voicemail and Symposium will not allow ACD calls to go to the agent's voicemail if they don't answer. Instead, Symposium sends the call back to the queue and puts the agent's phone in a not eady state to prevent further calls from being presented. You can do this with Genesys, by configuring the agent's phone to hunt to the queue, but then ANY call that was presented to that phone, ACD or not, would get thrown into the queue if the agent didn't answer. That's no good...what if the agent's supervisor tried to call and the agent didn't answer? That internal call is now in the queue! And when the supervisor realizes it and hangs up...abandoned call! Symposium can tell the difference, and will send unanswered ACD calls to the queue and everything else to voicemail (if that's how the phone is configured). Symposium's reports are much better, as well. Genesys reports for a Nortel switch tend to be...difficult to interpret sometimes (that's a nice way to say it). The outofox Symposium reports are useful, userfriendly and, most importantly, ACCURATE! Besides all that, the integration with the switch is much better. Where Genesys routes calls by instructing the switch to execute a series of transfers, once Symposium has the call it does all the work...the switch has much less to do when Symposium is routing vs. Genesys. You can also set up access ports for Symposium in Meridian Mail. With these you can run all of your busy treatments, menus, etc. from Meridian Mail, and you build this IVR ype functionality right into your routing scripts. You don't need another server to handle that stuff (like VTO).

    Paulo Veras

    • Guest
    Moving from Genesys to Nortel Symposium
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • I agree with Chris. Genesys is much more robust and flexible, but unfortunetly it doesn´t integrate completely with Meridian. Since Symposium is the native Nortel's CTI software, it can see all the Meridian ACD's facilities and is much easier to work with.

    Richard

    • Guest
    Moving from Genesys to Nortel Symposium
    « Reply #3 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • While I don't dissagree with Chris and Paulo's concerns, that is not to say that the problems associated with getting Genesys to work well with the Meridain switch cannot be overcome in most cases.

    In the case of not being sent to an agents phone and not getting answered, our integrator (Aria Solutions) configured a custom softphone for us that resolved these issues. If a call tagged as a Genesys call comes through to the softphone the softphone will initiate a timer which will transfer the call back to the Genesys queue (with a higher prioroty) before the call has a chance to go to the agents personal voice mail, and does not drop to any underlying hunt group, and Genesys retqins control of the call. The softphone then also places that agent on "not ready" to ensure that no more Genesys calls are targeted to this agent until the agent again places their phone in the "ready" state. If a call comes to the agents phone that is not a Genesys call, it is not tagged as a Genesys call and the softphone would let that call ring through to the agent's voice mail without softphone intervention.

    There are also some other limitations such as the inability to play RAN from the Genesys environment (because Nortel does not allow this), that required some creative solutions as well. But there are definatly creative solutions available.

    Other problems that we encountered included a problem with using the Symposium Call Centre Server product as our link, which required us to eventually disable all but 4 of the SCCS services that are normally running. As well we are using the Nortel PC Console product as well as Nortel's Call Pilot product to interact with some calls prior to reaching a routing point controlled by Genesys. This would from time to time would cause additional problems for us, but we have also found solutions for these issues as well.

    In the end we are fairly happy with the Genesys product (as we have been able to work through the integration issues associated with the Nortel switch), and Genesys is flexible enough to allow us to build fairly effectively upon the flexible infastructure we now have in place.