CM.com Features: A Practical Guide to Its Platform, Messaging APIs, and Developer Tools

CM.com positions itself as an AI-powered engagement platform that helps businesses move from a first interaction to a fully supported customer relationship across multiple channels. The company's product surface is broad: messaging APIs, a mobile marketing cloud, payments, identity verification, and customer contact tools all live under one roof. For developers and technical decision-makers, however, the most important question is not what the marketing pages promise, but what the platform actually exposes through its APIs and feature sets.

This guide breaks down CM.com features by functional area, explains how the core messaging API behaves, and highlights where the platform fits—and where a unified messaging API like UnifyPort may be a better architectural fit.

What Is CM.com's Engagement Platform?

CM.com Features: Platform, Messaging & API Capabilities - What Is CM.com's Engagement Platform?.

CM.com describes its product suite as an AI-powered engagement platform that spans the entire customer journey. In practice, that means several distinct product lines:

• Messaging APIs for SMS, WhatsApp, RCS, Viber, Apple Messages for Business, Facebook Messenger, and Instagram
• Mobile Marketing Cloud for campaign orchestration, segmentation, and cross-channel journeys
• Payments for in-app, online, and point-of-sale transactions
• Identity and verification tools for customer onboarding
• Customer contact solutions, including a webchat widget powered by DigitalCX

The platform's breadth is its main selling point. A single vendor contract can cover messaging, payments, and identity, which appeals to enterprises that want to consolidate suppliers. But that breadth also means the developer experience varies by product line, and the messaging API carries specific design choices that teams need to understand before committing.

Core Messaging API Features

CM.com Features: Platform, Messaging & API Capabilities - Core Messaging API Features.

CM.com's messaging API is the most developer-relevant part of the platform. The official API documentation reveals several features that shape how you build on top of it.

Unified Message Object with allowedChannels

One of the most distinctive CM.com features is the allowedChannels array. Instead of calling a separate endpoint for each channel, you send a single message object and specify which channels are eligible for delivery:

{
    "messages": {
        "msg": [{
            "body": {
                "type": "auto",
                "content": "Message Text"
            },
            "to": [{
                "number": "00316012345678"
            }],
            "from": "TestSender",
            "allowedChannels": ["WhatsApp", "SMS"]
        }]
    }
}

This is a meaningful abstraction: you write one request shape and let the platform decide which channel actually carries the message. The allowedChannels field accepts any combination of SMS, Viber, RCS, Apple Messages for Business, WhatsApp, Facebook Messenger, and Instagram.

Channel Fallback Logic

A key behavior tied to allowedChannels is fallback. If the first eligible channel fails or is rejected, CM.com tries the next one. For example, specifying ["WhatsApp", "SMS"] means a WhatsApp rejection triggers an SMS delivery using the same message body.

There are two important caveats:

1. The order of channels in allowedChannels does not determine fallback order. Priority is configured per account, and changing it requires contacting CM.com support.
2. Fallback is immediate, not retry-based. When a channel fails, the platform moves to the next channel rather than retrying the first one.

Fallback is supported for WhatsApp, Push, RCS, Viber, and SMS. This is a practical feature for transactional notifications where delivery reliability matters more than channel preference, but the account-level routing configuration can surprise developers who expect array order to control priority.

Batching and Asynchronous Delivery

CM.com supports sending multiple messages in a single request. You can either target multiple phone numbers with the same message or declare multiple distinct messages in one msg array. The recommended maximum batch size is 1,000 messages; exceeding it may degrade throughput.

All messages are delivered asynchronously. The API response only confirms that a message was accepted for a delivery attempt, not that it was delivered. Delivery confirmation arrives later through status report webhooks, which means your integration must be webhook-first rather than response-first.

References and Custom Grouping

Each message can carry a reference string (1–32 alphanumeric characters) that is echoed back in status reports and inbound replies. This lets you correlate delivery events with your internal message IDs. CM.com also supports up to three customGrouping fields for tagging messages, which can feed into other products like the Transactions API for analysis.

