A customer calls and asks about the new service. They saw the ad, understood the benefit and want to use it.
The person who answers looks for information. One colleague says the offer is only valid at certain locations. Another thinks it starts next week. The campaign page promises one thing, the internal procedure describes another.
The problem is not that the ad did not work. It just brought in someone interested. The problem is that the organization is not ready for the conversation the ad started.
Internal communication is not just the launch announcement
An email, a presentation and a message from management can inform the team. They do not prove that each person knows what to do.
Hearing about the campaign, understanding the promise and being able to deliver it are three different things. For someone at reception, being prepared may mean explaining eligibility. For a consultant, recommending correctly. For operations, being able to handle the volume. For a manager, knowing when the promotion has to be paused or adjusted.
We would not send everyone the same presentation, and we would not consider the problem solved because people confirmed they read it.
Strategy turns the promise into responsibilities
We would start with the public wording and ask what has to be true to support it.
- Who decides?
- Who answers?
- What happens when a customer’s situation does not fit the usual case?
If we promise “simple,” we check how many steps we ask for. If we promise “fast,” we define when the clock starts and what capacity is available. If we promise “personalized,” we clarify what the team can adapt and within what limits.
Sometimes this discussion confirms the message. Other times it shows that the process needs to change or the promise needs to be narrowed. We would rather find the gap before we buy distribution.
A demonstration: “A quote in 24 hours”
Suppose, in a hypothetical example, that a home renovation company wants to promote a quote in 24 hours. But the calculation requires measurements, photos and a conversation about materials.
What do the 24 hours mean, then?
- The first reply?
- A rough estimate?
- A final quote once all the information has arrived?
- Are they calendar hours or business hours?
We would not treat these questions as fine print. They define the service being bought and the team’s work.
| Possible promise | What would need to support it | What we would check |
|---|---|---|
| “You get a first reply within one business day.” | A clear owner for inquiries and coverage during the stated hours. | Is the reply useful or just an automatic confirmation? |
| “You get an estimate once the brief is complete.” | A clear brief, completeness criteria and an estimating method. | Does the customer understand it is not yet the final quote? |
| “You get a final quote by the confirmed date.” | Sufficient data, technical validation and available capacity. | Who confirms the date and communicates any changes? |
There is no universally correct option. The choice depends on the actual service. Once it is clarified, the ad, the form, the phone answer and the confirmation message have to describe the same option.
What we would prepare before launch
We would propose a short promise sheet: who it is for, what it includes, what it excludes and who handles exceptions. We would adapt the instructions by role and keep a single source of information, with an owner for updates.
Then we would test a few situations: a customer without all the details, a request from outside the service area, a request that exceeds capacity and a complaint about the message. Not as a memory test, but as a check of the process.
If the right answer requires approval from someone who is unavailable, we have a dependency to resolve. If the team has no access to information or tools, another communication session will not fix the gap.
We listen before we ask for enthusiasm
The people who talk to customers every day can spot ambiguous wording and exceptions the campaign presentation left out. We would create a feedback path before and after launch, with clear responsibility for responding.
We would not confuse the team’s reservations with a lack of commitment. Sometimes the person who says “we can’t promise that yet” is protecting both the customer and the brand.
Likewise, we would not automatically turn employees into distributors of the campaign on their personal accounts. Understanding and delivering the promise come before the appearance of public enthusiasm.
What we would measure
Opens of internal materials can show how information was distributed. They do not prove readiness. We would check answers to concrete situations, unnecessary transfers, contradictory information and whether communicated deadlines are met.
If delays appear, we would analyze the cause: lack of clarity, capacity, tools or decision-making. We would not blame every problem on the employee who last spoke with the customer.
Before a large launch, we could propose a pilot with one team or one location. The criteria for expanding would be agreed with operations and tied to real capacity, without thresholds invented to look good in a report.
How we would approach the project
At NOT MORE., we would connect the brand promise with the instructions, materials and touchpoints it requires. The company would validate the procedures, resources and decision-making authority. We would not pretend that a communication project can replace operational management.
The difference would be when we bring the team into the conversation: before launch, when their observations can still change the message and the experience.
The people in the company should not be the last to learn what the brand has promised on their behalf.
Are you preparing a campaign or a new service? Let’s also check what the team that will deliver it needs to know, be able to do and be able to decide.