Back to all articlesMessaging cost planning

Choose low, base, and high messaging budgets from explicit assumptions

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A hypothetical messaging budget of 2,500 currency units tells a manager what someone expects to spend. It does not reveal whether that expectation depends on fewer messages being delivered, a cheaper recipient-market mix, or a smaller share of higher-cost message categories. Adding a percentage buffer leaves those dependencies hidden.

Instead, build low, base, and high cases from explicit combinations of delivered volume, recipient market, message category, and verified current rates. Keep platform subscriptions and AI usage separate. Then choose one case for planning and define the forecast change that requires another approval.

The worksheet below makes that decision reproducible. It is not a prediction of delivery or a claim about available Alactic controls.

1. Define the decision before building the scenarios

Start with the question: What spending commitment should we approve for this period, and when must the owner return for a decision? That is different from asking for the largest conceivable bill.

Set a common boundary for all three cases:

  • Period: the same reporting period and billing currency.
  • Activity scope: the same proposed programme, unless expansion is explicitly part of a scenario.
  • Cost scope: Meta messaging charges, provider or platform charges, and AI usage shown separately.
  • Accounting scope: whether taxes, currency conversion, and other fees are included or handled elsewhere.
  • Decision owner: who approves the initial commitment and who can authorise an increase.

Without these boundaries, a low case may quietly exclude a cost included in the high case. That is inconsistent accounting, not uncertainty modelling.

Also distinguish spending from performance. Lower delivery can reduce charges while leaving the business objective unmet. A low-cost case is not automatically a good outcome.

2. Use one calculation structure across all three cases

Meta messaging pricing depends on delivered messages, message category, and recipient market. Check exact rates and applicable exceptions against the current official pricing information. Do not assume every delivered message attracts a charge.

Calculate at the market-and-category level rather than applying one blended rate to all messages:

Delivered messages = planned attempts × assumed delivered share

Chargeable messages in each market/category cell
  = delivered messages allocated to that cell
    minus messages covered by applicable exceptions

Meta messaging cost
  = sum of chargeable messages in each cell × applicable rate

Total scoped cost
  = Meta messaging cost
    + provider/platform charges
    + AI usage cost

The chargeable-message calculation must reflect applicable pricing rules. A single chargeable-share assumption can simplify an early worksheet, but its basis must be recorded. If exceptions differ materially between categories or markets, model them in the relevant cells.

Record the rate-card date and currency. Use the same verified current rates across the cases unless a documented rate change is an explicit uncertainty. Do not inflate the high case with an invented future rate increase.

3. Construct coherent cases, not arbitrary totals

Each case needs an explanation linking its assumptions. The low case represents a plausible lower-spend operating path. The base case reflects the working plan. The high case represents a plausible higher-spend path that managers may need to fund.

Delivery and market mix may move together. Reaching more of the intended audience in a higher-cost market can increase both delivered volume and average cost. Treating those changes as independent may understate exposure.

Category mix also needs an operational explanation. Do not move messages into a cheaper category merely to meet a budget. Model the category appropriate to the intended message and applicable rules.

For each case, explain what changes about the activity or audience, which numerical assumptions follow, and what approval decision that combination supports. If AI work also changes, describe that workload independently rather than increasing its allowance by an unexplained percentage.

These cases are not probability estimates. Without a defensible basis for probabilities, do not average them into an expected bill. Selecting a planning case is a management decision about commitment and tolerance for revision.

4. Filled hypothetical scenario worksheet

Fictional worked example: every quantity, share, rate, cost, threshold, and decision below is hypothetical. Rates are arithmetic inputs, not current Meta or Alactic prices. Markets A and B are fictional planning groups, not actual pricing destinations.

The team considers one period with 100,000 message attempts. The lower-spend path reaches fewer recipients, concentrated in Market A. The base path follows the working audience mix. The higher-spend path reaches more recipients in Market B and includes a larger marketing share.

Category shares are identical within each market. For arithmetic simplicity, 90% of delivered messages in every cell are assumed chargeable. That is not a WhatsApp pricing rule; replace it with the applicable treatment for each cell.

The team separately models AI-assisted work at 1,000, 1,500, and 2,200 task units. These are hypothetical workload estimates for drafting and reviewing follow-up material, not a fixed share of delivered messages. For this example only, each task consumes one fictional planning unit costing CU 0.10. Neither the unit nor its price represents Alactic billing.

HYPOTHETICAL WORKSHEET — ONE PLANNING PERIOD
Currency: CU, a fictional currency unit
Scope: messaging + platform + AI usage
Taxes and currency conversion: outside this example

Fixed illustrative rates per chargeable message:
Market A: utility CU 0.01; marketing CU 0.03
Market B: utility CU 0.02; marketing CU 0.06
Rate basis: fictional; replace with verified current rates

INPUT                              LOW        BASE       HIGH
Planned message attempts           100,000    100,000    100,000
Assumed delivered share                70%        80%        90%
Delivered messages                  70,000     80,000     90,000
Illustrative chargeable share          90%        90%        90%
Chargeable messages                 63,000     72,000     81,000
Market A share                         80%        60%        40%
Market B share                         20%        40%        60%
Utility share within each market       80%        60%        40%
Marketing share within each market     20%        40%        60%
AI task units                        1,000      1,500      2,200
AI cost per fictional unit, CU         0.10       0.10       0.10

