What we do
Tools
Industries
Department
How we workLet's talk →
Home/Service Cloud
Service Cloud and your other systems

Salesforce Service Cloud Integration: Where Outside Data Meets a Case, and Where It Leaves

A customer emails about a late delivery. Email-to-Case turns it into a case, Omni-Channel hands it to an agent, and the agent then opens the shipping portal to find out what the customer already knows. Service Cloud runs the case itself well. A Service Cloud integration is about the few moments where that case needs a fact from outside Salesforce, or needs to change something out there.

Where Service Cloud stops

A case opens, and the agent still has to go find out what's happening across billing and inventory.

Stuck on Service Cloud? Let's solve it →

Five places a Service Cloud case touches other systems

Each step names the Salesforce piece involved, and the part that has to be built.

  1. 1

    The case is created

    Email-to-Case, Web-to-Case and Salesforce's messaging channels create cases on their own, so there's nothing to build for those. A portal, an app or a monitoring tool outside Salesforce can create one through the Salesforce REST API on the Case object.

    Watch for: duplicates when a portal and an email report the same problem. Decide which one creates the case and which one adds to it.

  2. 2

    The case is filled in

    Order status, invoice standing and warranty dates live in your ERP, order system or accounting software. Either copy them onto the case or account when it's created, through a Flow callout or an outside service, or show them live with Salesforce Connect, a separately licensed feature that displays outside data as external objects without copying it.

    Watch for: copied data goes stale, and live data needs the other system up whenever an agent looks.

  3. 3

    The case is routed

    Omni-Channel routes by queue or by skills, and an Omni-Channel flow can decide where work goes. All of them can only weigh what's on the record, so account tier, contract value or a past-due flag from another system has to reach a Salesforce field first.

  4. 4

    The agent works it in the console

    A Lightning component on the case page can show order history or tracking pulled from outside, and offer actions such as issuing a credit or sending a replacement that call the other system's API. Phone cases add a softphone through Service Cloud Voice or a vendor's Open CTI app, compared on our Service Cloud telephony page.

  5. 5

    The case closes, and something else has to change

    A refund in accounting, a corrected delivery date in the warehouse system, an article in Salesforce Knowledge that needs fixing. Change Data Capture can publish case changes as events, so an outside service hears about a status change without polling Salesforce.

An industrial manufacturer whose key accounts stopped waiting in line

An industrial manufacturer on Service Cloud, routing cases by queue and skill.

Before

Routing balanced the workload, but it had no way to tell which accounts were at risk.

A major customer's case could wait behind routine ones until someone happened to recognize the name.

After

Account-level signals from outside Salesforce now feed routing, so cases from key or at-risk accounts move up the queue.

Escalations became rarer.

Questions that shape a Service Cloud integration before anyone scopes it

  • Which system owns each fact an agent needs?

    If order status lives in both the order system and the ERP, pick one. Two sources on one case leave agents trusting neither.

  • Should each fact be copied onto the case, or shown live?

    Copies are fast and reportable. Live views are always current. Some fields want one and some the other.

  • Which agent actions have to change another system?

    A credit issued on a case that never reaches accounting is a promise nobody keeps.

  • What should routing know that it doesn't today?

    Tier, contract value, past-due balance. Each one is a Salesforce field to fill before Omni-Channel can use it.

  • Which edition and add-ons does your org have?

    Omni-Channel features, Service Cloud Voice and Salesforce Connect depend on edition and licensing, which changes the cheapest route.

Service Cloud, and connecting it to the rest of the business

What is Salesforce Service Cloud?

Salesforce's customer service product: cases and queues, Omni-Channel routing across email, chat, messaging and phone, a console for agents, and Knowledge for articles. It runs on the same platform as Sales Cloud, so cases sit on the same account and contact records.

What's the difference between Sales Cloud and Service Cloud for a support team?

Sales Cloud is built around opportunities and the pipeline, Service Cloud around cases and the agents who resolve them. Which seats each team needs is covered on our Sales Cloud and Service Cloud page. For integration, both read the same accounts and contacts, so a fact written onto the account once is visible on either side.

How much does Service Cloud cost?

It's priced per user per month and rises by edition, with Omni-Channel capabilities, Service Cloud Voice and AI tools depending on edition and add-ons. Salesforce lists current prices on its pricing page. For an integration budget, also check whether the route you want needs an add-on such as Salesforce Connect.

Can you run Sales Cloud and Service Cloud together and connect outside systems once?

Yes. Both clouds read the same accounts and contacts, so one integration that writes ERP or accounting facts onto the account serves reps and agents alike. Build that layer once, then add the case-side pieces, enrichment on creation and write-back actions, for the service team.

What features does Service Cloud include?

Case management, Email-to-Case and Web-to-Case, Omni-Channel routing, the service console and Knowledge, plus, by edition or add-on, Service Cloud Voice and Einstein features for things like case classification and suggested replies. Inside Salesforce they work together already. Data held in another system is what has to be integrated.

Who builds Salesforce Service Cloud integrations?

A Salesforce admin can set up channels, queues and routing rules. Code that calls your ERP, order or accounting API from a case, and the service that listens for case changes, is developer work. That case-side layer is what n-frames builds: data filled in on creation, routing fields fed from outside, and console actions that change the other system.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.