Pourquoi l'orchestration compte plus que le volume de messages

Somewhere in the history of business communication, we collectively decided that more is better. More emails. More notifications. More touchpoints. More follow-ups. More "just checking in" messages that nobody asked for and everybody dreads.

It's not working.

Optimove's 2023 marketing frequency benchmarking report found that brands sending more than roughly five marketing messages per week saw engagement drop by over 70%^[1]. Not a gradual decline, but a cliff. Meanwhile, a YouGov survey on push notification preferences found that 47% of consumers feel they receive too many push notifications^[2], with nearly half opting out entirely or deleting the app rather than adjusting their settings. The response to feeling overwhelmed isn't "let me fine-tune my settings." It's "make it stop."

And yet, the instinct to send more persists. It's a deeply human impulse: if a little communication is good, surely a lot must be better. It's also wrong.

The spray-and-pray problem

We've all been on the receiving end of spray-and-pray communication. You sign up for a service, and within 48 hours you've received a welcome email, a "getting started" guide, an invitation to a webinar, a product tips newsletter, a case study, and a "how are you finding things?" check-in from someone named "Alex" who is almost certainly not a real person.

Each of those messages, in isolation, might be perfectly reasonable. Together, they're noise. And noise trains recipients to do one thing extremely well: ignore you.

This is the fundamental problem with volume-based thinking. It treats each message as independent, a standalone attempt to deliver value. But recipients don't experience messages independently. They experience them as a stream, and the quality of that stream is determined by its overall rhythm, relevance, and restraint.

What orchestration actually means

Orchestration is a word that gets thrown around a lot, usually to make "sending messages" sound more sophisticated. But it genuinely means something specific and important.

Think of an orchestra. (Yes, the metaphor is right there in the word; we didn't name it.) A symphony isn't impressive because it has a lot of instruments playing a lot of notes. It's impressive because every instrument plays the right note at the right time, with awareness of what every other instrument is doing.

Communication orchestration works the same way. It's the practice of coordinating timing, context, and channel across every message you send, so that the recipient experiences a coherent, well-paced conversation rather than a barrage.

Timing

Not just "when do we send this?" but "what else has this person received recently, and what's coming next?" If a client got an invoice on Monday, a product update on Tuesday, and a satisfaction survey on Wednesday, Thursday's "thought leadership" email isn't adding value. It's adding weight.

Context

What does this person already know? What have they done recently? If someone just completed onboarding yesterday, they don't need a "tips for getting started" email today. If a client raised a support ticket two hours ago, now is probably not the ideal moment for an NPS survey.

(And yet. We've all gotten that NPS survey. Right after a frustrating support experience. The irony is never lost on the recipient.)

Channel

Email, SMS, push notification, in-app message: each has its own weight and interruption cost. An SMS feels more urgent than an email. A push notification demands immediate attention in a way that an in-app banner doesn't. Orchestration means choosing the channel that matches the message's actual importance, not defaulting to whatever's easiest to send.

Silence as a feature

This is the part that makes marketing teams uncomfortable: sometimes the right thing to send is nothing.

Silence is information. When a service doesn't pester you, it communicates something powerful: "We respect your attention. We'll reach out when we have something worth saying." That restraint builds trust in a way that no amount of "just touching base" emails ever could.

Consider how you feel about the apps on your phone. The ones you trust most are probably the ones that notify you sparingly and meaningfully. The ones you've muted or deleted are almost certainly the ones that couldn't stop talking.

The opposite of good communication isn't silence. It's noise.

An Accenture Strategy study of over 25,000 consumers found that 81% feel loyal to brands that are there when needed but otherwise respect their time and leave them alone^[3]. Customers didn't feel neglected. They felt respected.

The cost of over-communication

Over-communication isn't just annoying. It has real, measurable costs.

• Lost trust: Every irrelevant message teaches the recipient that you don't understand them. This compounds. Trust is easy to erode and expensive to rebuild.
• Unsubscribes and opt-outs: Once someone unsubscribes, you've lost the channel entirely. And they rarely come back. HubSpot's consumer research found that 51% of people unsubscribe because emails come too often, compared to just 9% who say the content is no longer valuable.^[4] Frequency, not quality, is what drives people away.
• Signal degradation: This is the boy-who-cried-wolf problem. If you send urgent-sounding notifications for non-urgent things, people stop paying attention. Then, when something genuinely important happens, your message lands in a graveyard of ignored notifications.
• Internal cost: Every message you send has a production cost: content creation, review, QA, delivery infrastructure. Sending messages that don't deliver value is literally burning money.

A framework for deciding when not to send

We use a simple framework internally when evaluating whether a message earns the right to exist. We call it the three-gate test, and every message needs to pass all three:

Gate 1: Does the recipient need this?

Not "would this be nice to know" or "could this theoretically be useful." Does the recipient actually need this information to do something, decide something, or understand something that matters to them right now? If the answer is "well, not need exactly, but..." then it probably fails this gate.

Gate 2: Does it need to be now?

Could this message wait? Could it be bundled into a digest or summary? Would the recipient's experience be meaningfully worse if they received this information tomorrow instead of today? Urgency should be determined by the recipient's context, not by your content calendar.

Gate 3: Is this the right channel?

Even if the message passes the first two gates, sending it via the wrong channel can undermine its value. A non-urgent informational update sent as an SMS feels intrusive. A time-sensitive alert buried in a weekly email digest is useless. Match the channel's interruption level to the message's actual importance.

If a message fails any of these gates, it doesn't get sent. Not "deprioritised." Not "queued for later." Not sent. And that's fine. The message you don't send can't annoy anyone, can't erode trust, and can't contribute to the growing background noise that makes all your other messages less effective.

What good orchestration looks like in practice

Here's a concrete example. Imagine a client who just renewed their annual subscription. In a volume-oriented system, this might trigger:

1. A renewal confirmation email
2. A "what's new this year" product update email
3. An invoice email
4. A "thank you for renewing" email from their account manager
5. An NPS survey

Five emails in the span of a day or two. Each one defensible on its own merits. Together, exhausting.

An orchestrated approach might look like this:

1. A single renewal confirmation that includes the invoice, a brief "here's what's new" section, and a genuine thank-you note, all in one well-crafted email.
2. An NPS survey sent five days later, after the client has had time to use the product again.

Two messages instead of five. Less effort for you, less noise for them, and almost certainly better engagement on the survey because it arrives when the client can actually reflect on their experience rather than in the middle of an email avalanche.

The shift that matters

Moving from volume to orchestration requires a genuine mindset shift. It means accepting that your communication system's success isn't measured by how many messages you send, but by how few you can send while still achieving your goals.

It means treating your recipient's attention as a finite, precious resource, because it is. Every message you send withdraws from that account. Relevant, well-timed, appropriately channelled messages also deposit something back: trust, value, the sense of being understood. Irrelevant ones just withdraw.

The companies that get this right don't necessarily have better technology or bigger teams. They have better discipline. They ask "should we?" before "can we?" and they're willing to leave messages unsent when the answer is no.

In a world that's only getting noisier, that discipline is becoming a genuine competitive advantage. Not because silence is easy (it isn't, especially when every metric dashboard is screaming at you to send more) but because it's what your customers actually want.

They just don't usually get a chance to tell you, because you've already sent them another email.