Set a campaign success threshold before asking for approval
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A brief that says “generate more qualified enquiries” leaves the approver to invent the standard of success. How many enquiries would justify the work? Would confirmed bookings be enough, or must customers have paid? What happens if the campaign creates more replies than the team can handle?
Before asking for approval, separate four things: the desired outcome, the minimum useful outcome, the assumptions supporting the proposal, and the consequences the business will not accept. Add named owners and rules for changes. That turns an attractive objective into a bounded decision.
The worked example below includes a filled worksheet you can adapt. All organisations, roles, quantities, costs and scenarios in the example are fictional and hypothetical, not Alactic customer results or performance benchmarks.
1. Give the approver a decision, not just an objective
An objective describes a direction. Success criteria explain what would make the proposed work worthwhile under stated constraints.
“Increase interest in our onboarding workshop” provides direction but leaves the commitment undefined. It does not explain which outcome matters, what that outcome is worth, or how much effort the business should risk pursuing it.
A decision-ready statement follows this structure:
Approve this campaign to pursue [desired outcome]. We regard [minimum useful outcome] as sufficient to justify [bounded resources], because [business rationale]. The plan depends on [assumptions]. If [material change] occurs, [owner] must pause or seek renewed approval.
This is not a guarantee. It establishes the purpose of the work and the limits of the authority being requested. Keep the desired outcome separate from the minimum: one expresses ambition; the other defines the smallest result worth the proposed commitment.
2. Justify the floor with business value
The minimum useful outcome is not simply the smallest positive number the campaign might produce. It needs a rationale connected to the resources being requested.
For a paid offer, one useful approach is to compare incremental contribution with campaign spending and staff effort. Contribution here means the amount remaining from a sale after its incremental fulfilment costs. An already-scheduled workshop may have spare seats, but filling those seats can still create materials, administration or support costs.
Define the outcome unit before doing the arithmetic. A reply, a relevant enquiry, a reserved place and a paid booking are different commitments. If the value assumption depends on payment, an unpaid reservation cannot satisfy it.
Not every campaign needs a direct financial test. A business might approve a bounded learning exercise or a service initiative using an explicit internal value criterion. What matters is that the approver can see why the proposed floor justifies this particular effort—not merely why any additional interest would be welcome.
3. Reusable filled worksheet: a workshop invitation campaign
Hypothetical planning artifact: A business-services team proposes one WhatsApp invitation campaign for a paid onboarding workshop. The roles below must be assigned to named people before approval. These are recommended operating arrangements, not claims about software controls.
Decision requested
Approve one invitation campaign with a maximum of 900 budget units in incremental cash spending and 18 staff hours. The cash ceiling excludes staff time, which is valued separately below. A second send is outside this approval.
Desired outcome and counting rule
Pursue 12 paid, confirmed bookings for the next workshop. A booking counts only when the coordinator has confirmed suitability and an available place, and payment has been received. Enquiries, unpaid reservations and cancelled bookings do not count toward the threshold.
Minimum useful outcome and its basis
The floor is six paid, confirmed bookings, provided all guardrails hold. Hypothetically, each booking contributes 350 budget units after incremental workshop fulfilment costs but before campaign spending and campaign labour. The workshop is already scheduled; this proposal does not require another session.
The internal approval criterion is that incremental contribution must cover the maximum campaign spending plus staff effort valued at 60 units per hour. At the full allowance, that commitment is 900 + (18 × 60) = 1,980 units. Six bookings contribute 2,100 units, leaving 120 units above that criterion. Five contribute 1,750 units and fall short. Six is therefore the smallest whole-booking floor under these assumptions.
This is a narrow margin, not a generous cushion. The workshop lead must validate the contribution assumption before approval. Any change to price, fulfilment costs or labour allowance requires the rationale to be checked again.
Planning assumptions and launch dependencies
- The proposed audience contains 400 contacts whose permission and suitability for this invitation must be established before launch.
- For planning only, 10% might make a relevant enquiry and 30% of those enquiries might become paid, confirmed bookings: 400 × 10% × 30% = 12. These are unverified assumptions, not forecasts supported by evidence.
- The coordinator confirms 16 available places and checks availability before accepting each booking.
- The invitation is scheduled for Tuesday at 09:00. The campaign coverage period is Tuesday and Wednesday, 09:00–17:00 local business time.
- Any required template approval, audience checks and staffing assignments must be resolved before launch.
- Current charges and other incremental spending must fit within the cash ceiling.
Staff allowance and service commitment
Allocate eight hours to preparation, including audience checks, message preparation, review, handover and scheduling. Reserve ten hours for reply triage, booking administration and escalation. Two assigned staff members share staggered checks across the coverage period; the plan does not assume both work continuously throughout it.
Every campaign reply must receive a human response identifying the next step within two covered business hours. This is not a promise to resolve every enquiry within that period. Time outside 09:00–17:00 does not count toward the commitment. The service lead owns the rota and must arrange an explicit handover for unresolved and later replies when campaign coverage ends.
Capacity triggers and unacceptable consequences
- The service lead escalates when the oldest unanswered reply reaches one covered hour and the assigned staff cannot clear the queue within the next covered hour.
- The campaign owner escalates at 14 total staff hours used, or earlier if forecast remaining work would exceed the 18-hour ceiling. The remaining allowance is not permission to spend beyond the cap.
- No contact with unresolved permission may be included, and opt-outs must be honoured.
- No place may be promised before availability is confirmed.
- No additional send, broader audience, incentive or spending increase is authorised by this brief.
Stop, revise and escalate rules
The campaign owner withholds launch if readiness checks fail. An eligible audience below 300 requires renewed review because it materially reduces the planning margin. This is a chosen review trigger, not a known response-rate boundary.
If a permission issue arises, the owner pauses any remaining campaign sends while it is resolved. If a capacity trigger is reached, the service lead escalates before the allowance is exhausted and prevents further campaign activity that would create additional demand. Already-sent messages cannot be recalled; outstanding replies still require an assigned owner. Additional staffing needs explicit approval.
Approval responsibilities
The campaign owner maintains the brief and requests revisions. The workshop coordinator confirms places and paid bookings. The service lead accepts the response commitment and handover. The budget approver authorises the cash and labour allowances. Approval applies only to this stated scope.
4. Test assumptions without presenting them as evidence
The worksheet makes two different calculations visible. The contribution calculation explains why six bookings would justify the commitment. The audience calculation explains how the team arrived at an ambition of 12. Neither proves demand will materialise.
Give each important input a status: confirmed operational fact, estimate awaiting validation, or unresolved launch dependency. An available-place count checked by the coordinator should not be presented with the same uncertainty as an untested enquiry assumption.
A hypothetical sensitivity check illustrates the distinction. With 200 eligible contacts and unchanged assumed rates, the arithmetic produces six bookings—exactly the floor. That leaves no planning margin. It does not establish that six bookings are likely, and it does not justify lowering the floor.
The contribution assumption also deserves scrutiny. If hypothetical contribution fell to 300 units per booking, six bookings would provide only 1,800 units against the 1,980-unit commitment. The approver would need a revised resource commitment or outcome floor before launch.
If there is no defensible basis for demand estimates, state that uncertainty. A smaller test with its own useful outcome and resource ceiling may be more appropriate than a full campaign supported by precise-looking guesses.
5. Make guardrails operational
“Protect customer experience” is an intention. A guardrail needs a boundary, an observable trigger and an owner with authority to respond. The worksheet’s queue-age trigger gives the service lead a decision point before the response commitment is missed.
Staffing requires particular care: stopping further promotion does not remove replies already arriving. A brief should therefore specify both how additional demand is limited and who retains responsibility for outstanding conversations. If that handover is unavailable, readiness has failed.
For WhatsApp, permission and opt-outs belong in preparation. Approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Check the current WhatsApp Business Messaging Policy for precise requirements. Template approval does not guarantee delivery.
Keep campaign preparation, template review and actual delivery as separate states. A prepared audience is not launch authorisation, and an approved template is not evidence of delivery. If automation is proposed, require a clear human escalation path rather than assuming software will handle exceptions.
Separate provider or platform subscription costs, Meta messaging costs and any AI usage. Meta pricing depends on delivered messages, message category and recipient market; check the current rate card and applicable exceptions. Do not assume every message is billable or apply an unverified fixed rate.
6. Agree conflict and revision rules before launch
Use the approval discussion to resolve conflicting criteria, rather than leaving interpretation to whoever later presents the outcome:
- The desired outcome is reached but a guardrail is breached: the commercial outcome does not erase the breach.
- The minimum is reached but the ambition is missed: the proposal met its floor, not its full target.
- Interest is strong but paid bookings are insufficient: the approved outcome remains unmet.
- Demand exceeds fulfilment capacity: more promotion is not the immediate remedy.
- A launch dependency fails: that is a readiness failure, not evidence of weak audience demand.
Write revision authority into the brief as well. The owner may correct wording before launch if the correction leaves the offer, audience, permission basis and commitments unchanged. Adding a send, offering a discount, increasing resources or expanding the audience requires renewed approval.
These are pre-launch rules, not instructions to improvise a rescue campaign. A revised proposal should show what changed, why it matters and which approval is now requested. It should preserve the original decision record rather than silently rewriting it.
7. Compress the worksheet into the approval request
Once the supporting detail is settled, the hypothetical approval paragraph can read:
Approve one eligible-audience invitation campaign to pursue 12 paid, confirmed workshop bookings, within 900 budget units of cash spending and 18 staff hours. Six bookings are the minimum useful outcome: their assumed contribution of 2,100 units covers the maximum 1,980-unit cash-and-labour commitment. Launch depends on audience permission, capacity, required template approval and the agreed two-day response rota. Demand assumptions are unverified, not promised results. The campaign owner must seek renewed approval for material changes, while the service lead owns capacity escalation and unresolved-reply handover.
For your next brief, fill in the outcome unit, business rationale, resource ceilings and named escalation owners first. The proposal is ready to circulate when the approver can identify what makes the work worthwhile—and where its authority ends—without supplying those answers themselves.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications