A customer emails on Monday, starts a chat on Tuesday and fills in a web form on Wednesday about the same problem. Salesforce Service Cloud can turn each of those into a case that your team works from one console.
This guide covers what Service Cloud does, which features sit in which edition, what each edition costs per user and which teams it fits. It also explains the rename, because two Salesforce sources now use two different names for the same product.
We’re HyphenX Solutions, a Salesforce consulting firm. The prices, limits and features below come from Salesforce’s own pages, checked on October 9, 2026, and the arithmetic and fit guidance are ours. Where Salesforce’s pages disagree with each other, we say so.
TL;DR
What Service Cloud Does Under Either Name
Service Cloud is Salesforce’s customer service platform. It creates cases from support emails and web forms, routes them to the right people and gives agents one console to resolve them. Salesforce Help now calls it Agentforce Service, while Salesforce’s pricing page still says Service Cloud.
Pricing That Starts at $25 per User
As of October 2026, Service Cloud editions run from Starter Suite at $25 to Max at $550 per user per month. Routing and entitlements start at Pro Suite, Slack swarming at Core and a Full Sandbox at Advanced. Messaging, AI and other add-ons raise the real annual cost.
Who Should Buy and Where to Start
Service Cloud fits teams with steady case volume across email, web and messaging. A team with a handful of requests a week may not need it. Start with the 30-day free trial, match your needs to the edition table, then decide whether to launch alone or with help.
What Salesforce Service Cloud Is, and What Salesforce Now Calls It
Salesforce Service Cloud is a platform for resolving customer issues, which Salesforce calls cases or tickets. Agents work those cases in one place, the Service Console.
Salesforce names service representatives, support managers and field technicians as the people who use it. Salesforce’s own guide describes the core job as simplifying how customer issues, often called cases or tickets, get resolved. The name covers a set of tools, from case management and routing to AI agents, and your edition decides which ones you get.
Where you see it | What it calls the product |
|---|---|
Salesforce Help, “What Is Agentforce Service?” | Agentforce Service (formerly Service Cloud) |
Salesforce’s pricing page and product page | Service Cloud |
Salesforce’s Service Cloud guide | Answers “Did Service Cloud recently change its name?” with a yes and refers to “the new Service Cloud brand name” |
Salesforce’s September 3, 2026 edition announcement | Agentforce Service Editions |
This page uses “Service Cloud” because Salesforce’s pricing and product pages do. When Salesforce Help says Agentforce Service, it refers to the same product. We found no rename date on Salesforce’s pages, so check the live pages before you put either name in a contract.
Why Support Teams Adopt Service Cloud
Service Cloud gives every request a case, a customizable record that holds the details of the request. Four jobs show the difference a shared record makes.
- Channels. Before: email, web forms and chat sit in separate tools. After: email and web-form requests turn into cases automatically, and messaging brings chat into the same product.
- Routing and answers. Before: reps choose what to work on and hunt for answers. After: work goes to the right queue, rep or skill set, and a Salesforce Knowledge base holds the articles reps answer from.
- Service promises. Before: response targets live in a spreadsheet. After: entitlements record the support a customer is owed, and milestones track the steps required to deliver it.
- Ownership. Before: no one can say who is handling a request. After: cases are assigned to queues or reps, and escalation rules and queues move stalled work along.
The “before” lines are our illustration of common situations. Salesforce’s own research adds an AI angle: its 2026 survey of 3,075 service professionals reports AI agent adoption in customer service rising from 39% to 66% between 2025 and 2026, and 70% of adopters say they see measurable value within 60 days. It covers customer service teams in general, so read it as context for the AI layer and as Salesforce’s own view.
How a Customer Request Moves Through Service Cloud
A request moves through five stages in Service Cloud: it arrives, becomes a case, gets routed, gets resolved and gets tracked against a service promise.
- A request arrives. Email-to-Case creates a case when a customer writes to your support address, and Web-to-Case does the same for a web form. Messaging for In-App and Web handles chat, and it replaced Salesforce’s legacy chat products.
- A case is created. Cases are records that hold the details of each request, and you can customize them to fit your process. This is where Service Cloud case management starts.
- Work is routed. Omni-Channel sends work items to queues, support reps and skills. Our support automation page covers the routing and follow-up side for teams that want it automated.
- An agent resolves it. Agents work in the Service Console, a standard Lightning console app, and answer from Knowledge articles. On Core and above, Slack swarming lets a rep pull in other experts.
- Promises are tracked. Entitlements define the support a customer is owed, such as phone support or web support, and milestones mark the required steps. Case escalation rules and queues come with every edition.
This path is our summary of Salesforce’s documented features, and your edition decides how much of it you can run, since routing and entitlements start at Pro Suite and swarming starts at Core.
On our own Service Cloud rollouts we test each component in a sandbox before moving anything toward production, and the pricing table later in this guide shows which editions include which sandbox.
Salesforce Service Cloud Features From Basic to Advanced
Salesforce Service Cloud features stack in four levels, from capturing a request to running AI agents. Each card shows what the level does and which edition includes it, and the examples are ours.
Start Here: Capture and Track Every Request
- What it adds: Cases hold each request, which is Service Cloud case management at its simplest. Email-to-Case and Web-to-Case create them automatically, and the Service Console gives agents one workspace.
- Example: A customer emails the support address, a case lands in a queue and an agent replies from the console.
- Edition gate: All five editions include case management, the console, Knowledge, web and email case capture, and escalation rules and queues.
- Watch for: Starter Suite covers only this level in the edition table, so every later level needs Pro Suite or above.
Next: Route Work and Answer Faster
- What it adds: Omni-Channel routes work to queues, reps and skills, and Knowledge holds the articles agents answer from.
- Example: A billing question goes to a billing queue, and a rep with the matching skill picks it up.
- Edition gate: Omni-Channel Routing starts at Pro Suite and runs through Max.
- Watch for: By default, internal users with Read permission can read published articles, and doing more takes the Knowledge User license.
Then: Keep Service Promises and Add Self-Service
- What it adds: Entitlements and the case milestone tracker record what customers are owed. Slack swarming brings other experts into a case, and Flow Builder automates routine steps. Experience Cloud portals support self-service.
- Example: A premium customer’s case carries a first-response milestone, and an escalation rule alerts a manager if it slips.
- Edition gate: Entitlements and milestones start at Pro Suite. Swarming, advanced case management and Help Center start at Core. Pro Suite allows 5 flows per org, and Core and above allow unlimited flows.
- Watch for: Count the automations you want before you pick Pro Suite, because it caps flows at 5 per org.
Finally: Messaging, Digital Channels and AI Agents
- What it adds: Messaging, digital channels and workforce and quality management extend support beyond email and web forms. Agentforce for Service adds AI agents, covered after the pricing table.
- Example: An AI agent resolves a common request, such as an order-status question, without a rep.
- Edition gate: Digital Channels and Workforce and Quality Management are available for purchase in Core and Advanced, with Web Chat included in Advanced, and included in Max. Agentforce for Service follows the same purchase pattern, with limited credits in Max.
- Watch for: Enhanced Messaging adds $75 per user per month in Core and Advanced, and the table has no plain Messaging row, so ask Salesforce which edition includes Messaging for In-App and Web.
Each level adds setup work, and from level two on it can add edition or add-on cost. The next section shows exactly where each feature begins.
Field Service is a separate product, which Salesforce Help calls Agentforce Field Service and Operations, and Salesforce’s Field Service page says it requires at least one Service Cloud user license.
Salesforce Service Cloud Pricing by Edition and What Each One Includes
As of October 2026, list prices run from $25 to $550 per user per month, depending on edition. Read down your must-have features, then across to the first edition that says Yes.
Feature | Starter Suite | Pro Suite | Core | Advanced | Max |
|---|---|---|---|---|---|
Price per user per month | $25 | $100 | $195 | $395 | $550 |
Billing | Monthly or annual | Annual, contract required | Annual | Annual | Annual |
Case management, Service Console, Knowledge, web and email case capture, escalation rules and queues | Yes | Yes | Yes | Yes | Yes |
Omni-Channel Routing | No | Yes | Yes | Yes | Yes |
Service contracts and entitlements | No | Yes | Yes | Yes | Yes |
Case milestone tracker | No | Yes | Yes | Yes | Yes |
Slack swarming | No | No | Yes | Yes | Yes |
Advanced case management | No | No | Yes | Yes | Yes |
Help Center | No | No | Yes | Yes | Yes |
Flow Builder | No | 5 flows per org | Unlimited | Unlimited | Unlimited |
Web Services API | No | $25 add-on | Yes | Yes | Yes |
Developer Sandbox | No | Yes | Yes | Yes | Yes |
Developer Pro Sandbox | No | For purchase | For purchase | Yes | Yes |
Partial Sandbox | No | No | 1 per org | 1 per org | 1 per org |
Full Sandbox | No | No | No | Yes | Yes |
Digital Channels | No | No | For purchase | Web Chat included, more for purchase | Yes |
Enhanced Messaging | No | No | $75 add-on | $75 add-on | Yes |
Agentforce for Service | No | No | For purchase | For purchase | Yes, limited credits |
Workforce and Quality Management | No | No | For purchase | For purchase | Yes |
We read this table cell by cell from Salesforce’s pricing page on October 9, 2026. Salesforce labels the Starter Suite and Pro Suite prices as starting prices with transaction fees, and a “No” in the table means the page marks the feature Not included. The page’s own FAQ still lists older edition names, so rely on the price cards and confirm edge cases, such as Flow Builder in Starter Suite, with Salesforce.
Salesforce announced Core, Advanced and Max on September 3, 2026 and says pricing on legacy editions is unchanged. Salesforce’s pricing page describes Core as the essential service tools, Advanced as adding AI-powered channels and protected data, and Max as the complete service platform. Starter Suite and Pro Suite are CRM suites with sales, service and marketing tools, so their price covers more than service.
Agentforce for Service: What It Adds and How Salesforce Bills It
Agentforce for Service is the AI layer of Service Cloud, and it appears as its own row in the pricing table above. It adds AI agents that handle support requests alongside your human reps, and Salesforce’s default Agentforce Service Agent template creates an agent designed to resolve common support cases and requests.
- Flex Credits: $500 per 100,000 credits. An Agentforce action uses 20 credits ($0.10), and Salesforce says usage types and multipliers differ for Agentforce Voice actions.
- Conversations: $2 per conversation. At the Flex Credit rate, the same $2 would buy 20 actions.
- Per-user add-on: $125 per user per month, listed for Sales, Service and Field Service.
- Included credits: Salesforce’s September 3 announcement lists 500,000 Flex Credits in Core, 1 million in Advanced and 2.75 million in Max.
- Included agents: The same announcement lists the Agentforce Help Agent as included in Advanced and Max, and Service Rep Assistant as included in Max.
- Break-even: The pages we read don’t say how many actions a conversation contains, so price a real sample of your requests under both models before you commit.
Salesforce’s Agentforce pricing page says Flex Credits and conversations can’t be used in the same org, so pick a billing model before you build. Because Voice actions use different multipliers, price any voice requests as their own line instead of assuming the 20-credit rate.
The pricing table above lists Agentforce for Service as available for purchase in Core and Advanced, while the September 3 announcement lists included Flex Credits for both. Only the Max card states a time basis, per org per year, so ask Salesforce what the included credits cover and over what period. Our Agentforce services cover the build side.
What Service Cloud Costs a 10-Agent Team: Licenses, Add-Ons and Setup
Salesforce Service Cloud pricing starts with the per-user license, and add-ons change the total. This is the arithmetic for 10 agents at list price, with each add-on priced on its own.
Line item | Math for 10 users | Cost |
|---|---|---|
Licenses | ||
Starter Suite | 10 x $25 = $250 a month, x 12 | $3,000 a year ($300 per agent) |
Pro Suite | 10 x $100 = $1,000 a month, x 12 | $12,000 a year ($1,200 per agent) |
Core | 10 x $195 = $1,950 a month, x 12 | $23,400 a year ($2,340 per agent) |
Advanced | 10 x $395 = $3,950 a month, x 12 | $47,400 a year ($4,740 per agent) |
Max | 10 x $550 = $5,500 a month, x 12 | $66,000 a year ($6,600 per agent) |
Add-ons, if all 10 users need each one | ||
Enhanced Messaging on Core or Advanced | 10 x $75 x 12 | $9,000 a year |
Web Services API on Pro Suite | 10 x $25 x 12 | $3,000 a year |
Agentforce per-user add-on | 10 x $125 x 12 | $15,000 a year |
Flex Credits for 5,000 actions | 5,000 x 20 credits = 100,000 credits | $500 for the credits |
1,000 conversations | 1,000 x $2 | $2,000 for the conversations |
Two sample stacks: Pro Suite plus the Web Services API comes to $12,000 + $3,000 = $15,000 a year, and Core plus Enhanced Messaging comes to $23,400 + $9,000 = $32,400. These figures leave out Premier support, which Salesforce’s pricing page describes in two conflicting ways, Contact Center and Field Service, which Salesforce prices on separate pages, and taxes and discounts. Included Flex Credits in Core, Advanced and Max may cover some AI usage, so confirm what they cover before you price the credit lines above.
On services, our implementation cost guide gives an illustrative band of $15,000 to $40,000 for a focused one-cloud rollout: fewer than 75 users, clean data, 0 to 2 simple integrations and limited custom code, over 4 to 10 weeks. The guide’s model excludes Salesforce subscription charges, which it treats as separate recurring costs, and it labels these figures planning bands. The band describes any single-cloud rollout, so it is a rough reference for Service Cloud, and a quote will say more.
Who Service Cloud Fits, and Who May Not Need It
Service Cloud fits teams that handle steady request volume across several channels and want shared records, routing and tracked service promises. It fits less well when volume is small and one person owns the inbox.
- Volume. Good fit: requests arrive daily and more than one person works them. Poor fit: a few requests a week land with one person, and a shared inbox keeps up.
- Channels. Good fit: email, web forms and messaging all need one queue and one history. Poor fit: one channel carries everything and already works.
- Process. Good fit: you want escalation rules, service entitlements and shared knowledge articles. Poor fit: no one owns the support process yet, so there is nothing to configure.
- Billing. Good fit: a per-seat contract fits your budget, annual from Pro Suite. Poor fit: you need month-to-month flexibility beyond Starter Suite.
- AI. Good fit: you plan to add Agentforce for Service on Core or above. Poor fit: you need Agentforce for Service on Starter Suite or Pro Suite, where the pricing table lists it as not included.
- Growth. Good fit: you expect more channels, more agents or AI agents as you grow. Poor fit: volume and channels are stable and small.
The fit lines are our judgment, built on Salesforce’s published limits. Salesforce’s guide says companies that handle thousands of inquiries a day use it, and it lists five use cases that match a good fit: high-volume case management, omnichannel customer support, self-service and AI agents, field service operations and issue resolution before customers report problems.
Salesforce says Service Cloud is used by businesses of all sizes, and we found no minimum seat count on its pages. The Starter Suite card mentions built-in AI, which the Agentforce for Service row doesn’t list for Starter Suite, so ask Salesforce what it covers.
Service Cloud vs Sales Cloud: Do You Need Both?
Sales Cloud helps a team sell, and Service Cloud helps a team serve. Salesforce’s guide says both are built on the same core Salesforce platform, and a Salesforce Help article says the clouds can be used separately and independently.
Service Cloud | Sales Cloud | |
|---|---|---|
Goal (our paraphrase of Salesforce’s guide) | Simplify customer service and resolve issues before they become problems | Improve sales efforts, capture leads and close more deals |
Core tools | Case management, routing, Knowledge, entitlements and AI agents | Lead management, opportunity tracking, forecasting and sales process automation |
Fits when (our judgment) | Your team’s daily work is answering, assigning, tracking and closing requests | Your team’s daily work is working leads and opportunities |
If both teams share customers, connect the clouds to share data such as contacts, leads or orders, or start on Starter Suite or Pro Suite, which bundle sales, service and marketing tools in one edition.
Settle which teams share customers before you buy seats, because that decides whether you need one suite or two clouds.
How to Start: Free Trial, Fixed-Scope Launch, Full Rollout or Ongoing Care
Start with the free trial to test your cases, then choose a launch path by how many channels, integrations and records you need to move.
Free Trial: Test With Your Own Requests
- Fits when: You want to test cases yourself with a sample of real requests before you spend anything.
- What it covers: Salesforce’s 30-day trial, with no credit card and no installations.
- Watch for: The pricing page shows trial buttons on four editions and a contact button on Max, and it doesn’t say which edition the 30-day trial covers, so confirm that before you test a feature.
Quickstart Package: A Fixed-Scope First Launch
- Fits when: It’s your first rollout. Standard suits up to 25 users on Sales Cloud or Service Cloud, and Extended suits teams that launch sales and service together.
- What it covers: The HyphenX Quickstart package has two tiers. Standard runs four to six weeks with standard integrations, data migration, user training and two weeks of post-launch support, and Extended runs six to eight weeks with advanced integrations, custom development, an Experience Cloud portal and four weeks of support.
- Watch for: The Quickstart service follows fixed-scope, fixed-price models, but the page publishes no price, so ask for the quote and what it assumes.
Full Rollout: Expert-Led From Plan to Go-Live
- Fits when: You have many channels, integrations or records to move, and you want experts to plan and build the rollout.
- What it covers: Our Service Cloud implementation help tests components in a sandbox, phases the rollout and supports you after go-live as a retainer or a handover.
- Watch for: Ask which edition and add-ons the scope assumes, because the license is a separate cost.
Managed Services: Ongoing Care After Go-Live
- Fits when: You’re live, and routing, automation and knowledge upkeep keep piling up faster than your admins can clear them.
- What it covers: Our managed services cover omnichannel routing, case lifecycle automation and knowledge management.
- Watch for: Agree the scope and the hand-off at the start, so your admins know what stays with them.
Whatever you choose, get the scope in writing. We work in fixed-scope, time-and-materials, phased, managed and hybrid models, so ask which one the scope assumes.
Moving from a legacy CRM, an on-premise system or another Salesforce org adds a data step, and we map cases, entitlements, knowledge content, Omni-Channel routing and service configurations before they move.
Seven Service Cloud Mistakes to Avoid Before You Buy or Build
Each mistake below traces back to a rule or limit on Salesforce’s own pages, so you can verify the fix yourself.
- Budgeting from an older price list. The edition lineup changed in September 2026, so quote from the live pricing cards, not from a saved copy or an older list that still names the previous editions.
- Expecting routing in Starter Suite. Omni-Channel Routing, entitlements and the milestone tracker begin at Pro Suite, so a team that needs routing budgets from $100 per user per month.
- Skipping the Knowledge User license. Reps can read published articles by default, but doing more than read takes the license, so count those seats before launch.
- Mixing AI billing models. Flex Credits and conversations can’t share an org, so test both on a real sample of requests and choose one before you design your agents.
- Planning around legacy chat. Salesforce ended support for its legacy chat products on February 14, 2026, so any chat plan built on them needs a rebuild on Messaging for In-App and Web.
- Looking for the Setup Assistant in a new org. Salesforce’s Service Setup Assistant, which set up queues, macros and flows, isn’t available in orgs created in Spring ’26 or later, so plan your first setup with Salesforce Go in mind.
- Assuming every edition has the sandbox you need. The pricing table lists no sandbox in Starter Suite, a Developer Sandbox from Pro Suite, a Partial Sandbox from Core and a Full Sandbox from Advanced, so on Starter Suite, ask Salesforce how you’ll test changes.
Several of these surface after launch. Our guide to when to move from an implementation partner to managed services covers who should own the org afterward.
Your Service Cloud Evaluation Checklist
Work through these 11 checks in sequence and test your edition, budget and rollout choices against your own numbers.
Fit
☐ Count monthly requests by channel: email, web form and messaging
☐ Name who works cases and who approves escalations
Edition and features
☐ Mark every feature you need on the edition table, including routing, entitlements, swarming and sandboxes
☐ Decide whether you need AI agents, and which billing model: credits, conversations or per-user
☐ Count Knowledge User licenses for reps who need to do more than read articles
Budget
☐ Multiply seats by price by 12 for two editions, then add messaging and AI
☐ Recheck prices on Salesforce’s pricing page the day you decide
Rollout
☐ Start the 30-day trial with a real sample of your cases
☐ List the systems that must connect, such as billing or order data, because integration work shapes scope and cost
☐ Plan how existing cases and knowledge articles will move, including data migration
☐ Pick a test environment, a launch owner and a named owner for life after launch
Revisit the list whenever Salesforce changes its edition table or the product name.
Case Study: Connecting Outside Data to Salesforce Without Duplicates
B2B SaaS Client: Unifying Three Prospecting Tools in One Salesforce Action
This project sits outside Service Cloud, since we have no published Service Cloud case study, and it shows how we handle the connected-data work behind integration and migration. A B2B SaaS company ran outbound prospecting through Apollo, Lusha and Hunter, and none of the three connected to Salesforce, so reps copied contact data into the CRM by hand. HyphenX linked the providers through APIs behind a single-click identify-and-insert action on Lead, Contact and Account records, with real-time deduplication, source attribution and Hunter email verification before any record was written, over five phases from discovery to ongoing tuning.
Key takeaway: Connecting outside data sources to Salesforce works best when deduplication, source-of-truth rules and email verification are built in before records are written.
Read the full case study: From Swivel-Chair Prospecting to Single-Click Pipeline. Explore more case studies.
Salesforce Service Cloud FAQs
What is Salesforce Service Cloud?
Salesforce Service Cloud is a customer service platform that creates cases from support emails and web forms, adds messaging conversations and gives agents one console to resolve them. Salesforce’s guide describes its core function as simplifying how customer issues, often called cases or tickets, get resolved.
Is Service Cloud now called Agentforce Service?
Salesforce Help says Service Cloud is now Agentforce Service, but Salesforce’s pricing and product pages still use Service Cloud. We found no rename date on Salesforce’s pages. Both names point to the same product, so check Salesforce’s live pages before you put either name in a contract.
How much does Service Cloud cost per user in 2026?
As of October 2026, Salesforce lists Starter Suite at $25, Pro Suite at $100, Core at $195, Advanced at $395 and Max at $550 per user per month. Salesforce labels the first two as starting prices with transaction fees. Starter Suite bills monthly or annually, the rest bill annually, and Pro Suite requires a contract.
What happened to the older Service Cloud editions?
On September 3, 2026, Salesforce announced new Core, Advanced and Max editions and said pricing on legacy editions is unchanged. It also says existing Agentforce 1 Edition customers can upgrade to Max at no extra cost. Salesforce describes no one-for-one mapping, so confirm what your own plan maps to.
Is there a free trial of Service Cloud?
Yes. Salesforce’s pricing page lists a free 30-day trial with no credit card and no installations, and it doesn’t say which edition the trial covers. Max shows a contact button in place of a trial button, so confirm with Salesforce which features the trial includes.
Which edition includes Omni-Channel routing and entitlements?
Pro Suite and every edition above it. Starter Suite includes case management, the Service Console and Knowledge, but not Omni-Channel Routing, service contracts and entitlements or the case milestone tracker. Slack swarming starts at Core, per Salesforce’s pricing table as read on October 9, 2026.
What are the main Service Cloud features?
Core features include case management, Email-to-Case and Web-to-Case, the Service Console, Knowledge, Omni-Channel routing, entitlements and milestones, Flow automation and swarming. Newer layers add messaging, digital channels and Agentforce for Service. Your edition decides which of these come included, and some cost extra.
What is the difference between Sales Cloud and Service Cloud?
Per Salesforce’s guide, Service Cloud aims to simplify customer service and resolve issues before they become problems, for service reps, support managers and field technicians. Sales Cloud aims to improve sales efforts, capture leads and close deals, with lead management, opportunity tracking and forecasting. Both are built on the same core Salesforce platform.
Do I need Sales Cloud to use Service Cloud?
No. A Salesforce Help article says the clouds can be used separately and independently, and you can connect them to share data such as contacts, leads or orders. Starter Suite and Pro Suite also bundle sales, service and marketing tools in a single edition.
How much does Agentforce for Service cost on top of the license?
Salesforce lists three models: Flex Credits at $500 per 100,000 credits, with 20 credits per action ($0.10), $2 per conversation, or a $125 per user per month add-on. Flex Credits and conversations can’t be used in the same org, so pick one model before you build.
Are digital channels and field service included?
Max includes Digital Channels and Workforce and Quality Management, and Core and Advanced sell them separately, with Web Chat included in Advanced. Enhanced Messaging adds $75 per user per month in Core and Advanced. Field Service is a separate product that requires at least one Service Cloud user license.
Is Service Cloud a fit for a small business?
Salesforce says Service Cloud is used by businesses of all sizes, and we found no minimum seat count on its pages. Small teams can start on Starter Suite ($25) or Pro Suite ($100). Routing and entitlements begin at Pro Suite, so check that before you choose.
Do support reps need a Knowledge license?
Not to read. By default, all internal users with Read permission can read published articles. Salesforce Help says support reps need the Knowledge User license to do more than read articles, so count those seats before launch and budget for them.
How long does a Service Cloud implementation take?
It depends on scope. Our Quickstart Standard supports Sales Cloud or Service Cloud for up to 25 users and runs four to six weeks, and Extended combines both clouds in six to eight weeks. Our cost guide puts a focused rollout at 4 to 10 weeks, and more channels, integrations and data stretch it.
Can I pay monthly, and how long is the contract?
Starter Suite bills monthly or annually. Pro Suite, Core, Advanced and Max bill annually, and Pro Suite requires a contract. Salesforce says most of its products use annual contracts but terms vary, so confirm renewal, seat changes and add-on terms in your order form.
