Enterprise DNA

Instead of Salesforce Communications Cloud

Stop renting Salesforce Communications Cloud. Own your telecom service desk.

We build your version around how you manage customer services, bring your Salesforce records across and run it for you. Your carrier follow-ups, evidence and renewal rules stay together.

Salesforce lists Advanced at US$475 per user per month, billed annually. That is US$5,700 per user per year.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The recurring software bill

What sits inside a Communications Cloud subscription

The platform covers more than an internal service desk. Compare the parts your operators use with the parts your business needs connected.

paid

Growth seats

Growth lists US$325 per user per month, billed annually, for the industry platform.

layers

Advanced seats

Advanced lists US$475 per user per month, billed annually, with revenue and contract capabilities.

inventory_2

Service and asset records

Customer services and asset-based orders are part of the platform. Your team still needs accurate service locations and carrier references.

sync

Industry processes

Pre-built communications processes sit in the product. Your customer instructions and carrier follow-up steps determine how the work actually moves.

extension

Related products

The pricing page lists additional communications products and integrations. Check your own contract for what is included.

description

The annual commitment

The displayed seat prices are billed annually. Start your comparison with the contracted seats, operating scope and renewal date.

Your own operating records

Follow each service change through to evidence

Service inventory

Know which service belongs where

Read a customer service file with its location, carrier and current terms.

  • check Customer accounts and service locations linked together
  • check Fibre, voice, mobile and data service records
  • check Monthly charge and recorded carrier cost kept by currency
  • check Active services with missing carrier references surfaced for review

Change control

An instruction, an owner and a confirmed result

Track moves, additions, commercial changes and disconnections against the existing service.

  • check One open change per service
  • check Customer authorisation recorded before completion
  • check Carrier tasks closed with supporting evidence
  • check Confirmed changes update the local service record

Commercial review

See renewals beside unfinished work

Review contracts that are ending while a service change is still open.

  • check Contracts expiring within 60 days and expired active contracts
  • check Negative monthly margins identified in the recorded figures
  • check Customer margins separated by currency
  • check Renewals joined to unfinished changes in one answer

The weekly desk

Give the team a clear follow-up list

Prepare the week from overdue work and named owners.

  • check Carrier commitments sorted by due date
  • check Open and overdue changes grouped by owner
  • check Accuracy and retention review queues
  • check Branded service schedules, change papers and renewal briefs

Make it yours

Design your own Salesforce Communications Cloud replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Salesforce Communications Cloud. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Salesforce Communications Cloud replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Salesforce Communications Cloud data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Telecom Operations for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Telecom Operations for Claude Code

Connected to your own database

Which service changes are overdue or still waiting for authorisation?

MACD-101

Rvice ca
SVC-101
Rrier ki
Demo Carrier North
Nd ow
move
Ner st
Mia
Atus du
authorised
E on da
2026-10-15
Ys overdue op
2
En tasks
1

MACD-102

Rvice ca
SVC-104
Rrier ki
Demo Carrier South
Nd ow
add
Ner st
Ari
Atus du
requested
E on da
2026-10-22
Ys overdue op
0
En tasks
1

Ask it anything

Questions Salesforce Communications Cloud cannot answer

Every one of these is a real question the demo answers today. Yours will be different, and that is the point.

chat_bubble Which active services cost more than their monthly charge?
chat_bubble Which renewals have an unfinished service change?
chat_bubble Which carriers have overdue follow-ups?
chat_bubble Which customer accounts have the lowest monthly margin in each currency?
chat_bubble Which active services have no carrier reference?
chat_bubble Which requested changes still need customer authorisation?
chat_bubble Which authorised changes are blocked by carrier tasks?
chat_bubble Which service records need an accuracy or retention review?
chat_bubble Which expired service contracts are still active?
chat_bubble Which completed changes have both customer and carrier evidence?

Switching

How to switch from Salesforce Communications Cloud