{
    "messages": {
        "msg": [{
            "allowedChannels": ["SMS"],
            "from": "SenderName",
            "to": [{"number": "00447911123456"}],
            "body": {"type": "auto", "content": "Test message"},
            "reference": "order-12345",
            "customGrouping": "Campaign ABC",
            "customGrouping2": "Department XYZ"
        }]
    }
}

Validity Periods

CM.com lets you set a validity window on each message, after which the platform treats it as failed and notifies you via status report. You can specify an absolute timestamp or a relative offset like 2h or 30m. The default and maximum validity is 24 hours, and the feature is best-effort: operators already processing a message may not honor it.

Rich Content

For WhatsApp, RCS, Viber, Twitter, Facebook Messenger, and Instagram Messaging, CM.com supports rich content through a richContent JSON attribute. This contains a conversation array of content items and optional suggestions for interactive replies. Rich content is where the API diverges from plain SMS: you can send cards, media, and structured messages that go well beyond a 160-character text body.

Mobile Marketing Cloud Features

CM.com Features: Platform, Messaging & API Capabilities - Mobile Marketing Cloud Features.

CM.com's Mobile Marketing Cloud is the campaign-oriented layer on top of the messaging API. It packages features into Basic, Advanced, and Pro tiers, with capabilities that typically include:

• Audience segmentation based on behavioral and profile data
• Cross-channel journey builders that orchestrate messages across email, SMS, WhatsApp, and push
• Template management for WhatsApp and other rich channels
• Campaign analytics for open, click, and conversion tracking
• A/B testing and personalization tools in higher tiers

The marketing cloud is aimed at marketing teams rather than developers. It abstracts the API into a visual interface, which is convenient for campaign managers but adds a layer of vendor lock-in: journeys built in the marketing cloud are not portable to another messaging provider.

Where CM.com's Messaging Model Creates Friction

CM.com's messaging API is capable, but its design has specific trade-offs that matter for engineering teams:

Account-Level Routing Obfuscates Control

The fact that allowedChannels order does not control fallback priority is a significant design decision. Developers expect explicit, request-level control over routing. With CM.com, that control lives in account configuration, which means:

• Routing behavior can change without any code change on your side
• Testing fallback scenarios requires support involvement
• Multi-tenant applications cannot easily give each tenant different routing rules

Asynchronous Delivery Requires Webhook Discipline

Because the API only confirms acceptance, your system must reliably consume status report webhooks to know whether messages actually arrived. This is standard for messaging APIs, but CM.com's webhook surface is one more integration surface to build, secure, and monitor.

Channel-Specific Rich Content Still Leaks Through

While the base message object is unified, rich content uses channel-specific conversation item formats. WhatsApp templates, RCS cards, and Viber messages each have their own structure, so the "one API for all channels" promise weakens as soon as you move beyond plain text.

A Unified Alternative: UnifyPort

For teams that need multi-channel messaging without provider-specific complexity, UnifyPort takes a different approach. UnifyPort is a unified messaging API platform that connects Telegram, WhatsApp, LINE, X (Twitter), Zalo, and TikTok through a single REST API and standardized webhook events.

The architectural difference is meaningful. Where CM.com unifies the request shape but still exposes channel-specific routing configuration and rich content formats, UnifyPort normalizes both sides:

• A standard event layer converts every provider message into a consistent JSON shape, so inbound webhooks from Telegram look structurally identical to those from WhatsApp
• A webhook control plane manages signatures, subscriptions, and retries in one place
• Built-in rate limiting, retries with idempotency, and failure isolation handle delivery reliability without account-level routing surprises
• Workspaces and accounts isolate tenants and act as virtual devices per channel

This model is particularly relevant for AI agents, CRMs, notification systems, and operations tools that need to connect to many messaging platforms without building separate integrations for each. If your use case is primarily SMS and WhatsApp with fallback, CM.com's messaging API is a reasonable fit. If you need normalized events across chat apps like Telegram, LINE, Zalo, and TikTok, a platform like UnifyPort addresses a gap that CM.com's channel list does not cover.

