Salesforce Communications Cloud: Features, Architecture and Implementation Guide
Communications Cloud, now also called Agentforce Communications, is Salesforce's industry cloud for telecom operators. Here is what it actually includes, how the catalog, quoting, ordering and contract pieces fit together, what it leaves to your billing and network systems, and how to decide whether your business needs it.
Key Takeaways
- Salesforce Communications Cloud is an industry cloud for communications service providers. It runs the commercial "middle office": product catalog, quoting, ordering, contracts and customer service for B2C, B2B and wholesale markets.
- Salesforce's Trailhead now calls it Agentforce Communications, while its product and pricing pages still say Communications Cloud. It is a telecom product, not a generic email and SMS messaging tool.
- It connects to billing, charging, inventory and network systems through TM Forum Open APIs and integration tools. Plan those integrations as a core part of the project, not an afterthought.
- It comes as a managed package (the former Vlocity stack) or on the Salesforce platform, built on Agentforce Revenue Management. New projects and migrations should confirm which model fits.
- Smaller operators with simple catalogs can often run well on Sales Cloud with a custom telecom data model. Complex multi-service catalogs and order orchestration are where Communications Cloud earns its cost.
What is Salesforce Communications Cloud? It is Salesforce's industry cloud for telecom and communications service providers (CSPs). Salesforce describes it as a "complete digital BSS suite that's catalog-driven from commerce to cash". It adds a telecom data model, a product catalog, industry quoting, order decomposition and orchestration, contract management and prebuilt processes to Salesforce's sales and service clouds, so operators can sell, deliver and support services on one platform.
We first published this article in 2024. That version mixed Communications Cloud up with multichannel messaging features it does not have, and quoted statistics we could not trace. This version is rebuilt from Salesforce's current product pages, Trailhead modules and developer documentation, checked in October 2026. It is written for COOs, IT directors, sales operations leaders and Salesforce teams at growing and mid-market companies in telecom, broadband and digital services, and for enterprise operators weighing a move.
What Is Salesforce Communications Cloud, and Is It Now Agentforce Communications?
Yes. They are the same product. Trailhead states that "Communications Cloud is now called Agentforce Communications" and warns that you will still see the old name in the application and documentation. Salesforce's product and pricing pages still use "Communications Cloud". Either way, it is the telecom industry cloud, and the name you search for leads to the same thing.
According to Salesforce's Communications Cloud foundations module, the product has prebuilt processes, integrations and data models for business-to-consumer (B2C), business-to-business (B2B) and wholesale markets. It takes a catalog-driven, modular approach aligned with telecom industry standards, and builds on Salesforce's sales and service products. It also handles post-sale changes such as upgrades, downgrades, disconnections, reconnections and moves.
Two names cause confusion:
| Name you may see | What it is |
|---|---|
| Communications Cloud / Agentforce Communications | The telecom industry cloud itself: data model, catalog, quoting, ordering, contracts, consoles and processes |
| Agentforce for Communications | Salesforce's prebuilt AI agents for telecom, announced in February 2026, sold as an add-on |
| Vlocity | The company Salesforce acquired in 2020. Vlocity is now known as Salesforce Industries; the name survives in managed-package namespaces such as vlocity_cmt |
| "Communication Cloud" for email, SMS and push | There is no Salesforce product by that name. Multichannel messaging belongs to Marketing Cloud, which Communications Cloud can work alongside |
Sources: Salesforce Communications Cloud product page and Salesforce's Vlocity acquisition announcement.
Who Is Communications Cloud Built For?
It is built for communications service providers that sell configurable services, such as mobile, broadband, fiber, TV, voice and enterprise connectivity, and need catalog, ordering and service processes to work as one. Salesforce positions it for B2C subscriber businesses, B2B sales to multisite enterprises and governments, and wholesale, inter-carrier transactions.
It fits when you sell bundles, add-ons and promotions across several service lines; orders must be broken down into technical tasks for provisioning systems; enterprise deals involve many sites and subscribers; you want TM Forum-aligned APIs to your BSS and OSS; and you have the budget and team to run an industry cloud.
Think twice when you sell a handful of plans with few rules; orders hand off to one provisioning platform; the main pain is lead tracking, onboarding or billing sync; or you mainly need email and SMS campaigns. Sales Cloud or Service Cloud with a well-designed telecom data model and integrations may be enough.
How Is Salesforce Communications Cloud Architected?
In layers: digital channels on top, industry applications and shared commercial components in the middle, and OmniStudio as the build layer underneath, all on the Salesforce platform. A shared catalog and an industry data model feed quoting, contracts, digital commerce and order management, so every channel sells from the same product definitions.
Web, app, agent console and partner channels
Subscribers and enterprise buyers browse and buy through self-service portals and apps, while agents and sales reps work in prebuilt consoles. Every channel calls the same catalog and pricing logic.
Enterprise Sales Management and Mobile (Multiplay) Subscription Management
Ready-made processes for B2B multisite selling and for B2C subscriber care, covered in Section 05.
Catalog, data model, CPQ, contracts, digital commerce and order management
The Communications industry data model holds offers, bundles, promotions, products, services, resources, rules, pricing and decomposition maps. The shared catalog is the single source of commercial product truth.
OmniStudio
OmniScripts for guided flows, FlexCards for at-a-glance views, and Integration Procedures and Data Mappers for reading and writing data inside and outside Salesforce.
What Are the Core Features of Communications Cloud?
Six components do most of the work: the product catalog, Industries CPQ, Industries Order Management, Contract Lifecycle Management, Digital Commerce and OmniStudio. Together they take an offer from definition to quote, contract, order and fulfilment, while keeping commercial products separate from the technical services that deliver them.
| Component | What it does | Why it matters for a telco |
|---|---|---|
| Shared Catalog and Enterprise Product Catalog (EPC) | One source of commercial product and service data; EPC adds product-lifecycle features such as entity versioning | Launch a bundle or promotion once and sell it in every channel |
| Industries CPQ | Omnichannel configure, price, quote with product rules that show only eligible offers; Document Generation included | Reps and self-service buyers only see valid combinations and prices |
| Industries Order Management | Decomposes the commercial order into technical orders, then orchestrates and fulfils them | Turns "Internet + TV" into the tasks each provisioning system needs |
| Contract Lifecycle Management | Contract requests, templates and clauses, redlining, e-signature, renewals and frame agreements | Keeps enterprise agreements and renewals tied to the quote |
| Industries Digital Commerce | High-volume browsing and configuration for self-service channels, with caching and APIs that work without a quote or order record | Fast online shops that stay in step with the catalog |
| OmniStudio | Guided flows, cards, integration procedures and data mappers | Builds onboarding, serviceability and care journeys without heavy code |
Sources: Salesforce Trailhead on Industries CPQ and Industries Order Management, and the Digital Commerce developer guide.
Product catalog: define once, sell everywhere
The catalog holds the offers, bundles, add-ons, promotions, pricing and rules. Because quoting, digital commerce and order management all read from it, a new plan or promotion does not have to be rebuilt in each channel. In the managed package, product managers work in the catalog designer below; the screenshot comes from the Vlocity era, so today's labels and branding differ.
Order decomposition and orchestration: from what the customer bought to what the network does
Industries Order Management takes the order created in CPQ, which Salesforce compares to a commercial bill of materials, decomposes it, adds the technical detail and orchestrates fulfilment. It keeps two views: the commercial order (what the customer wants) and the technical order (what you deliver). A point of no return (PONR) decides how changes are handled: before it, a change amends the in-flight order; after it, a change order is created.
Salesforce's guidance is that Industries Order Management suits operators with many dynamic rules and decomposition scenarios, while standard Salesforce Order Management fits static rules. If you already run an order management system, Industries CPQ comes with integration tools to hand orders to it instead.
OmniStudio: guided journeys for agents and customers
OmniStudio is where onboarding, serviceability checks, moves and care scripts are built. An OmniScript like the one below walks an agent through capturing a customer and checking serviceability at an address, calling outside systems through Integration Procedures along the way.
Since Summer '25, OmniStudio is package-free for new customers, with designers and runtime available natively under supported licences. Our earlier article on OmniStudio solutions and our guide to Salesforce Industries CPQ go deeper on both tools.
What Do Enterprise Sales Management and Multiplay Subscription Management Add?
They are prebuilt industry applications on top of the shared components. Enterprise Sales Management (ESM) handles B2B deals for large, multisite customers. Multiplay Subscription Management (MSM), still called Mobile Subscription Management in some Salesforce material, handles B2C subscriber sales and care. Each saves you from designing those processes from scratch.
| Enterprise Sales Management (B2B) | Multiplay Subscription Management (B2C) | |
|---|---|---|
| Customers | Large and medium-sized enterprise and government customers | Consumer subscribers |
| Selling | Multisite, multi-subscriber quotes; bulk upload of locations and subscribers from CSV or XLS; group and member quoting; bulk add, change and disconnect | Plans, add-ons for data, voice or text, renewals |
| Product models | Predefined models for enterprise mobile, business internet and VPN | Subscriber offers from the shared catalog |
| Care | Orders submitted at once or as sub-orders over time; address validation and map views of sites | Usage and balance views, wallet top-ups, lost or stolen SIM, termination |
| Channels | Sales console | Agent console and an Experience Cloud self-service portal |
| Integrations | Industries CPQ included with the ESM licence | Prebuilt integration with the Matrixx online charging system; mock integrations for vouchers, SIM and number inventory |
Sources: Salesforce Trailhead on Enterprise Sales Management and Multiplay Subscription Management.
Note that "mock integrations" are placeholders: they show the shape of the integration, but your team still connects the real voucher, SIM and number-inventory systems.
Does Communications Cloud Replace Your Billing and Network Systems?
No. Plan for it to connect to them. Communications Cloud runs the commercial middle office: catalog, quote, order, contract and service. Rating, charging, invoicing, inventory and network provisioning stay in specialist systems that it exchanges data with. Salesforce's own B2C application, for example, integrates an external online charging system rather than charging usage itself.
The standard billing objects make the split visible. Salesforce's developer guide describes the BillingAccount object as representing "the customer's billing controls in the backend system", such as bill frequency, format and autopay. Orders flow out to fulfilment and billing; status and account data flow back.
TM Forum Open APIs
Communications Cloud exposes inbound TM Forum Open APIs so external systems can read catalogs, place orders and manage customers in a standard way. Salesforce's TM Forum API developer guide lists the supported set:
| API | Name | Version |
|---|---|---|
| TMF620 | Product Catalog | v4 |
| TMF621 | Trouble Ticket | v5 |
| TMF622 | Product Ordering | v4, v5 |
| TMF629 | Customer Management | v4 |
| TMF632 | Party Management | v5 |
| TMF637 | Product Inventory | v4, v5 |
| TMF648 | Customer Quote | v4 |
| TMF651 | Agreement | v4 |
| TMF666 | Account Management | v5 |
| TMF667 | Document Management | v4 |
| TMF671 | Promotion Management | v4 |
| TMF679 | Product Offering Qualification | v5 |
The TM Forum APIs cover the standard conversations. Anything else, such as a specific charging platform, number portability, SIM inventory or a field workforce tool, needs integration work, usually through MuleSoft or another middleware layer with retries, error logging and monitoring. Our MuleSoft integration services cover that layer.
What Do Agentforce for Communications and Data 360 Add?
Agentforce for Communications adds prebuilt AI agents for telecom tasks such as billing disputes, quoting and service insights. Data 360 brings billing, network and CRM data into one context those agents can use. Both depend on clean, connected data: an agent that cannot see billing or network data cannot resolve a billing or outage question.
Salesforce announced Agentforce for Communications on February 26, 2026, with agents for billing resolution, service level objective (SLO) insights, quoting, site grouping and guided selling for field technicians. Its communications AI page now lists these prebuilt capabilities:
Billing Resolution
Compares historical and current invoices with product and service context to explain bill changes and resolve disputes.
Quoting, Ordering and Upsell
Helps sellers build quotes and orders and spot upsell and cross-sell opportunities.
Site Grouping
Aimed at enterprise deals that span many locations, where sites must be organised before they can be quoted.
Service Insights
Surfaces service level objective data so teams can see and act on service performance.
The AI page also lists asset service and inventory management, and notes that prebuilt capabilities may not reflect actual product details or be available yet. Treat the list as direction and confirm what is generally available for your edition before you plan around it. Agents can be customised in Agentforce Builder.
On data, Salesforce says Data 360 with the communications data models can "unify billing, network, and CRM data into a single, trusted context layer without moving your data". For a broader view of how agents reason and act, see our guide to how Salesforce Agentforce works.
Managed Package or Salesforce Platform: Which Version of Communications Cloud?
Communications Cloud is available both as a managed package and natively on the Salesforce platform. The managed package is the former Vlocity stack. The platform version builds on Agentforce Revenue Management and extends it with telecom capabilities. Existing customers usually run the package; new projects should confirm with Salesforce which model their scope supports.
| Managed package | Salesforce platform (core) | |
|---|---|---|
| Foundation | Industries packages such as vlocity_cmt with their own objects | Agentforce Revenue Management on standard objects |
| Catalog | Shared Catalog and Enterprise Product Catalog | Product Catalog Management with Business Rules Engine |
| Pricing and configuration | Industries CPQ | Salesforce Pricing and Product Configurator |
| Quote to order | Industries CPQ and Industries Order Management | Transaction Management, with asset tracking |
| Decomposition and orchestration | Industries Order Management | Dynamic Revenue Orchestrator |
| TM Forum APIs | Supported | Supported |
Sources: Salesforce Trailhead, Discover Agentforce Revenue for Communications, and the Communications standard objects reference.
Salesforce keeps adding standard objects for communications on the platform, such as billing account objects in Summer '26 and cart item attributes and relationships in Spring '26. That is a sign of where new investment is going.
If you run the managed package today
Moving OmniStudio from the managed-package runtime to the standard runtime has a tool: the Omnistudio Migration Assistant, a CLI plugin with assess and migrate modes. But Salesforce is candid about its limits: it does not move industry objects from the Vlocity packages to standard objects, which Salesforce calls "a huge effort which is often underestimated". It also cannot convert Angular OmniScripts, which must be rebuilt in Lightning Web Components first, and Salesforce does not recommend uninstalling the package while workflows still depend on its schema. Start with an assessment, not a date.
Do You Need Communications Cloud, or Can Sales Cloud Run a Telecom Business?
It depends on catalog and order complexity more than company size. If you sell many configurable bundles and orders fan out to several provisioning systems, Communications Cloud's catalog and orchestration repay their cost. If you sell a few plans and the hard part is onboarding and billing sync, Sales Cloud with a custom telecom data model and solid integrations is often the faster, cheaper route.
We have seen both paths work. For a US digital services provider launching 5G, we kept the client on Sales Cloud, built custom ICCID (SIM) and MSISDN (mobile number) objects, connected Mavenir provisioning through MuleSoft with retry logic, and automated account creation in the Alepo billing system. The telecom case study reports activation time cut from 48 hours to 12 and provisioning failures down 30%, delivered in phases over 10 to 16 weeks. For a Pacific-region satellite broadband provider, Sales Cloud with Formstack document automation and distributor KYC tracking was the right fit.
At the other end, our Salesforce for telecom and infrastructure page describes a client, a 5G and fiber operator, whose transformation, built on Salesforce Communications Cloud with an ODA-aligned architecture and Aria billing integration, was showcased at TM Innovate Americas 2024. Multi-service operators at that scale are where the industry cloud pays off.
How Do You Implement Salesforce Communications Cloud?
Start from the catalog and the order flow, not the screens. Map how a customer moves from offer to quote, order, activation, bill and change, decide which system owns each step, then model the catalog and integrations to match. Build and test journey by journey in a sandbox before any cutover, and keep billing and provisioning teams involved from day one.
| Phase | Decisions and work | Done when |
|---|---|---|
| 1. Discover and decide | Current systems and handoffs; managed package or platform; editions; system of record for customer, product, order, asset and bill | An agreed target architecture |
| 2. Model the catalog | Product, service and resource specifications; bundles, promotions, pricing and eligibility rules; decomposition maps | The top offers configure and price correctly in a sandbox |
| 3. Integrate | Billing and charging, provisioning, inventory, number portability, field service; TM Forum APIs or middleware; error logging and retries | Orders reach downstream systems and statuses return |
| 4. Build journeys | Sales and care journeys in OmniStudio; consoles and self-service; contracts and documents | End-to-end tests pass for each priority journey |
| 5. Migrate and launch | Customer, asset and contract data; phased rollout by segment or region; training | One segment runs live without manual workarounds |
| 6. Run and extend | Dashboards for order fallout and integration errors; catalog governance; Agentforce and Data 360 use cases | New offers launch without code changes |
Pitfalls to avoid
Integration is usually the largest share of the work. Our Salesforce integration services connect Salesforce to billing, provisioning and network platforms with monitoring built in.
The Bottom Line
Salesforce Communications Cloud is a serious telecom platform for operators whose catalogs and orders are complex enough to need it. It runs the commercial middle office and connects to the billing and network systems around it. Twopir Consulting designs and integrates Salesforce for telecom and infrastructure companies, on Communications Cloud or on Sales Cloud, whichever fits the business.
- 1
Know what you are buying: a telecom BSS front office, now also called Agentforce Communications, not a messaging tool.
- 2
Choose it for catalog complexity and order orchestration; otherwise consider Sales Cloud with a telecom data model.
- 3
Decide between managed package and platform early, and assess any migration before setting dates.
- 4
Design billing, provisioning and TM Forum API integrations with the catalog, and plan for the Winter '27 Direct Access change.
- 5
Add Agentforce and Data 360 once billing, network and CRM data are connected and trusted.
Get a Clear Answer on Communications Cloud
Tell us what you sell, how orders reach your network and billing systems, and where they get stuck. We will tell you whether Communications Cloud, Sales Cloud or an integration fix is the right next step.
Schedule a Discovery CallFrequently Asked Questions
Yes. Salesforce's Trailhead states that Communications Cloud is now called Agentforce Communications, and that the old name still appears in the application and documentation. Salesforce's product and pricing pages still say Communications Cloud. Agentforce for Communications is different: it is the set of prebuilt telecom AI agents.
It is built for communications service providers: mobile, broadband, fiber, cable and enterprise connectivity operators. Salesforce supports B2C subscriber businesses, B2B sales to multisite enterprises and governments, and wholesale markets. It fits best where catalogs are complex and orders must be orchestrated across several provisioning and billing systems.
Plan for it to connect to them, not replace them. Communications Cloud runs catalog, quoting, ordering, contracts and service. Salesforce's B2C application integrates an external online charging system, and its billing account object represents billing controls held in the backend system. Rating, charging and invoicing stay in your billing platform.
The managed package is the former Vlocity stack, with its own objects, Industries CPQ and Industries Order Management. The platform version builds on Agentforce Revenue Management, using Product Catalog Management, Salesforce Pricing, Product Configurator, Transaction Management and Dynamic Revenue Orchestrator on standard objects. Both support TM Forum Open APIs.
Salesforce lists inbound support for TMF620 Product Catalog, TMF621 Trouble Ticket, TMF622 Product Ordering, TMF629 Customer Management, TMF632 Party Management, TMF637 Product Inventory, TMF648 Customer Quote, TMF651 Agreement, TMF666 Account Management, TMF667 Document Management, TMF671 Promotion Management and TMF679 Product Offering Qualification. From Winter '27, only Direct Access is supported.
Salesforce announced agents for billing resolution, service level objective insights, quoting, site grouping and guided selling in February 2026. Its AI page also lists upsell and cross-sell, asset service and inventory management, with a note that some capabilities may not be available yet. Confirm what is available for your edition before planning.
Not on a fixed date that Salesforce has published, but new capabilities are arriving on the platform. The Omnistudio Migration Assistant moves OmniStudio components to the standard runtime, but does not migrate Vlocity industry objects to standard objects, which Salesforce calls a huge and often underestimated effort. Start with an assessment.
Often, yes. Operators with a small catalog and one or two provisioning systems can run well on Sales Cloud with custom telecom objects, such as SIM and mobile number records, plus solid billing and provisioning integrations. Communications Cloud earns its cost when bundles, eligibility rules and order orchestration grow complex.
