Cross-channel communication

Cross-channel communication is the degree to which a customer receives a coordinated, consistent message across the channels they use, such as email, SMS, push, and in-app. A coordinated programme reaches each customer where they actually engage, with one message rather than four contradicting ones. A siloed programme sends the same person an email, a push, and a text about the same thing, or worse, sends conflicting offers because each channel team works alone.

The metric matters because customers experience your brand as one entity, not as separate channel teams. When the email team runs a win-back offer while the SMS team sends a different discount, the customer sees an organisation that does not know its own left hand. Measuring cross-channel communication turns that coordination into a number, so the cost of running channels in isolation becomes visible instead of being absorbed as a vague sense that messaging feels noisy.

Good coordination is not about reaching everyone everywhere. It is about reaching each customer on the channel they respond to, at a sensible frequency, with a message that lines up across touchpoints. Read alongside engagement metrics such as email open rate, a strong coordinated reach rate paired with steady engagement signals a healthy programme. Strong reach with falling engagement usually means frequency has tipped into fatigue.

The coordinated reach rate divides customers reached on a preferred channel without conflict by the total targeted. To compute it honestly you need a unified view of each customer across channels, not channel-by-channel send logs. These are the inputs that make the rate meaningful.

1. 1

   Customers targeted

   The full set of people a communication was intended to reach, deduplicated to one record per person across all channels. Counting per channel double-counts anyone reachable on more than one.

2. 2

   Channel preference and engagement

   Which channel each customer actually responds to. A push notification to someone who never opens the app is reach on paper and silence in practice.

3. 3

   Message consistency

   Whether the messages a customer receives across channels agree with each other. Conflicting offers or stale information mark a touchpoint as a conflict, not coordinated reach.

4. 4

   Frequency and suppression

   How many messages each customer received in the window, and whether suppression rules stopped the same person being hit on every channel at once. Without this, the rate hides fatigue.

Coordinated reach is a headline that hides whether the problem is the wrong channel, a conflicting message, or simple over-sending. A metric tree decomposes it into the drivers underneath, so a falling rate is diagnosed as a data problem, a routing problem, or a frequency problem rather than treated as one vague coordination failure. Each branch points to a team and a fix.

The gap between a dashboard and a decision is that a dashboard shows the rate dropping but not which channel team caused it. KPI Tree connects each node in the tree to its owner through RACI, so the channel-routing branch sits with the lifecycle owner and the data-quality branch sits with the data team. When the rate moves, the push goes to the owner of the branch that drove it, and the verified impact loop checks whether a change such as a new suppression rule actually improved coordination instead of just shifting the noise to another channel.

There is no single industry target, because coordination depends on how many channels you run and how complete your customer data is. The honest benchmark is your own trend and the band your programme sits in. The ranges below are practical guides for reading the coordinated reach rate, not formal standards.

Improving coordination starts with a unified view of the customer and ends with frequency rules that protect them. The moves below raise the coordinated reach rate without simply sending more, which is the trap most programmes fall into.

1. 1

   Counting reach per channel

   Adding up sends across channels double-counts anyone reachable on more than one. Always deduplicate to one customer record before measuring coordinated reach.

2. 2

   Treating more touches as better

   Hitting a customer on every channel is duplication, not coordination. The metric rewards a consistent message on the right channel, not the highest number of touchpoints.

3. 3

   Ignoring message conflict

   Two channels can each deliver a clean send while contradicting each other. Coordination has to check that the messages agree, not just that they arrived.

4. 4

   Capping frequency within channels only

   A per-channel frequency cap lets the same customer be hit on every channel at once. Caps have to count across channels or fatigue and opt-outs creep up unseen.