Service Cloud implementation · CloudX
Service Cloud implementation: customer service on Salesforce, from WhatsApp to the right agent
CloudX is an Israeli consultancy that implements Salesforce Service Cloud, Salesforce's customer service platform. We build case management across channels, Omni-Channel routing to agents, WhatsApp inside Salesforce, a knowledge base, SLAs and customer support portals. In production at our clients, a WhatsApp conversation first reaches an Agentforce agent, and when a person is needed it moves through Omni-Channel to a human agent, with the full conversation and the customer record in front of them. We work with technology companies, service organizations and nonprofits.
What Service Cloud is and what it covers
Service Cloud is Salesforce's customer service product. It manages a request from the moment it arrives until it is resolved: cases, channels such as email, web forms, chat and WhatsApp, routing to agents, a knowledge base, service commitments and reporting.
Its main advantage is that service sits on the same data as sales. The agent sees the customer, the contract and the history, and the account executive sees open cases before a renewal call.
What Service Cloud includes
| Component | What it does |
|---|---|
| Cases | A request record with status, priority, owner and full history |
| Email-to-Case and Web-to-Case | Automatic case creation from email or a website form |
| Omni-Channel | Routes work to queues and agents by availability, capacity and, where configured, skills |
| Messaging | Messaging channels, including WhatsApp and web chat, inside Salesforce |
| Knowledge | Knowledge articles for agents, the portal and AI agents |
| Entitlements and Milestones | Service commitments and response times by customer or contract |
| Service Console | An agent workspace with the case, the customer and knowledge in one place |
Some capabilities, such as messaging channels, voice and AI, depend on the edition and on additional licensing. We map that against the need before choosing.
How organizations in Israel use Service Cloud
- SaaS and technology companies: support for business customers, with SLAs by contract, a support portal and a knowledge base.
- Service organizations working on WhatsApp: customers in Israel prefer WhatsApp, and the organization wants those conversations inside the system, with routing and reporting.
- Nonprofits and welfare organizations: referral and inquiry intake, an intake interview, handling-time tracking and a move to active service.
- Small service teams: moving from a shared mailbox to a process they can measure.
What CloudX builds on Service Cloud
Case management and service processes
We define case types, statuses, queues and assignment rules that fit your team. We build automatic case creation from email and forms, reopening when a customer replies, merging duplicate cases and Slack alerts for the team. Every process gets fault handling, so no case is lost along the way.
WhatsApp in Salesforce and Omni-Channel routing
WhatsApp is the main service channel for many organizations in Israel. We connect it to Salesforce through Service Cloud messaging channels, set up Omni-Channel routing to queues and agents, and build tools to reroute a conversation stuck with an agent who went offline. For organizations moving from Salesforce's previous messaging setup to the new one, we run the migration with a step-by-step guide and preserve conversation history.
Knowledge base
Knowledge is the foundation of consistent service. We build the article structure, a writing and approval process, display inside the case and in the portal, and permissions by audience. A well-organized knowledge base is also what an AI agent needs to answer correctly.
SLAs and service commitments
With Entitlements and Milestones we define response and resolution times by customer, contract or priority. We build warnings before a breach, escalation to a manager and SLA compliance reports. For nonprofits we have also built a dedicated SLA object that tracks handling time from referral to the start of service.
The AI layer: Agentforce in customer service
The most common use of AI in service is an agent on first contact. In production at our clients, a WhatsApp conversation reaches an Agentforce agent, the agent handles what is in its scope, and when the conversation needs a person a transfer action returns it to Omni-Channel, which routes it to a human queue. The human agent gets the whole conversation and the customer record, and the customer does not start over.
We have also built an Agentforce agent that answers from Knowledge articles, including information held in custom fields and not only in the article body. Our rule: start from the process and the knowledge, then build the agent.
Integrations
- Telephony: connecting a phone system or telephony provider to Service Cloud, so a call opens on the customer record.
- ERP and billing: order status, invoices and balance for the agent handling the case.
- Slack: alerts on urgent cases and SLA breaches.
- A previous help desk: migrating case history, correspondence and files into Salesforce.
- Integration platforms: for complex connections we also work with Workato.
Customer support portal
Many customers prefer to open a case and find an answer on their own. A support portal built on Experience Cloud connects directly to Service Cloud: the customer opens a case, follows its status and reads knowledge articles, and the agent works on the same record.
Adoption: how agents work in the system
Service agents work fast, so their screen has to be simple. We build a console by role, cut fields down, add response templates and surface relevant knowledge inside the case. Service managers get reports on workload, handling times and who accepted or declined each request.
How an implementation runs
- Map the service process: channels, case types, teams, SLAs and escalation paths.
- Design: queues, routing, knowledge structure, permissions and reports.
- Build in a sandbox: channels, Omni-Channel, automation and components.
- Data migration: case history, correspondence and files from the previous system.
- Acceptance testing: scenarios for every channel and role.
- Go-live: by channel or team, with close support in the first days.
- AI layer and ongoing support: an Agentforce agent once the foundation is stable, and improvements driven by the data. If you already run Service Cloud and want it to work better, see improving and supporting an existing Salesforce org.
Choosing a Service Cloud partner: what to ask
- Have they built WhatsApp and Omni-Channel in production? Messaging channels and routing are where most implementations get stuck.
- How do they design the handoff to a human? An AI agent is only as good as its transfer to a person, with the full conversation and context.
- What do they do with history? A returning customer expects the agent to see what happened before, including in the previous system.
- How do they measure? Response times, workload per agent and SLA compliance should be defined before the build.
- Who owns the system after go-live? Queues, templates and knowledge articles change constantly, and someone needs to know them.
At CloudX, the answers to these questions go into the design document during mapping.
What drives cost
- Licenses: number of agents and edition, plus channels and AI features that may require additional licensing.
- Number of channels: email, forms, WhatsApp, chat and telephony, each with its own setup and testing.
- Routing and SLA complexity: how many queues, skills and service levels.
- History migration: how many cases, messages and files move over.
- Portal and AI agent: each is a phase of its own.
Service Cloud and the other Salesforce clouds
Service Cloud works best when it shares data with sales in Sales Cloud, and when customers come in through a portal on Experience Cloud. Nonprofits that manage inquiries and referrals will find more on the Salesforce for nonprofits page, and the full picture is on the Salesforce implementation page.
Want customer service that starts on WhatsApp and reaches the right agent with the full picture? Book a call and we will map your service process together.
Work we have done
Customer service organization · In production
WhatsApp to Agentforce, then to a human agent
The service team answered customers on WhatsApp, but with no agent on first contact. We built the full path inside Salesforce: a Messaging Channel Flow routes each incoming conversation to an Agentforce agent, the agent handles what is in its scope, and when the conversation needs a person, a transfer action returns it to Omni-Channel, which routes it to a human queue. The human agent picks it up with the whole conversation and the customer record, instead of asking the customer to start over. WhatsApp now runs in the same Salesforce org, with the same queues and reports, as every other service channel.
Customer service team · In production
WhatsApp migration to the new messaging setup, with routing fixes
The organization needed to move its WhatsApp number to Salesforce's new messaging setup without losing history, and conversations transferred to an agent who had gone offline were getting stuck. We wrote a step-by-step migration guide, run in a live session with the client, and obtained written confirmation from Salesforce support that conversation history is preserved. We built ways to reroute a stuck conversation, and an AgentWork report showing who accepted and who declined each request. Service managers now see the real workload split and can reroute a stuck conversation.
Software company · In production
Support portal and knowledge base on Service Cloud
The company wanted customers to reach support and knowledge content through a portal, with cases managed against service commitments. We adapted the case processes in Service Cloud, built the display of Knowledge content in the portal, and set up case creation and guest user permissions. We worked on Entitlements and Milestones, Slack case alerts and processes for reopening and merging cases. Customers find answers and open cases in the portal, and the team works against defined response times.
Organization with a professional knowledge base · In production
An Agentforce agent that answers from the knowledge base
The organization keeps its professional knowledge in Salesforce Knowledge articles, and an important part of it sits in custom fields and structured content, not only in the article body. We set up an Agentforce Data Library based on Knowledge, connected it to the agent, and tuned the knowledge source so information in the custom fields is available to answers too. We tested the agent against articles with structured content to confirm each answer rests on the right article and field. The team now gets answers from the organization's own knowledge instead of searching by hand.
Customer service organization · In production
Migrating service history from a previous help desk
The organization moved to Service Cloud and needed to bring its service history along, exported from the previous system as JSON files. We built a Python script that converts the exports into import files, and mapped tickets to Case, notes to CaseComment, correspondence to EmailMessage and files to ContentVersion, linked to their records. The conversion is documented so it can be rerun in a controlled way. Agents now open a case and see the customer's history from the previous system alongside it.
Rehabilitation nonprofit · In production
Referral intake, intake interview and SLA, with AI document reading
The organization needed to connect the referral, the intake interview and the move to active service, with consistent statuses and tracking of handling times. We built referral screens that show fields by referral source, an intake interview process that updates the record, automation that converts a referral into a service recipient, and an SLA object for tracking. Alongside it, AI reads PDF service documents into Salesforce, handling duplicates and hidden whitespace in ID numbers. The team now works one process from referral to service.
FAQ
Who implements Salesforce Service Cloud in Israel?
CloudX is an Israeli consultancy that implements Service Cloud: case management, Omni-Channel, WhatsApp inside Salesforce, Knowledge, SLAs and support portals. We also build an Agentforce agent on first contact, with handoff to a human agent. We work with technology companies, service organizations and nonprofits.
Can WhatsApp be connected to Salesforce?
Yes. Service Cloud includes messaging channels that support WhatsApp, so conversations arrive in Salesforce, are routed by Omni-Channel to agents and are saved on the customer record. In production at our clients, a WhatsApp conversation first reaches an Agentforce agent and moves to a human when needed. The channel requires suitable licensing and a WhatsApp Business account.
What is Omni-Channel in Salesforce?
Omni-Channel is Service Cloud's routing engine. It distributes cases, conversations and other work to queues and agents by availability and capacity, and by skills where configured. Every request from every channel reaches an available, suitable agent, and service managers see the workload in real time.
How long does a Service Cloud implementation take?
Case management from email and forms for one team can go live within a few weeks. An implementation with several channels, WhatsApp, SLAs, a portal and history migration usually takes a few months. We go live by channel or team, and an AI agent is added once the foundation is stable.
How much does a Service Cloud implementation cost?
Cost depends on the number of channels, routing and SLA complexity, the size of the history migration and whether a portal and an AI agent are in scope. Salesforce licenses are separate, set by the number of agents and the edition, and capabilities such as messaging and AI may require additional licensing. After a mapping call we give an estimate by phase.
What is the difference between Service Cloud and Sales Cloud?
Sales Cloud runs the sale: leads, opportunities, quotes and forecasts. Service Cloud runs service: cases, channels, routing, knowledge and SLAs. Both sit on the same data, so the service agent sees the contract and the account executive sees open cases.
Can we migrate case history from another help desk to Service Cloud?
Yes. We map data from the previous system, convert tickets, notes, correspondence and files into the Salesforce structure, and test the load in a sandbox before production. Agents then see each customer's history from before the move as well.
Can an Agentforce agent replace service agents?
An Agentforce agent handles requests within its defined scope and answers from the organization's knowledge, and when the conversation needs a person it hands it to a human agent with full context. We build it as a first layer that frees agents for requests that need judgment. The prerequisites are a well-organized knowledge base and a clear handoff process.
Does Service Cloud support Hebrew?
Yes. Salesforce supports Hebrew as a user interface language, and Hebrew cases, messages and knowledge articles are stored and searched normally. We build response templates and articles in Hebrew and English, and test custom components in right-to-left layout too.
How do you set up customer service SLAs in Salesforce?
With Entitlements and Milestones you define response and resolution times by customer, contract or priority. We add warnings before a breach, escalation to a manager and SLA compliance reports. When the process does not fit the standard structure, we also build a dedicated tracking object.
Can customers open cases through a portal?
Yes. A support portal on Experience Cloud connects directly to Service Cloud: the customer opens a case, follows its status and reads knowledge articles, and the agent works on the same record. We set permissions so each customer sees only their own organization's cases.
Last updated: