Salesforce Agentforce Service Reviews and Ratings

Rating: 8.6 out of 10

Score

8.6 out of 10

Community insights

TrustRadius Insights for Salesforce Agentforce Service are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Versatility: Users have praised the versatility of Salesforce Service Cloud, highlighting its ability to communicate through various channels like email, web forms, chat, and social media.

Customization Options: Many users have found the platform easy to customize, aligning business practices with service needs without extensive coding requirements.

User Interface: The user interface of Service Cloud is consistently commended for being easy to use, allowing for seamless data input and access while offering customization options like tailored dashboards and reports.

Robust Community Support: Users appreciate the robust community and instructional material provided by Salesforce, making it easier to find solutions for customizations and enhance learning processes.

Reviews

100 Reviews

Salesforce Service Cloud Review

Rating: 8 out of 10

Incentivized

November 5, 2025

Use Cases and Deployment Scope

In my company, I use Salesforce Service Cloud as a Sales Cloud because I enter opportunities and track them until closure. It’s very, very useful and easy for me to track all my opportunities — what stage they’re in and their pipeline status. So overall, it’s been very, very successful.

Pros

Okay, so in terms of details — when I have an opportunity, I just enter it, and it gives me stage-by-stage information, where each stage is associated with a certain probability. For example, if it’s in the opportunity stage, it might be 50%, and if it’s still in the lead stage, it’s around 20%. So it automatically calculates the expected revenue for that opportunity, which is pretty interesting. I don’t have to manually modify or enter any data to understand how much revenue is actually expected from that particular opportunity.

Cons

So when an opportunity is converted into a closed stage, if it’s split across the total duration, that’s very useful — and Salesforce does that. But there are some scenarios where the project is invoiced on a milestone basis. For example, we don’t always invoice a 12-month, $120K project as $10,000 every month. In some contracts with our customers, they might say, “Once you finish this particular module, invoice $25,000,” and then, “Once you finish the rest of the modules, invoice $75,000.” There’s currently no way for me to track that kind of milestone-based customization in Salesforce. That would be an amazing feature if they could bring it to the table.
For example, we don’t always invoice a 12-month, $120K project as $10,000 every month. In some contracts with our customers, they might say, “Once you finish this particular module, invoice $25,000,” and then, “Once you finish the rest of the modules, invoice $75,000.”
There’s currently no way for me to track that kind of milestone-based customization in Salesforce. That would be an amazing feature if they could bring it to the table.

Likelihood to Recommend

Well, anywhere you need to track sales and opportunities in a structured manner, Salesforce can be used. But for very small companies that don’t have a large number of leads to convert, I don’t think Salesforce is the right product for them.

Verified User

Director in Information Technology (1001-5000 employees)

Vetted Review

2 years of experience

Salesfore Service Cloud Review

Rating: 9 out of 10

Incentivized

November 5, 2025

Use Cases and Deployment Scope

We use Service Cloud to track everything — every complaint or issue a customer might have. It’s connected with our call center, which is a third-party provider but fully integrated within our Salesforce environment. Every case — complaints, problems, maintenance — goes through Service Cloud. When an issue becomes more technical and the dealer can’t resolve it, we escalate it to the engineering team. I should also mention that our dealers use Experience Cloud to open cases, so we have two different front ends working together for the same case management process.

Pros

It’s very good at giving us real-time visibility into what’s happening. We’re not yet using all the available analytics features, but even with the reports we currently have, we get valuable insights into the main types of cases we’re facing. This helps us identify patterns and address the root causes of issues.

Cons

It's hard to integrate real time and we have a lot of information on connected vehicle that we could be using more to get a proactive assistance by the contact center so that I think it's half of a problem on Salesforce, half of a problem on our own systems. But for everything, if we have real time, since we are using data cloud and many levels, it can be a bit difficult.

Likelihood to Recommend

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.

Verified User

Manager in Information Technology (10,001+ employees)

Vetted Review

4 years of experience

Salesforce Service Cloud Review

Rating: 8 out of 10

Incentivized

November 5, 2025

Use Cases and Deployment Scope

It basically covers the full sales and service journey — from prospecting, ordering, and quotation to fulfillment and service — the entire customer journey. From “I research” to “I buy,” “I maintain,” and even “I resign,” including all complaint checks as well. It’s also integrated with Communication Cloud for the catalog, which provides all the complex telecommunication bundles across major lines of business like mobile, fixed network, broadband, data transmission, and SD-WAN.

Pros

It’s easy to get started with because it’s an add-on to Sales Cloud and Service Cloud, specifically designed for the communications industry. It solves some — not all, but some — industry-specific problems right out of the box.

Cons

Performance is definitely still an issue, but we’re looking forward to improvements. It’s currently a managed package, and it’s already on the roadmap to be migrated to a core package. Once that happens, performance and stability should be much better.

