" /> Configuration of 3rd Party tools (SMS, Fax, E-mail) in Genesys Suite. - Genesys CTI User Forum

Author Topic: Configuration of 3rd Party tools (SMS, Fax, E-mail) in Genesys Suite.  (Read 14487 times)

This topic contains a post which is marked as Best Answer. Press here if you would like to see it.

Manoharan

  • Guest
Advertisement
3rd Party email (MS Exchange 2007)/chat application GUI may be used by agent.
can anyone  guide on the integration of these application with Genesys suite.Thanks in advance

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Hi Manoharan,

Sorry for starting with question... What kind of integration you're thinking about - client-side or server-side? What do you mean by integration of Exchange 2007?

Thanks
R.

Manoharan

  • Guest
Hi,
Thanks  for the response.Assume for email MS Exchange 2007 is used.for fax (Captaris RightFax)is used. In Genesys suite we need to Configure Email-Server or respective servers for other channels (fax/chat) in Genesys.when we are using 3rd party clients for multi-media interactions how to go about in integration with Genesys Suite.


(At present we are using Genesys Demosrv.in that we have configured  Genesys E-mail server,chat server as applications in CME.)

Offline Adam G.

  • Hero Member
  • *****
  • Posts: 552
  • Karma: 12
  • Still Gorgeous.......
