Business users want and need customer communications management (CCM) software that allows them to create and modify layouts and templates without help from IT, and without having to learn HTML5 or CSS3. And they want an intuitive, user-friendly visual interface.

The title of Micah Solomon’s recent Forbes article caught my eye: “Stupid Touchpoints Are Worse Than No Touchpoints in Customer Service and Customer Experience.” It proved to be an entertaining and worthwhile read, reminding those of us in customer experience (CX) and customer communications management (CCM) to think very hard about the reasons and ways we touch customers before we start touching them inappropriately (i.e., everywhere, all the time, and turning them off in the process).

In Three Ways to Use CCM Metrics, Analytics to Improve Customer Experience, one of the three methods I mentioned was multichannel contextualization:

Unless you’re a brand-spanking-new startup, your organization almost certainly has legacy software. By “legacy,” we mean previously acquired and now outdated – any software that was purchased when business requirements and market dynamics were different than they are today.

All companies have two topline objectives, regardless of industry, size or business model: revenue growth and profitability. So the metrics that companies gather for any business function, including customer communications management (CCM), usually speak to one or both of these. Profitability usually gets translated to CCM in terms of operational efficiency. The goal is simply to spend less generating, distributing and tracking communications. Since customer service call centers are usually the most costly way to deliver customer service, there’s a lot of sensitivity around call center volume, resolution rates, cost per touch, etc. So companies work to deflect the need for customers to use the call center through methods such as customer self service portals and improved customer communications.

Cloud-based software and software-as-a-service (SaaS) solutions appeal to many enterprises. Most companies are either looking for software they can access through a web browser and/or they want to subscribe to or “rent” their software for a monthly fee. How an organization pays for its software is often a function of their CFO’s preference — for example, to capitalize the purchase of software for EBITDA reasons, or treat it as a monthly operating expense for cash flow reasons. Why an organization uses and where it manages its software, however, come down to line of business and IT requirements.