Avaya Contact Center is delivered through Avaya Infinity, a cloud-native platform designed to orchestrate customer interactions across multiple channels. Built on a Microservices Architecture with open AI Orchestration, Avaya Infinity enables organizations to manage Voice, Digital, Email, and Messaging interactions. The system provides Dynamic Routing, AI automation, and real-time orchestration—with the flexibility to deploy in the cloud, on-premises, or in a hybrid…
N/A
Salesforce Agentforce Service
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.
$25
per month
Pricing
Avaya Contact Center
Salesforce Agentforce Service
Editions & Modules
No answers on this topic
Starter Suite
$25
per month
Pro Suite
$100
per month per user
Enterprise
$165
per month per user
Unlimited
$330
per month per user
Agentforce 1
$550
per month per user
Offerings
Pricing Offerings
Avaya Contact Center
Salesforce Agentforce Service
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Required
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Avaya Contact Center
Salesforce Agentforce Service
Features
Avaya Contact Center
Salesforce Agentforce Service
Contact Center Software
Comparison of Contact Center Software features of Product A and Product B
Avaya Contact Center
8.1
38 Ratings
4% below category average
Salesforce Agentforce Service
-
Ratings
Agent dashboard
8.036 Ratings
00 Ratings
Validate callers
8.333 Ratings
00 Ratings
Outbound response
6.032 Ratings
00 Ratings
Call forwarding
9.036 Ratings
00 Ratings
Click-to-call (CTC)
8.729 Ratings
00 Ratings
Warm transfer
8.836 Ratings
00 Ratings
Predictive dialing
5.828 Ratings
00 Ratings
Interactive voice response
9.332 Ratings
00 Ratings
REST APIs
7.927 Ratings
00 Ratings
Call scripts
6.730 Ratings
00 Ratings
Call tracking
8.735 Ratings
00 Ratings
Multichannel integration
9.433 Ratings
00 Ratings
CRM software integration
8.032 Ratings
00 Ratings
Workforce Optimization (WFO)
Comparison of Workforce Optimization (WFO) features of Product A and Product B
Avaya Contact Center
8.0
38 Ratings
4% below category average
Salesforce Agentforce Service
-
Ratings
Inbound call routing
8.637 Ratings
00 Ratings
Omnichannel inbound routing
8.633 Ratings
00 Ratings
Recording
8.136 Ratings
00 Ratings
Quality management
7.934 Ratings
00 Ratings
Call analytics
8.134 Ratings
00 Ratings
Historical reporting
8.235 Ratings
00 Ratings
Live reporting
6.834 Ratings
00 Ratings
Customer surveys
8.031 Ratings
00 Ratings
Customer interaction analytics
7.730 Ratings
00 Ratings
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
Avaya Contact Center
-
Ratings
Salesforce Agentforce Service
8.0
81 Ratings
2% below category average
Organize and prioritize service tickets
00 Ratings
8.379 Ratings
Expert directory
00 Ratings
7.957 Ratings
Subscription-based notifications
00 Ratings
8.367 Ratings
ITSM collaboration and documentation
00 Ratings
7.062 Ratings
Ticket creation and submission
00 Ratings
8.779 Ratings
Ticket response
00 Ratings
8.078 Ratings
Self Help Community
Comparison of Self Help Community features of Product A and Product B
Avaya Contact Center
-
Ratings
Salesforce Agentforce Service
8.7
76 Ratings
8% above category average
External knowledge base
00 Ratings
8.567 Ratings
Internal knowledge base
00 Ratings
8.874 Ratings
Multi-Channel Help
Comparison of Multi-Channel Help features of Product A and Product B
I would say well-suited for the everyday user, with the ability to use the products. I think it's really user-friendly in that way. The lack of education for the end users, maybe through some of our companies, makes it difficult. And the turnover.
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.
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.
Calls are automatically terminated at an agent and do not allow for the agent to "manually" answer the incoming call. This is very problematic as agents are not able to prepare properly for incoming calls. In addition, agents have stepped away from their desks and forgotten to put themselves in an away status, and calls have been directed to them, and they just sit there with no agent present. This is a very undesirable feature of the system.
Password resets are extremely problematic and continuously cause problems for users. Agents are prompted to change their password upon expiry, and when they follow the instructions as outlined, it rarely works and ends up needing a full reset. The challenge questions are useless and do not work at all.
Support can be a bit challenging as there are definite language barriers that have made both explaining the problem and understanding the recommended solution difficult.
The system is sometimes unreliable and will randomly log agents out with no explanation. Agents are then advised by support to log out, clear cache, and log back in. This is not feasible in a busy call center.
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.
I am really not the decision maker on this subject but given the cost of the investment in Avaya, I do not see the company not renewing the use of Avaya. The new licensing model no longer requires expensive upgrades to stay current with new features added to the system and really helps with the cost of investment.
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.
Avaya has versatility in calling, receiving, and configuring. Being able to have notion of location, exchange of messages. we could see supplier information and configure it to our liking. as it is practicality for configuration and manual handling. Interactive and easy to learn screen. Being able to generate call reports for analysis of service in others
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
I give it this rating because the support services of Avaya have proven to be reliable when needed. Great feedback for our queries has always been received from the support agents. 24/7 availability of support, which is very essential as our Call Center department also functions this way, therefore, the knowledge and technical support we require is always available to us.
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
Switched from Polycom to Avaya, although polycom worked well there were too many reoccuring connectivity issues and the turn around time for solving them was also too long. Avaya has fewer connectivity problems and their support is much better too. Pricing wise they were similar so we didn't have much to lose.
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.
Overall from a business objective standpoint, Avaya has to have had a positive impact on our Return on Investment. Its use in day-to-day operations has been beneficial to not only the company, but the business as well.
Using the Avaya soft phones supplies a business or company a way to limit expenditures on the hard phones by allowing the use of Avaya soft phones. The equipment is no longer needed, save for headsets to be used with the application itself.
Business objectives have to be just that, objectives. Economics begs for ways for a company to limit expenditures that may see little or no return. Avaya has tackled this issue and won!
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