Genesys PureConnect was an omnichannel contact center platform that offered cloud-based or on-premise deployments. It featured a SIP-based architecture with VoIP capabilities, allowing companies to connect legacy voice systems and use existing phones. A legacy product, new users are encouraged to investigate Genesys Cloud.
N/A
Jira Service Management
Score 8.1 out of 10
N/A
Jira Service Management (formerly Jira Service Desk, now including features from the former Mindville Insight, acquired by Atlassian in June 2020) is a service desk software that is purpose-built for IT, service, and support teams. The software provides everything IT and support teams need out-of-the-box for service request, incident, problem and change management. Jira Service Management integrates seamlessly with Jira Software so that IT and development teams can work better together. Users…
$0
per month
Pricing
Genesys PureConnect (discontinued)
Jira Service Management
Editions & Modules
No answers on this topic
Free
$0
per month
Standard
$20
per agent/per month
Premium
$40
per agent/per month
Enterprise
Contact sales team
Offerings
Pricing Offerings
Genesys PureConnect (discontinued)
Jira Service Management
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Genesys PureConnect (discontinued)
Jira Service Management
Considered Both Products
Genesys PureConnect (discontinued)
No answer on this topic
Jira Service Management
Verified User
Project Manager
Chose Jira Service Management
I dont have experience using any other similar products
CIC is best suited for business models that rely on heavily leverage Data Integration especially one like ours that require real-time and high-speed data access for billing and customer integration. CIC is not well suited for small organizations < 50 where they are only answering phones in the course of doing business VS. the business is the phone.
Great to manage your issues in a clear and centralised way. If your development teams work with Jira, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up
Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem).
No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability.
Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive.
Request forms are very basic and there is no native dynamic field ability available.
We are so embedded on Pure Connect that we like to progress with it. For instance, we are looking into ways to provide different solutions to our customers, help our business to succeed, and work in a better CX.
One of the biggest advantages is that all is in one platform.
The interface is only semi user-friendly on almost every front. Agent experience is lacking and we have found many limitations within the system. Workforce forecasting is not as robust as expected. Quality continues to be a struggle. Interaction searches are not robust.
Jira Service Management tool will serve it's purpose to do what it is meant to be. It has it's own limitataions on few features, however it's the industry standard ticketing tool. All covers all the processes that required to resolve the issues. It has various use cases in incident management, Request management etc.
The application itself uses a hub and spoke model that can help isolate errors in one section of the application from the rest, creating a much more stable overall program. Of all of the outages that we've had with our contact center platform, I can count on one hand how often it was truly a Genesys issue rather than a network issue, server issue or issue with a platform relied upon for an integration (web services, db calls).
Some of the client applications take a bit of time on initial load, but with the move towards web based applications that issue is alleviated. You can tell that effort really isn't putting into the desktop apps any longer and that the client development effort is being put into bringing Interaction Connect closer to feature parity with the desktop (and bringing wholly new features to Connect). As far as IVR operations, web service calls, database operations: they all operate reasonably.
Some cases are resolved quickly others are taking longer and the reseller sometimes has to chase support several times and explain the issue seen several times. While being a direct customer before, I recognise this and it seems that when a case moves to another engineer they don’t read the previous case notes or don’t understand what has been done. This, from a customers perspective, slows down resolution times.
I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.
I liked the setup of the whole class. The instructor knew the topic well enough to answer questions from entry level to a more advanced one.
Instructor encouraged participation of the whole class and was able to engage every one. Also provided "real live" examples so everyone can relate to it.
The online training itself is good. You are provided resources and can self study to a certain point, but the pacing always felt off. Either snails pace or like trying to drink from a fire hose. I think this easily could have had to do with course material and my personal preparations, though. I would say my main gripe is that since the acquisition the team responsible for actually booking training is very unresponsive and often not knowledgeable about the courses they offer. Booking my last training was a real chore.
Don't try to go the perfect solution as a first target. Work on answer the more needs with a simple solution. Then analyse and try again to answer the most needs with adding a bit if complexity only if require. No needs to customise straight from the beginning or deployment takes too long.
Call Manager, you had to buy all the components that are out of the box for PureConnect. The licensing model is more expensive on the Cisco side vs the Genesys PureConnect side. Lastly was on the Cisco side since you have to connect/integrate all the components on the cisco side you have to have so many vendors to install those parts. This drives the cost up even more so it was not worth going that route for our organization.
When I evaluated Spiceworks, it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did. JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and JIRA was the better option since it was less expensive and geared towards being a ticketing system.
Genesys PureConnect's core and adjunct model allows for fairly easy growth in satellite locations via off site session managers, remote located media servers, remote content servers, etc to allow you to spread the infrastructure out while not pushing as much network traffic to your core data centers.
We're improving our CX by optimizing our call centers, using additional attributes and keys to identify the best rep for the job.
We are also streamlining the journey of each individual customer by using PureConnect as the central interface for omnichannel interactions, allowing us to pick up the conversation where we left off.
Using additional attributes that start with the contact center interaction, we're able to track a student journey and proactively step in - increasing our individualized support to focus on the student outcome.
