Cisco Unified Contact Center is a contact center platform that can support up to 24,000 agents. It supports call routing, omnichannel integrations, and a management portal for creating customer profiles, segmentation, and resource monitoring.
N/A
Salesforce Service Cloud
Score 8.6 out of 10
N/A
Service Cloud is a customer service platform that helps businesses manage and resolve customer inquiries and issues. It provides tools for case management, knowledge base, omni-channel support, automation, and analytics, enabling companies to deliver exceptional customer service experiences.
I would recommend it to other people in my contact and business circle, but if I recommend it to someone who has certain difficulties in accessing some tools within Cisco, he may have great difficulty in getting help because of the support that is lacking in most of the times.
I think Service Cloud is best suited for medium to large operations that require both proactive and reactive service. It’s a great fit for post-sales support. However, I wouldn’t recommend it for very small companies because it can be quite costly, and many of the features may go unused. Salesforce also performs best when you have a capable team managing it, so it’s important to consider your organization’s size and readiness before starting. Once you do, I recommend exploring other parts of the Salesforce ecosystem—Service Cloud works even better when integrated with Sales Cloud, since it allows better visibility across teams.
Provides you with a solid routing engine that was built to handle Service Provider level throughput - if you need stability and a work horse this is the platform for you.
The core features on the whole are good, but where UCCE is very good is the eco-system of Solutions Plus partner integrations that expand on the core capabilities with the market leaders in areas such as WFO, Campaign Management, Biometrics and Natural Language.
The investment Cisco makes in the CC space means they are always improving the platform features, scale and reliability.
Email to case is an interesting piece of it. The threading is very strong, sometimes too strong, but it does very well at handling the incoming emails.
The omnichannel routing, using skill-based routing is really effective.
Pathing. So making the workflow and helping the team understand what it is that they're trying to do, what they have to accomplish, those step-by-step pieces. That's really helpful.
After 25+ years, the product still requires experienced and highly skilled engineers to deploy the product properly per Cisco Best Practice guidelines.
Third-party integrations are also very cumbersome and require highly skilled and experienced engineers and significant time and financial investment to deploy.
Upgrading the product is cumbersome and requires Cisco ATP or Cisco AS which is time consuming and very expensive.
We had a principle initially to try and use Omni as much as we can from the user experience perspective, but have found that fairly restrictive. It was very difficult to actually get the right customer experience and customer engagement going. So we're actually on a journey at the moment to replace all of our Omni with Lightning web components that gives us that flexibility. That's probably one area where we've had some challenges in terms of how we've used the product out of the box.
Professional edition works best for a small company with lower call volumes and is very useful but as you grow exponetially I think it has limited ability to do all the things we want to - SLA management, defect, release management to name a few. Reports and dashboards being available in real time.
Cisco Unified Contact Center is a scalable product . Can be used in amy organizational units not only the contact center . Can be used for many IT Helpdesk setups and any internal or external CC . We can use it to automate the outbound dialing as well for marketting and invoices and other use cases
I had Salesforce experience prior to using Service Cloud which made it a little easier to learn and navigate, but overall my team (some who had no Salesforce experience) caught on very quickly and found Service Cloud to be easy to use.
Working on an application that caters to customer needs requires a platform that acts as a mediator between the actual person and the client. This mediator handles the customer and resolves many of their doubts, helps them map through the entire process, and automates the processes. Such a platform is Salesforce Service Cloud. For queries that cannot be serviced by the platform, it creates a separate ServiceNow ticket for us, and it is assigned.
The Salesforce Service Cloud generally has very good performance, however the overall new Lightning user experience can bring that down. For example, if you have too many tabs open, then it can take a while for the Lightning UI to load. This UI is probably not well equipped to handle loading of all of that information at once, but Users tend to leave their tabs open all day long. It can also be fickle depending on which browser you use, what extensions you have installed, and whether you've cleared your cache. This can be the downfall with any software as a service though, not just Salesforce
Cisco Unified Contact center is a very smart & reliable solution to go for. Its active-active sight base architecture and [customizable] features really help to deliver efficient customer service, enhanced next-gen experience, and uninterrupted operations. I believe every [organization] should opt for it if required.
Salesforce offers support, although it generally gets routed to overseas support teams first, and once they are unable to help, it gets escalated up the chain to higher tiers. Frequently, the answer back from support is that there is no native solution, and we either have to turn to the AppExchange for some solution provided by another developer, or custom build our own solution.
Our in-person training was provided by our implementation partner and it was quite good. This was in part because we were already working with them and so it naturally leant itself to a good training relationship. And because they were building our customizations and configuring things, they could then provide training on those things naturally.
Trailheads are great but it was often unclear what actually applied to our organization. This made it difficult to get a whole lot out of it. Part of it is that because the basic Salesforce features didn't quite work for us, we had to add customizations, which then nullified a lot of the training.
I would go through an implementation very differently knowing what I know now. It was difficult coming from systems we liked in post-sales service and having to adapt to the clunky and underwhelming feature set in Salesforce. I would trim back our expectations
Similar I guess, however, I feel like Avaya was more suited for a contact center and allowed for all information to be in one place. The QA Forms were more flexible and easy to review. Predicative analysis was available to assist with scheduling and staffing. It was easier to manipulate and implement- I didn't need to go through 3 different parties to make a simply modification.
We selected this product because we already had some competencies in Salesforce. We own a Salesforce partner with expertise in this area, and on top of that, Salesforce purchased it — it was originally called Velocity. When Salesforce decided to acquire it, that finalized the decision for us.
Licenses are very expensive. The customer has to buy IP telephony or Unified Communication and Collaboration Licenses and for Contact Center Solution licenses separately. There must be a price tone down as the competition is really high. New customers are willing to go for cloud-based solutions [that] are cheaper and easy to deploy.
We have cut our service team in half over the past 5 years due to the efficiency of the tool
The amount of direct inquiries to our technical team is less than 10% compared to the number support tickets that get entered in the system for them to work in a more organized manner
Responses are 100% more timely because tickets can be responded to by any individual in the queue or on the team, as opposed to direct emails to just one person