Likelihood to Recommend

I wouldn’t say it’s perfect for everyone right away, but after getting to know it and putting in some effort with configuration and customization, I think it can fit all types of telecommunication businesses.

Verified User

Director in Information Technology (10,001+ employees)

Vetted Review

5 years of experience

Salesforce Service Cloud Review

Rating: 10 out of 10

Incentivized

November 5, 2025

Use Cases and Deployment Scope

First, we allow customers to raise the cases, and once the cases get created, we work on the cases based on the entitlements. We work on the cases and provide the resolution for those cases. And one more thing — we also do case routing to the particular persons. We are using Field Service Lightning also in Service Cloud, where the users can get the cases assigned to them, and they can work on them onsite as well. So in short, we are using it mainly for case management and field management, mostly in those two areas.

Pros

We have given a provision for customers to raise their cases, and we have also given a provision for the customers to keep track of those cases. There is a provision for raising the cases.
They can track at what level the case is, status-wise and all.
In Service Cloud, we are using the asset information, and they can update their own asset information as well.

Cons

We are looking to automate the entire case management process. That is one thing — we don’t want our service agents to explicitly take the cases and work on them. We are looking for an automation kind of thing. This is where we have room to do more enhancements on those areas.

Likelihood to Recommend

For sure, I’ll give a 10 out of 10, because I’ve been using Service Cloud for the last 14 years, and I’ve seen that customers also like the way they can raise the cases — and not only for cases, but also for the community portals and the sites and all — and they’re fine with it. And for internal users also, it’s really good to track the work and all the things they’re working on. So I’ll rate it 10 out of 10 for Service Cloud.

Durga Kalyan Duggirala

Senior Enterprise Application Analyst in Information Technology at Supermicro (5001-10,000 employees)

Vetted Review

14 years of experience

Salesforce Service Cloud Review

Rating: 8 out of 10

Incentivized

November 5, 2025

Use Cases and Deployment Scope

We are managing our support processes directly from the case, supporting our customers with their challenges. We have an old environment with a lot of legacy processes and many fields, so we need to do some cleanup.

Pros

First of all, it has good integration from Experience Cloud to Salesforce
The UI is very flexible. There are a lot of advantages in Salesforce.

Cons

AI
Case deflection

Likelihood to Recommend

It's a good product for customer support business scenarios. It's not such a good product for internal support.

Verified User

Manager in Information Technology (1001-5000 employees)

Vetted Review

20 years of experience

Salesforce Service Cloud Review

Rating: 9 out of 10

Incentivized

November 5, 2025

Use Cases and Deployment Scope

We have implemented the case management for managing the customer request. Let's say the different kind of customer requests are coming, right? They're logging in, complaint management and all those. And the complaint assignment and reassignment, all those. And final, the resolution of the complaints has been minus and also along with this incident management.

Pros

Incident management
Customer journey management

Cons

Survey management
The complete contact center solution

Likelihood to Recommend

So best appropriate is for case management and omnichannel. And the less appropriate basically is for the contact center solutions wherever the contact center is, that's less suited into that new cases.

Verified User

Vice-President in Information Technology (1-10 employees)

Vetted Review

12 years of experience

Salesforce Service Cloud Review

Rating: 8 out of 10

Incentivized

November 4, 2025

Use Cases and Deployment Scope

As somebody that helped others implement it? I think the use cases vary, but they all hinge around customer service and having testing one data to best serve the customer, either through email interactions, phone call, interactions, complaints, ticketing testing, support, etcetera, and service cloud mix teams.

Pros

Fundamentally it allows consolidated data. Business units are not fragmented, one user is not isolated from understanding another user's interactions with the same customer. Having that helps them better serve their customer. Having data allows people to report on things escalate. So greater visibility and just gather insights, which are all super helpful.

Cons

I think Service Cloud has been around for 20 plus years, so it has evolved significantly and I'm sure there are lots of room for improvement. Where we as an implementation partner probably don't see a lot of that is because we are solving to a particular client's needs and we're meeting their requirements with those solutions. I think the AI and the agent and agent layer is going to be a big learning for people, not just us as implementers, but our customers as well and making sure they're equipped to support those needs. But as a stable customer service offering

Likelihood to Recommend

I think the one that we see time and time again is where management mid to senior don't have visibility over what their teams are doing and they cannot jump into help when needed. So by being able to bring it into one single solution and have greater visibility, simple things like reports or dashboards allow managers to view at a high level what their team's working on, understanding if they're meeting KPIs, if they're missing any deadlines, etcetera, so that they can intervene, which is super helpful.

Verified User

Director in Sales (10,001+ employees)

Vetted Review

15 years of experience

Salesforce Service Cloud Review

Rating: 9 out of 10

Incentivized

November 4, 2025

Use Cases and Deployment Scope