CHARGEABLE MESSAGE COUNTS           LOW        BASE       HIGH
Market A / utility                  40,320     25,920     12,960
Market A / marketing                10,080     17,280     19,440
Market B / utility                  10,080     17,280     19,440
Market B / marketing                 2,520     11,520     29,160
Total                              63,000     72,000     81,000

COST, CU                            LOW        BASE       HIGH
Market A / utility                  403.20     259.20     129.60
Market A / marketing                302.40     518.40     583.20
Market B / utility                  201.60     345.60     388.80
Market B / marketing                151.20     691.20   1,749.60
Meta messaging subtotal           1,058.40   1,814.40   2,851.20
Provider/platform                  500.00     500.00     500.00
AI usage                           100.00     150.00     220.00
TOTAL                            1,658.40   2,464.40   3,571.20

Check one messaging cell: base-case Market B marketing volume is 72,000 × 40% × 40% = 11,520 chargeable messages. At CU 0.06, that costs CU 691.20. The four messaging cells sum to CU 1,814.40.

Then reconcile AI separately: 1,000 × CU 0.10 = CU 100; 1,500 × CU 0.10 = CU 150; and 2,200 × CU 0.10 = CU 220. The base total is therefore CU 1,814.40 + CU 500 + CU 150 = CU 2,464.40.

For an operational worksheet, replace the fictional AI basis with the actual metered usage and applicable unit costs. Keep platform charges fixed only if the agreement supports that treatment. Check availability in the relevant workspace and current plan rather than assuming a feature or billing arrangement exists.

Total cost moves from CU 1,658.40 to CU 3,571.20 without any rate increase. Delivery, market mix, category mix, and separately estimated AI workload explain the movement.

5. Attach an approval decision to each case

The following filled decision record completes the hypothetical worksheet and can be reused by replacing its assumptions and owners:

  • Owner: messaging programme lead; finance approver authorises changes to the working commitment.
  • Low case — CU 1,658.40: lower-spend reference, not a saving target. If spending trends here because delivery is lower, review audience reach before reallocating apparent underspend.
  • Base case — CU 2,464.40: approve as the working budget for the stated scope. Report the latest full-period forecast against it.
  • High case — CU 3,571.20: recognise as a plausible funding requirement. Reserve capacity up to a hypothetical CU 3,600 ceiling, but require separate approval before increasing the commitment.
  • Escalation: request a decision when the full-period forecast exceeds hypothetical CU 2,800 or a material assumption becomes invalid.
  • Authority boundary: reserved capacity does not authorise additional activity automatically.

This separates planning, reserved capacity, and permission to spend. Finance can prepare for the high case without granting automatic spending authority.

A manager could choose a higher initial commitment if later funding revisions would be difficult. Alternatively, constrained funds may require a smaller scope. Record the reason. If the high case is unaffordable, specify which discretionary activity could be reduced and who decides; do not simply lower the spreadsheet total.

6. Escalate against the forecast, not just the bill

A trigger based only on posted spend may arrive too late. Use the latest full-period estimate: cost already incurred plus forecast cost of remaining authorised activity. Make pending cost records visible so they do not look like headroom.

The hypothetical CU 2,800 threshold sits above base and below reserved capacity. It is a management trigger, not a platform limit or pricing rule.

An escalation packet should show the revised forecast split into messaging, platform, and AI costs; changed assumptions and their cost effects; remaining authorised activity; and the decision required. Recommend either increased funding, reduced discretionary scope, or correction of a forecasting error.

Also escalate when an assumption becomes invalid even if the forecast remains below the threshold. An unverified rate basis or incorrect category allocation can undermine the forecast before it looks expensive. Any increase in activity still requires the relevant authorisation; this workflow does not imply automatic enforcement or execution by a product.

7. Diagnose misses without rewriting the story

Preserve the approved worksheet and put updated assumptions in a new forecast version. This separates a changed plan from a calculation error.

If spend exceeds base, compare delivered volume at the original mix and rates, then assess market mix, category mix, pricing treatment, and separate platform or AI changes. Attribution order can affect each factor's reported contribution, so use one consistent method.

Watch for these failure cases:

  • Low delivery looks like efficiency. Report delivered volume beside spend and examine whether the intended activity occurred.
  • Every adverse assumption enters the high case. Separate a coherent operating scenario from an extreme stress test.
  • Preparation is counted as delivery. Keep campaign preparation, template review, and actual delivery separate.
  • A cheaper category lacks justification. Correct the category basis and recalculate before seeking approval.

Recipient permission and opt-outs remain constraints. Approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Approval does not guarantee delivery. Automation also needs a clear human escalation path. Check the current WhatsApp Business Messaging Policy for precise requirements; budget approval does not replace them.

8. Test whether another reviewer can use the worksheet

Before approval, ask someone other than the author to reproduce all three totals, identify the rate basis, and explain why the high case costs more. They should also be able to identify the working commitment, escalation threshold, and person authorised to approve an increase.

After the first reporting cycle, compare observed delivery, market mix, category mix, AI usage, and scoped cost with the selected case. Assign an owner to each changed assumption. Update the assumptions that moved rather than hiding the difference inside a larger buffer.

Messaging budgetsScenario planningWhatsAppCost management

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