CCM as a service means a provider runs your customer communication platform for you: the software, the hosting, the upgrades, the security and the daily production runs. Your organisation keeps the content and the decisions: what customers receive, which rules choose who gets which variant, and who approves a change. For the team, the work of keeping a platform alive goes away and more time goes to the communication itself. Business owners make routine content changes themselves in low-code tools, and IT is no longer the queue every edit waits in. Accountability stays with you.
What is CCM as a service?
A customer communications management (CCM) platform produces the letters, statements, emails, SMS and portal messages an organisation sends to its customers. On-premise, you license the software and run it yourself. With CCM as a service (CCMaaS), a provider hosts the platform, keeps it current and runs production under agreed service levels.
🟦 your organisation · 🟧 the provider
| Activity | Platform you run yourself | CCM as a service |
|---|---|---|
| Deciding what the customer receives, approving changes | 🟦 Business owner | 🟦 Business owner |
| Routine content changes | 🟦 Business owner, or IT if the tools are too technical | 🟦 Business owner, in low-code tools |
| Building templates and business rules | 🟦 IT | 🟧 Provider, on the instruction of the business |
| Data feeds from source systems | 🟦 IT | 🟦 IT, with help from 🟧 the provider |
| Hosting, upgrades and security | 🟦 IT | 🟧 Provider |
| Monitoring production runs | 🟦 IT | 🟧 Provider and 🟦 IT, with the provider able to fix a run remotely |
| Compliance with sector rules | 🟦 Your organisation | 🟦 Your organisation |
Why do organisations move to CCM as a service?
Usually to put more of their attention on the communication itself, and less on the platform underneath it. Three things change in practice:
- Less effort per change. A wording change or a new variant no longer waits for a release window, a server or the one specialist who knows the platform.
- A cleaner template estate. Over the years most on-premise platforms collect template sprawl: near copies of the same letter, variants for products that no longer exist, business rules that overrule each other. The move is a natural moment to clear that out, and a provider that has done it before helps decide what to merge, rewrite or retire.
- More time for content. Business owners and IT spend their hours on what customers read and on the data behind it, instead of on keeping software running.
Key takeaway: A managed service takes the platform work off your team so the attention goes to what customers read. Clearing out years of overlapping templates and rules is often the biggest gain of the move.
What moves off your team’s plate?
The work that keeps the platform running, which is also the work that is hardest to staff:
- Patching and upgrading. On-premise, a major version upgrade is a project with its own budget and test cycle. As a service, it is part of what you pay for.
- Servers, capacity for peak runs such as the annual statement, backups and disaster recovery.
- Security of the platform and the certification evidence that goes with it.
- Watching production at night and at month end, and restarting a failed run.
- Support from a distance. Because the platform runs as a cloud service, the provider can get onto it remotely, pick up a problem straight away and roll out updates without an install round on your own servers.
What stays with your organisation?
Everything that decides what a customer reads, and the responsibility for it:
- The content. Wording, mandatory text, design, and the rules for which customer gets which variant.
- The approval. Every change is signed off by the named business owner of that document family.
- The data. Customer data comes from your source systems. Under the GDPR the provider is a processor that processes personal data only on behalf of the controller.
- Compliance. Accountability to your supervisor does not transfer with the work. The provider can produce the documents and the audit trail a regulator expects; answering for them stays with you.
That is the usual split. How independent you want to be, and where you want help, is up to you. Some organisations do all content work themselves from the first day. Others ask the provider to help with work that normally stays in-house, such as preparing template changes for the business owner to approve.
How do roles change in a managed CCM service?
Three roles shift. None of them disappears, and it helps to settle who owns, approves and runs what before the move.
- Business owners do more themselves. Modern CCM platforms give them low-code editors to change wording or adjust a template within agreed rules, with the approval route as the safety net. Passing every edit through IT is the old way of working.
- IT moves from running the platform to connecting it. Its work becomes the data feeds from source systems and the security requirements, and it no longer sits between the business and every content change. A CCM as a service provider usually helps build and maintain those connections, but IT stays involved: it knows the source systems and controls access to them.
- Someone owns the service. A named service owner, often in IT, holds the contract, reads the service reports and is the provider’s counterpart. For many mid-market teams this role is new, and easy to forget.
When does on-premise CCM still make sense?
The classic trade-off is investing up front or paying over time. On-premise, you buy licences and servers and staff the platform yourself. As a service, you pay a fee that usually moves with volume. The market is moving towards subscription and volume-based models, but some organisations still choose to run CCM themselves. That tends to fit in two situations:
- Very large scale. Running a platform well brings real technical overhead and investment in servers. That only pays back at very high volumes, and once you include what the migration itself costs.
- Deep customisation. An installation of your own can be adapted further than a shared platform. That advantage is smaller than it used to be: with today’s APIs, a standard platform connects to almost any system.
How a managed service like CCMaaS can help
The question usually comes up at a fixed moment: an end-of-support date, a major upgrade with no budget behind it, or the platform specialist handing in notice. Compare the routes then on the team each one needs, how quickly business owners can change content, and how you would leave. Eclipse is one example of a provider that delivers CCM this way. Whichever provider you look at, ask before the demo how they would help clear out your current templates and rules, and how much of the work you can keep in-house if you want to.
Frequently asked questions
Does a CCM as a service provider decide what goes in my letters?
No. The provider builds and runs what the business asks for. The wording, the rules and the approval of every change stay with your business owners.
Do I have to send every content change to the provider?
No. Routine changes such as wording or a new variant of a letter are made by your business owners in low-code tools. The provider takes the technical work, such as a new channel, and helps IT with new data feeds. If you want help with content work as well, you can ask for it.
Who is responsible for compliance when CCM runs as a service?
Your organisation. A provider can produce the documents and the audit records. The obligation to comply, and to give your supervisor access, stays with you.
What happens to our templates and data if we change provider?
That is set in the contract: termination rights, a transition period and export of templates, content and archive in a usable format. The processor agreement states how personal data is returned or deleted.
Related: CCM, CRM and marketing automation: who does what?
If your on-premise platform is heading for its next big upgrade, we are happy to walk through what would move and what would stay.