Also have a look at a company called Conseros [url=http://www.conseros.com]www.conseros.com[/url] and their GTL product. It links to Ixn Server and therefore the routing is done in IRD. It's actually better than MCR (I have worked with both products).

Pavel

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Manoharan,

You can find below some notes about "integration" of Genesys and Exchange but I would recommend you to hire someone experienced in Genesys Multimedia to help with configuration of your system and integration on client-side. Your questions are complex and it will be hard to help you via this forum only. Genesys isn't cheap system and saving money on consultant's work isn't the best strategy if you want get maximum benefits from the system.

---
Genesys Multimedia can be easily integrated with Exchange 2007 using Email Server Java (ESJ) via POP3/SMTP or IMAP protocol. It's necessary to create new POP client section in options of ESJ. In that section you define connection parameters for particular mailbox on your Exchange. ESJ will then check that mailbox in regular interval, retrieve new incoming emails and submit them to routing.

You can integrate faxes in the same way in case your fax server support fax-to-mail functionality.

Integration on client-side - Genesys has several SDKs that could be used for development of dedicated agent desktop or for integration of Genesys functionalities into existing applications.
---

Hope it helps you
R.





Hugo Thomsen

  • Guest
Hi Pavel,

I note that you have worked with Conseros - I would be very interested in your view on the gap between BPR and Conseros, if you wouldn't mind sharing that.

Cheers

Hugo


Marked as best answer by on April 26, 2025, 12:51:30 AM

Offline PeterJ

  • Newbie
  • *
  • Posts: 16
  • Karma: 0
Hi Hugo,

Ive done feasibility study and business case analysis for BPR / Conseros GTL for one telco operator.

I do not how deep is your knowledge about GTL and BPR, so I try to start from the beginning.

First of all, Genesys BPR and Conseros GTL are not comparable products.

I would say BPR is an interface / platform provided by Genesys to enable integration of 3rd Party Work items into Genesys environment. Using that interface you can submit (create) new interaction in INX (Genesys Interaction Server). Once submitted interaction is routed by Router (the same process as for e.g. e-mail).

GTL is product what is taking advantage of Genesys BPR - it is using the interface to submit work items into Genesys. Its huge advantage is that it is designed for business users. You can configure it and manage all work items in a nice GUI. You can set-up various rules for prioritization / reprioritization and more. I can provide more information if you are interested.

It works as follows:

- GTL extracts work items from various sources (e.g. CRM) and creates "work items". This phase is called Capture phase.

- When "work item" is created, various rules are applied to set desired priority and business value to each work item. There are rules applied to pending tasks as well - to re-prioritize tasks as SLA expires. This is Calculation phase.

- And finally, there is Distribution Phase. This is where GTL and BPR meet. GTL submits task into INX (distribution point - Queue - is configurable) and URS is routing the interaction. The communication works in both directions.

To conclude it I would compare BPR to Java and GTL to Java application.

Hope it helps.

Peter


Thorsten

  • Guest
Good evening,

I work for Conseros and we know Pavel from a previous project. Pavel, thank you very much for your positive feedback.

@PeterJ
Your summary is excellent.  If you need additional information on Conseros GTL, please send an e-mail to contact@conseros.com, and we will get in contact directly with you. We would be happy to share additional information and webinar if interested.

Some quick notes on GTL and BPR:
1. At a high level – Genesys BPR is not a product - it is a concept that requires custom development (Open Media, integration server, Interaction Server, and Universal Routing Server) to realize BPR goals and benefits. That is the first part of the challenge in terms of time, effort and risk.

2. The second key challenge we’ve seen is in the area of reporting and real-time monitoring.  The business requirements here are completely different from typical voice and interaction focused reporting – tasks and the way you need to manage task fulfillment is very different from “voice”.

3. Third part, and probably the most important, is the need for an implementation methodology to guide business and technical people through the process.

As PeterJ mentioned, if you want to implement the Business Process Routing concept you can either start from scratch and build a lot of IXN scripts, routing rules, reports and your own integration server – or you can leverage something like Conseros Global Task List. At the end of the day it is a commercial question and requires an evaluation of potential project risks.  If the scope is simple – e.g.: route some faxes into the call center – Conseros would recommend a custom, OpenMedia based Integration. When the scope moves towards more complex business process / CEBP type integration (some have called this dynamic enterprise, or centralized customer service organization) we would recommend taking a closer look at GTL.  GTL has already proven that it works and delivers BPR with out of the box functionality, mitigating many of the risks often seen in custom development.

The business benefits and the ROI for a BPR project are potential large. The more FTE’s you have in your customer service organization (front and back office, this isn’t only about the call center) the better the ROI will be. On another note, we are seeing more requests for BPR (Business Process Routing) or CEBP (Communication Enabled Business Processes) solutions – customers understand the benefits of such solutions.

Take care
Thorsten

Offline HugoThomsen

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
    • My CV
[quote author=Pavel link=topic=2988.msg12069#msg12069 date=1211364769]
Also have a look at a company called Conseros [url=http://www.conseros.com]www.conseros.com[/url] and their GTL product. It links to Ixn Server and therefore the routing is done in IRD. It's actually better than MCR (I have worked with both products).

Hi Pavel,
I am working on a gap analysis between BPR and Conseros ... i.e. what does Conseros offer that BPR does not. Looking at the Interaction Server and its integration with URS, it appears to me that the the main gaps are that Conseros has a separate, work item related realtime reporting facility, its own configuration interface that is slightly easier to use that updating routing strategies, and (the most important point) the capacity to escalate call priorities according to segment etc. without adding a plethora of VQs and GVQs. Can you add to that, resp. tell me that I am wrong anywhere ?
Cheers,
Hugo

Pavel
[/quote]

Offline HugoThomsen

  • Newbie
  • *
  • Posts: 4
  • Karma: 0
    • My CV
[quote author=PeterJ link=topic=2988.msg12655#msg12655 date=1215002813]
Hi Hugo,

Ive done feasibility study and business case analysis for BPR / Conseros GTL for one telco operator.

Hi Peter,

Whoops - I didn't even spot your response until now ! Good stuff, thanks a bunch ! Your reply was right spot on, really. If you have any more detail, I would be more than grateful to have the opportunity to look at it !

Regards,

Hugo

I do not how deep is your knowledge about GTL and BPR, so I try to start from the beginning.

First of all, Genesys BPR and Conseros GTL are not comparable products.

I would say BPR is an interface / platform provided by Genesys to enable integration of 3rd Party Work items into Genesys environment. Using that interface you can submit (create) new interaction in INX (Genesys Interaction Server). Once submitted interaction is routed by Router (the same process as for e.g. e-mail).

GTL is product what is taking advantage of Genesys BPR - it is using the interface to submit work items into Genesys. Its huge advantage is that it is designed for business users. You can configure it and manage all work items in a nice GUI. You can set-up various rules for prioritization / reprioritization and more. I can provide more information if you are interested.

It works as follows:

- GTL extracts work items from various sources (e.g. CRM) and creates "work items". This phase is called Capture phase.

- When "work item" is created, various rules are applied to set desired priority and business value to each work item. There are rules applied to pending tasks as well - to re-prioritize tasks as SLA expires. This is Calculation phase.

- And finally, there is Distribution Phase. This is where GTL and BPR meet. GTL submits task into INX (distribution point - Queue - is configurable) and URS is routing the interaction. The communication works in both directions.

To conclude it I would compare BPR to Java and GTL to Java application.

Hope it helps.

Peter


[/quote]