For a deeper comparison of unified messaging approaches, see Unipile examples and real API workflows and the CM.com integration guide.

CM.com Features vs. Unified Messaging APIs: A Decision Guide

Requirement	CM.com Messaging API	UnifyPort
SMS, WhatsApp, RCS, Viber	Yes	WhatsApp only among these
Telegram, LINE, Zalo, TikTok, X	No	Yes
Unified request shape	Yes (allowedChannels)	Yes (single REST API)
Normalized inbound events	Partial (channel-specific payloads)	Yes (standard event layer)
Request-level fallback control	No (account-level routing)	N/A (direct channel targeting)
Webhook management	Manual setup per channel	Built-in control plane
Marketing campaign UI	Yes (Mobile Marketing Cloud)	No (developer-focused)
Payments and identity	Yes	No

This table highlights the core decision: CM.com is a broad engagement platform with a messaging API attached, while UnifyPort is a focused messaging infrastructure layer. Choose based on whether you need the full platform or clean multi-channel messaging primitives.

Related reading

• Email API Integration: A Developer's Complete Guide - Learn how email API integration works, compare REST vs SMTP, explore code examples, key features, pricing models, and how to choose the right provider.
• CM.com Breda: History, HQ, Careers & Alternatives - Learn about CM.com's Breda headquarters, its 1999 founding as ClubMessage, key milestones, and how its messaging platform compares to unified API alternatives.

Frequently Asked Questions

What channels does CM.com support?

CM.com's messaging API supports SMS, WhatsApp, RCS, Viber, Apple Messages for Business, Facebook Messenger, and Instagram. Push notifications are also supported through the fallback mechanism.

Does CM.com support channel fallback?

Yes. You can specify multiple channels in the allowedChannels array, and if the first eligible channel fails, CM.com falls back to the next one. Fallback order is configured per account, not by array order.

Is CM.com delivery synchronous or asynchronous?

All CM.com messages are delivered asynchronously. The API response confirms acceptance only; delivery status arrives through status report webhooks.

What is the maximum batch size for CM.com messaging?

The recommended maximum is 1,000 messages per request. Exceeding this limit may reduce throughput.

Does CM.com support rich content?

Yes, for WhatsApp, RCS, Viber, Twitter, Facebook Messenger, and Instagram Messaging. Rich content uses a richContent JSON attribute with conversation items and optional suggestions.

How does UnifyPort differ from CM.com?

UnifyPort focuses on unified messaging across Telegram, WhatsApp, LINE, X, Zalo, and TikTok with a normalized event layer and webhook control plane. CM.com is a broader engagement platform covering SMS, WhatsApp, RCS, Viber, payments, and marketing tools, but does not support chat apps like Telegram, LINE, Zalo, or TikTok.

Can I use CM.com for mobile marketing campaigns?

Yes. The Mobile Marketing Cloud provides segmentation, journey orchestration, template management, and analytics across Basic, Advanced, and Pro packages.

Conclusion

CM.com features span a wide engagement platform: a capable messaging API with channel fallback, batching, references, validity windows, and rich content, plus a marketing cloud, payments, and identity tools. For enterprises that want a single vendor across SMS, WhatsApp, RCS, and Viber—and are comfortable with account-level routing and asynchronous webhook workflows—CM.com is a solid option.

For engineering teams that need normalized multi-channel messaging across chat apps like Telegram, LINE, Zalo, and TikTok, the platform leaves a gap. Unified messaging APIs like UnifyPort fill that gap with a consistent event layer, managed webhooks, and provider-agnostic delivery. The right choice depends on whether you need a broad engagement suite or clean messaging infrastructure. If you're evaluating SMS-focused options, the SMS API developer guide and CRM messaging integration overview provide additional context for building your messaging stack.