It's the first time that we're using CRM, so we're using it a lot for cases, ensuring that we were able to resolve the concerns of our passengers real time as much as we could, but basically more on case management and CRM.

Pros

When our passengers submit their refund requests through the web forms, so it'll push automatically to the our team who handles refunds and if needed, we also collaborate through Slack for faster resolution.

Cons

At this point, I'm not seeing anything yet so far based on our experience.

Likelihood to Recommend

I'm managing Connect Center, so I cannot identify at this point if there's any part of our team that will not really probably need it. It's very critical for us at this point. So I'm not seeing anything that's least using Service Cloud. Yeah, I'm not seeing anything yet.

Verified User

Manager in Customer Service (5001-10,000 employees)

Vetted Review

2 years of experience

Salesforce Service Cloud Review

Rating: 8 out of 10

Incentivized

November 3, 2025

Use Cases and Deployment Scope

For us, Service Cloud is handling all of our email and messaging incoming support requests. In a lot of cases it's also handling workflow, so whether it's a process request, billing requests, anything like that that's coming into Service Cloud, usually through email to case or messaging for in-app and web. And then our team is responding and going through the process to help the customer.

Pros

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.

Cons

Round robin, we don't have one. So whereas with Omnichannel you can route a case based on an agent's capacity. So if they've got 10 cases or 20 cases or 30 cases all at one time, omnichannel will let you assign based on that skill, right. But there's no just person A to person B to person C to person D routing, which is pretty common in a lot of service companies where there is no logic behind the routing, it just has to go round and round. So that required a lot of complex coding to get that functionality in place and it should just be there.

Likelihood to Recommend

Probably where you have a number of service teams that all contribute to a knowledge base is one area that's really useful. AI response, it looks like with AgentForce, that's going to be one of our next deployments. So they're AI based on the trust layer is, I like that it has the trust layer because it's already got some built in safeguards around privacy and security controls for AI, which is very important right now. Where it's probably less useful:gain, round robining a very email heavy conversation, so it's not the best email tool. A lot of our team still uses Gmail and logs to the case rather than actually emailing directly out of Salesforce. Email signatures are not great because you can only have plain text email signatures, you can't have HTML.

Verified User

Vice-President (51-200 employees)

Vetted Review

3 years of experience

Salesforce Service Cloud Review

Rating: 10 out of 10

Incentivized

November 3, 2025

Use Cases and Deployment Scope

Supporting of our group supports our larger business customers and by utilizing Service Cloud we can integrate various methods for them to contact us for like email to case and live chat and all these omnichannels. It gives our business users a way to get ahold of us in whatever means they need to contact us.

Pros

Case management is probably our biggest thing. We use it for being able to link cases with customers and accounts.

Cons

There are some plugins that are clunky by Salesforce and it looks like Agentforce will address some of those and so we're looking forward to testing it at the least.

Likelihood to Recommend

Less appropriate would be... because we deal with a lot of PII and so anything whether it's legal or if it's specifics for customers, that would be a con. So we're at this point, obviously every single person in the US is a customer of ours and protecting that data and how they can home mail user can contact us and stay for us to anonymize our information.

Verified User

Analyst in Customer Service (10,001+ employees)

Vetted Review

7 years of experience

Loading Reviews List....

Home
,
Help Desk
,
Salesforce Agentforce Service
,
Reviews and Ratings

Salesforce Service Cloud Review

Rating: 8 out of 10

Incentivized

November 5, 2025

Use Cases and Deployment Scope

Pros

Okay, so in terms of details — when I have an opportunity, I just enter it, and it gives me stage-by-stage information, where each stage is associated with a certain probability. For example, if it’s in the opportunity stage, it might be 50%, and if it’s still in the lead stage, it’s around 20%. So it automatically calculates the expected revenue for that opportunity, which is pretty interesting. I don’t have to manually modify or enter any data to understand how much revenue is actually expected from that particular opportunity.

Cons

So when an opportunity is converted into a closed stage, if it’s split across the total duration, that’s very useful — and Salesforce does that. But there are some scenarios where the project is invoiced on a milestone basis. For example, we don’t always invoice a 12-month, $120K project as $10,000 every month. In some contracts with our customers, they might say, “Once you finish this particular module, invoice $25,000,” and then, “Once you finish the rest of the modules, invoice $75,000.” There’s currently no way for me to track that kind of milestone-based customization in Salesforce. That would be an amazing feature if they could bring it to the table.
For example, we don’t always invoice a 12-month, $120K project as $10,000 every month. In some contracts with our customers, they might say, “Once you finish this particular module, invoice $25,000,” and then, “Once you finish the rest of the modules, invoice $75,000.”
There’s currently no way for me to track that kind of milestone-based customization in Salesforce. That would be an amazing feature if they could bring it to the table.

Likelihood to Recommend

Verified User

Director in Information Technology (1001-5000 employees)

Vetted Review

2 years of experience