A move involves exporting and mapping your service records, checking the import, and running both systems side by side before you switch off Salesforce Communications Cloud.

  1. 1

    Export your service records

    Start with a Salesforce Details Only service asset report if your account can provide one. Otherwise, export what your account allows, usually CSV or Excel, and check the available options with Salesforce Communications Cloud. Focus on the service records that include accounts, locations and service terms. Orders, tasks, attachments and approval history need a separately reviewed migration.

  2. 2

    Map and test the data

    Match the report headings to the fields used by the new service desk. This is a one-time mapping, and the example report shape is not universal. Ask for a test run before importing records. The test uses a dry run, so it lets you review the import without loading the records into the database.

  3. 3

    Review import findings

    Check the dry-run results before you proceed. The import can create accounts, sites and services, and it retains the original source rows. Unchanged repeated rows are skipped. Changed rows stop for reconciliation, so resolve those differences before importing. Check that dates and amounts are in the expected formats and that the mapped fields are correct.

  4. 4

    Run both systems side by side

    Keep Salesforce Communications Cloud available while your team checks the imported records and uses the new desk for the internal service register and change review. Compare the records and working process, and resolve any issues before relying on the new desk. Keep your live network, billing and emergency-service processes in place unless a separate replacement has been scoped and checked.

  5. 5

    Switch off Salesforce

    When you have checked the records and agreed the new process is ready, stop using Salesforce Communications Cloud for the work you have moved. Keep a suitable export or backup of the records you may need. The new desk stores your operational records in a database, but it does not operate the network, bill subscribers or send carrier orders.

construction

Where the real effort goes

The main work is usually mapping your own Salesforce report headings to the service fields, agreeing which business rules and review steps to carry over, and deciding how much history to migrate. The standard import covers accounts, locations and service terms, while orders, tasks, attachments and approvals need separate review. Enterprise DNA handles this mapping and migration work when you have them build and run your version.

Not ready for a call?

Get your Salesforce Communications Cloud switch plan by email

We will send you the step-by-step plan for moving your business off Salesforce Communications Cloud, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to make it yours

Use the free desk or have your version built

Open source

Do it yourself

Free code

  1. 1 Clone the repo and run npm install, npm test and npm run demo.
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor.
  3. 3 Map your Salesforce asset report and test the import with --dry-run.
  4. 4 Reconcile services, locations and amounts before using your own database.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your service fields, commercial terms and approval rules
  • check Your Salesforce export mapped and reconciled
  • check Carrier connections and a web front end scoped for your process
  • check A different database or technology setup if your business needs it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and connected through Omni by Enterprise DNA
  • check Your import, backup and access arrangements operated
  • check Weekly carrier follow-ups and record reviews maintained
  • check Service reports updated as your customer portfolio changes
Book a call with Sam

Questions

Instead of Salesforce Communications Cloud, answered

Does the free version run our network or bill customers? expand_more

It covers the internal service register, change review, carrier follow-ups and working papers. Keep your live network, billing and emergency-service processes in place. We scope and check the connections your custom version needs before any cutover.

Can we bring our Salesforce service history across? expand_more

The free importer takes a mapped service asset report and preserves its original rows. It brings accounts, locations and service terms across. Report headings need a one-time mapping. Existing approvals, orders, attachments and other history need a separately reviewed migration.

What stops an unapproved change being marked complete? expand_more

Completion requires a recorded customer instruction, current record reviews, closed carrier tasks and carrier completion evidence. It updates your local records only. An operator must verify the evidence. A typed name is not authenticated approval.

How does the cost compare? expand_more

Salesforce lists Growth at US$325 and Advanced at US$475 per user per month, billed annually. The free code has no licence charge, but hosting, operation and your chosen assistant have costs. Enterprise DNA builds and runs your version for one setup fee, then a retainer.

Can we keep our screens and carrier connections? expand_more

Yes. We scope a web front end, authenticated team access and carrier connections around your operating process. The free desk provides read-only reports and local working papers. Your custom version is agreed around the workflows your team actually needs.

Bring your service desk and your software bill

Spend 30 minutes with Sam. Look at your service changes, carrier follow-ups, Salesforce bill and export. Agree what your own version needs to run and what must be checked before switching.

Book a call with Sam Get the free version

Telecom Operations for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Salesforce Communications Cloud?

Get your version built