Agentforce Service
Omni-channel routing has transformed case handling and now supports complex field operations
What is our primary use case?
Currently, I work exclusively with Salesforce CRM and have not had the opportunity to work with HubSpot on any projects.
I work with Sales and Service. I have more than five years of experience with Salesforce Service Cloud. I am working with multiple projects that include not only sales or service, but also field service based on project requirements. I am currently working on field service and Health Cloud.
Recently, I worked on a UK project for door repair services. Customers book appointments for household repairs. They use this service with field service in combination for scheduling jobs, maintaining work orders, and managing service-related details. The UK project is primarily a house repair type of project.
Omni-Channel, which is in Salesforce Service Cloud, is useful for client information management from lead to order. It helps with routing to the related user when a case is created. Omni-Channel routing management is a valuable feature in Salesforce Service Cloud.
With the improvement of this service combined with field service, we also have customers who do not want to buy field service but want scheduling. We have other scheduling apps that help achieve client requirements with these cloud features. Previously, a health system used a mobile app for Field Service Lightning for service appointments when sending staff to home visits for patient care tasks.
What is most valuable?
Omni-Channel in Salesforce Service Cloud aids client information management, lead to order setup, and routing management for issues raised. It helps with case routing and problem resolution.
Salesforce Service Cloud helps by creating a knowledge base from Experience Cloud, making it easy for clients to resolve issues using knowledge-related articles.
The mobile service used by health systems highlights Field Service Lightning, although customization to client requirements is challenging.
Automation, order of execution, bulkification, and error monitoring are valuable features.
What needs improvement?
From my experience, we might need queue-based alignment in Omni-Channel routing. Assignment rules should be defined at the flow level. The challenge with SLA creation is evident in escalation rules, which should include a field flagging feature that is lacking in the current setup.
Einstein Bot, linked with Omni-Channel messaging, is complex to define, with a need for all related information in one place, making the process cumbersome. Understanding which bot is associated with specific messaging apps requires manual searching, and this can be improved.
For how long have I used the solution?
I have more than five years of experience with this solution.
What do I think about the stability of the solution?
I have not experienced any stability issues.
What do I think about the scalability of the solution?
I have not experienced any scalability issues with Salesforce Cloud.
How are customer service and support?
I communicate with customers whenever we need more information or face any issues. Recently, because of MFA, bots were unable to perform certain tasks, which led to communication for a quick solution. Customer service has improved significantly for developers, with strong support provided.
Regarding improvements, I believe the customer service experience could be enhanced further.
Which solution did I use previously and why did I switch?
I am not currently evaluating previous solutions as I have other work to complete.
How was the initial setup?
I build the projects, so I am not a customer evaluating the initial setup.
What about the implementation team?
I did not provide feedback on the implementation team as I may potentially be working on future projects.
What was our ROI?
I would rate the ROI at 9 to 9.5. It is a good service.
What's my experience with pricing, setup cost, and licensing?
I do not have knowledge of the setup cost as I do not look into pricing. Once the customer and my team discuss everything, I configure the system, but I do not have an idea about the pricing.
Which other solutions did I evaluate?
I did not have a chance to work in a scenario that would require evaluating alternate solutions.
What other advice do I have?
I am confused about whether Field Service Lightning and Field Service Cloud are different.
Automation, order of execution, bulkification, and error monitoring are features that I found to be valuable. With Salesforce, I have not faced any issues related to these functionalities.
Salesforce Service Cloud helps by creating a knowledge base from Experience Cloud, making client issue resolution easier through knowledge-related articles from the community level.
My overall review rating for this product is 8 out of 10.
AI Assistance Meets Traditional Customer Service—A Winning Combo
SFSC Streamlines Case Management and Automates Customer Journeys
Efficient Automation and Easy Setup with Agentforce
All Case Details in One Place—Faster Support with Flows and Knowledge
The automation for case routing and follow-ups has also reduced a lot of manual work. As a result, my team spends less time on repetitive tasks and more time actually helping customers. Overall, it’s made our support process more consistent and easier to scale as ticket volume grows.
Salesforce Service Cloud Centralized Our Support and Boosted Team Efficiency
The case management workflow is genuinely strong. Being able to set escalation rules, auto-assign tickets based on queue logic, and spot potential SLA breaches before they actually happen has saved us from more than a few embarrassing situations with key accounts.
I also really appreciate the Knowledge Base integration. Reps don’t have to ping each other on Slack asking, “Hey, what’s the process for X?” anymore—they can pull it up directly while they’re working a case. That alone noticeably cut our average handle time in the first couple of months.
The reporting side is better than I expected, too. I was skeptical at first because dashboards can feel bloated in a lot of tools, but once we dialed in the metrics we actually care about, it became genuinely useful for weekly standups instead of being something leadership glances at once a month.
Omni-Channel routing is another feature I didn’t realize I’d rely on so heavily. It’s not perfect, but the fact that it distributes load across agents based on capacity rather than just round-robin has made a real difference in team morale—nobody feels like they’re getting buried while someone else is coasting.
Look, no tool is perfect and this one has its rough edges too.
The learning curve caught us off guard honestly. New agents take a while to find their footing and even experienced ones sometimes dig through menus longer than they should. We ended up putting together our own internal cheat sheets because the out of the box training material doesn't always reflect how your specific setup actually looks.
Pricing is where it gets a little frustrating. It starts feeling reasonable until you realize the features you actually need day to day are sitting behind another add on or a higher tier. Storage, advanced reporting, extra automation capabilities — it all adds up quietly until your renewal conversation becomes a bit of a shock.
The customization thing is a double edged sword. I appreciate that you can bend it to fit your process but that also means someone has to do that bending. We leaned on our admin constantly in the early months and there were a couple of instances where we genuinely had to bring someone external in just to untangle logic that felt like it should have been simpler to set up.
Page load times are something agents complain about more than I'd like. Nothing dramatic, no crashes, just that slight lag when a Lightning page has a lot going on. When you're moving fast through a queue it's the kind of thing that quietly grinds on you over a shift.
And honestly, the irony of getting slow support from a company whose entire product is about support is not lost on our team. Non urgent tickets can sit longer than you'd expect given what the platform costs.
Complaint handling became way more structured. Instead of relying on people to remember where things stood, the case timeline does that work automatically. Our team leads can actually see what's happening across the board without having to chase agents for updates every morning.
The knowledge base piece helped reduce repetitive back and forth too. New hires ramp faster because answers are documented and searchable rather than locked in someone's head.
Overall response times came down and customer satisfaction scores moved in the right direction within the first quarter. It's not a magic fix but having everything in one organized place makes a bigger difference than you'd expect until you've actually experienced it.