Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: victor on June 06, 2018, 04:33:35 AM
-
I have been battling with something heavy recently...
I am not very clear on the value of letting Genesys expand into the omni channel, predominantly dominated by Salesforce and, now, ServiceNow. I am starting to suspect that by retaining non-legacy functionality outside Genesys, we can provide much more value and functionality to our clients.
This bring me to the whole Genesys conundrum: Genesys does have millions of features, but what it the point when majority of the activity is now done outside Genesys? As consultants many of us make money on supporting the product, but we are getting paid by the customer. So perhaps we should be supporting the client and not the product? I am unsure where exactly this will lead, but I think it would be amazing to start a group that examines different ways of combining Genesys with other platforms to provide the best possible outcome for the user as well as ourselves.
In my constant quest to improve our client opportunities, I was thinking about offering hybrid environments to our existing customers. Something in a form of current Genesys framework for existing clients and Bright Pattern or some other solutions for an overflow and expansion outside the normal voice.
For example, Watson or Lex or even Einstein: I do not see the value in integrating it with Genesys framework as opposed to Salesforce / SNOW: Everything would be much closer to data if I would connect directly with CRM vs. via middleware.
Or, perhaps, using Amazon Kinesis to provide screen and voice recording?
Overall, maybe I am late to the game, but I feel that it is not about pushing Genesys anymore, but about putting several of this solutions together and instead of passing on the revenue from the obvious overlap to the vendors between Genesys and Salesforce, Genesys and Verint, Genesys and Cisco, focus on re-funneling that revenue to us, the consultants, by using our knowhow of different product to limit them to where they serve best and develop the tools that link them together?
What do you think?
-
Well I think we are again at that point in where we defined not to sale legacy pbx as the main business but software instead and use pbx as a tool. Later it went to another evolution as VoIP. Now we are migrating to instant messaging and similar tools where Genesys is kinda slow to adopt.
So yes, for me now Genesys is a side tool but my main goal is to provide the solution to the customer with anything that satisfies his needs, to be honest many other tools do that job better and easier than Genesys. Chat bots for example, as others offer a "simple" and faster deployment on Genesys we have Kate...which works...? I haven't seen or at least Genesys guys hasn't been able to show something functional and straight ways to integrate so far...maybe Europe or US have more ready to deploy engineering, but here, South America, there is a real demand from customers, much more aggressive as when it was voip, just because it is easier and should be far faster...but Genesys lays on his dreams...so I can't relay on them to close business with customers.
I would love to see how bright pattern works. Haven't got the chance yet. If you have something please share :)
Enviado de meu E6633 usando o Tapatalk
-
I am thinking about compilation of tools that would allow us to focus on delivering the requirements without overlap, allowing us to pocket the difference.
Kate is a joke as far as I can tell. Compared to Watson and LEX it is really just silly. I managed to get LEX to run with AmazonConnect within 10 minutes. Watson and Bright Pattern - 5. This is not because LEX is better, but because the underlying platform - AWS / BP are designed for cloud. At least this is what I think.