Turn a messaging plan into a delivered-message cost estimate
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A plan to contact 12,000 people is not yet a messaging cost estimate. Some records will be excluded, some recipients will receive several messages, some planned messages will not be delivered, and some delivered messages may qualify for pricing exceptions.
Build the calculation in four layers: eligible recipients → planned message events → expected delivered messages → applicable chargeable units. Apply rates after those quantities are separate. Then add provider/platform fees and AI usage as distinct cost lines.
The filled worksheet below demonstrates the method. All example volumes, percentages, rates and amounts are hypothetical—not Alactic pricing, current Meta rates or customer results.
1. Define the estimate before entering a rate
Record the planning period, currency, included message steps, recipient markets and expected message categories. State whether the estimate covers one campaign or an entire billing period. Otherwise, a campaign’s messaging charges can accidentally be compared with a subscription covering all activity that month.
For WhatsApp, Meta’s pricing information makes delivered messages, message category and recipient market relevant to the calculation. Check exact rates and applicable exceptions against the current rate card before using the estimate for approval.
HYPOTHETICAL ESTIMATE HEADER Scope: One campaign and associated response messages Period: One planned billing month Currency: USD for illustration Recipient pricing groups: Fictional Market A and Market B Market mix: 70% A / 30% B in every worksheet row Included: Three message steps, messaging fees, platform fee, AI allowance Excluded: Taxes and unrelated campaigns Pricing status: Illustrative; replace before budget approval
The common market mix is a simplifying assumption. If follow-up recipients have a different distribution, give that step its own split. Use the market classification required by the applicable pricing rules rather than guessing from a contact’s current location.
2. Reconcile starting records with eligible recipients
The audience count is an inventory, not a delivered-message or billable-message count. Reconcile it before estimating message events.
In this fictional worksheet, exclusions are mutually exclusive: each excluded record appears in exactly one line. Overlapping exclusions would understate the eligible audience.
HYPOTHETICAL AUDIENCE RECONCILIATION Starting audience records 12,000 Less: permission absent or not established 1,200 Less: opted-out records not already excluded 500 Less: duplicate records not already excluded 300 Eligible unique recipients 10,000
This reconciliation does not authorise sending. Recipient permission matters, and opt-outs must be honoured. Consult the current WhatsApp Business Messaging Policy for precise requirements.
Keep any additional exclusions visible rather than burying them inside a lower delivery percentage. A record deliberately excluded before sending is different from a planned message that does not reach delivery. Keeping those quantities separate makes later changes explainable: removing records changes planned volume, while changing a delivery assumption changes expected outcomes from that volume.
3. Convert the sequence into message events
Give each step its own row. The planning unit is a message event, not a person. One recipient can contribute several events without becoming several audience members.
In this hypothetical plan, the initial message goes to all eligible recipients. A conditional follow-up is forecast for a subset. Associated service responses are counted as outbound message events, not additional unique recipients.
HYPOTHETICAL MESSAGE PLAN Step 1: Initial marketing template 10,000 recipients × 1 message = 10,000 planned events Step 2: Conditional utility template 4,000 forecast qualifying recipients × 1 message = 4,000 events Step 3: Associated service responses 1,000 forecast outbound response events = 1,000 events Total planned message events = 15,000
Category labels are scenario inputs, not determinations that particular messages qualify. Being second in a sequence does not make a message a utility message. Record the qualifying condition behind the follow-up volume; if that condition’s forecast changes, recalculate that row rather than multiplying the full audience by every step.
Approved templates are used to initiate WhatsApp Platform conversations and outside the 24-hour customer-service window. That window opens or resets with a user message. Campaign preparation, template review and actual delivery are separate states; template approval does not guarantee delivery. Any automated response workflow also needs a clear human escalation path.
4. Apply delivery assumptions by step
Use a delivery assumption for each row. Different steps can involve different subsets and conditions. Record the basis, such as comparable internal records, or label the percentage an untested planning input.
All delivery percentages below are untested hypothetical inputs. The two scenarios hold planned volumes constant while changing expected delivery.
HYPOTHETICAL DELIVERY WORKSHEET Step Planned Lower case Higher case Initial marketing 10,000 90%: 9,000 96%: 9,600 Conditional utility 4,000 85%: 3,400 95%: 3,800 Service responses 1,000 90%: 900 98%: 980 TOTAL 15,000 13,300 14,380
Expected delivered messages = planned message events × delivery assumption
These are scenarios, not confidence intervals or guarantees. Higher delivery can produce a higher bill while achieving more of the intended communication. The lower-cost case is not automatically the better operational outcome.
The worksheet also holds the conditional follow-up volume fixed. If your forecast makes follow-ups depend on delivery of the first step, document that dependency and recalculate the qualifying population in each scenario. Otherwise, a seemingly cautious range can contain inconsistent volume assumptions.
5. Map delivered messages to chargeable units
For every row, identify the charging unit, applicable rate and any exception that changes the chargeable quantity. Do not assume all delivered messages produce the same charge.
This fictional model treats all delivered marketing messages as chargeable. It assumes that 50% of delivered utility messages are chargeable in the lower case and 75% in the higher case. Service responses are assigned no Meta messaging charge under an assumed applicable exception.
These shares and exception treatments are hypothetical modeling inputs, not statements of current WhatsApp rules. Replace them with verified treatment for the actual category, market, timing and current pricing exceptions. An unresolved exception belongs in a separate exposure case, not an unexplained zero-cost line.
HYPOTHETICAL META CHARGEABLE-UNIT WORKSHEET Step Lower case Higher case Marketing 9,000 × 100% = 9,000 9,600 × 100% = 9,600 Utility 3,400 × 50% = 1,700 3,800 × 75% = 2,850 Service responses 900 × 0% = 0 980 × 0% = 0 TOTAL CHARGEABLE UNITS 10,700 12,450
The denominator matters: the chargeable share here applies to delivered messages, not audience records or planned events.
A provider may use a different charging basis from Meta. A message with no Meta messaging charge could still contribute to a provider fee under the agreement. Do not reuse one supplier’s chargeable-unit total for every cost line.
6. Complete the reusable cost worksheet
The invented rates below demonstrate the arithmetic only. They are not a verified rate card, quote or indication of Alactic pricing.
HYPOTHETICAL RATES — USD, NOT ACTUAL PRICING Marketing: Market A $0.040; Market B $0.060 per chargeable unit Utility: Market A $0.020; Market B $0.030 per chargeable unit Provider: $0.002 per delivered message, including service responses Platform subscription allocated to estimate: $100 AI allowance: $0.005 per fictional planning unit
For the AI line, define one fictional planning unit as one-tenth of the budgeted AI work for one assisted response event. Assume 300 of the 1,000 planned response events need assistance in the lower case and 600 in the higher case. At ten planning units per assisted event, that produces 3,000 and 6,000 units respectively.
This is an internal accounting convention, not a token measure or an Alactic billing unit. It budgets work performed while preparing responses, whether or not those responses are delivered. Replace it with a documented usage estimate and the applicable billing basis for a real budget.
Apply the 70%/30% market split within each category. This example assumes the utility chargeable share is identical in both markets; otherwise, calculate chargeability by market first.
FILLED HYPOTHETICAL COST WORKSHEET — USD LOWER CASE Marketing A: 6,300 units × $0.040 $252.00 Marketing B: 2,700 units × $0.060 $162.00 Utility A: 1,190 units × $0.020 $23.80 Utility B: 510 units × $0.030 $15.30 Meta messaging subtotal $453.10 Provider: 13,300 delivered × $0.002 $26.60 Platform subscription allocation $100.00 AI: 300 assisted events × 10 units × $0.005 $15.00 TOTAL $594.70 HIGHER CASE Marketing A: 6,720 units × $0.040 $268.80 Marketing B: 2,880 units × $0.060 $172.80 Utility A: 1,995 units × $0.020 $39.90 Utility B: 855 units × $0.030 $25.65 Meta messaging subtotal $507.15 Provider: 14,380 delivered × $0.002 $28.76 Platform subscription allocation $100.00 AI: 600 assisted events × 10 units × $0.005 $30.00 TOTAL $665.91
The hypothetical estimate is $594.70–$665.91, before taxes and excluded costs. It contains 15,000 planned events, 13,300–14,380 expected delivered messages and 10,700–12,450 Meta chargeable units. Those quantities are not interchangeable.
The subscription appears once. If it covers other activity, distinguish an allocated share of total spend from incremental campaign cost. Confirm actual product availability and billing arrangements in the workspace, current plan and provider agreement rather than inferring them from this worksheet.
7. Stress-test what could break the range
The range changes delivery, utility chargeability and AI assistance assumptions. It holds planned message volumes constant and excludes additional reminders, retries and unrelated activity. Test those boundaries explicitly.
- Conditional volume grows: recalculate the follow-up row from the revised qualifying population.
- An exception remains unresolved: calculate a separate exposure case in which uncertain units are chargeable.
- Category treatment changes: update both the applicable rate and exception treatment; changing a label is not a pricing determination.
- Extra sends enter the plan: add message-event rows and evaluate their delivery and charging treatment separately.
- Market mix shifts: reallocate affected units between rate groups, even if total delivery stays unchanged.
- AI work expands: revise assisted-event volume or the documented workload assumption rather than hiding extra usage inside messaging rates.
For a worked sensitivity check, suppose the hypothetical higher-case utility chargeable share rises from 75% to 100%. Chargeable utility units increase from 2,850 to 3,800. At the same market mix, the additional cost is 665 × $0.020 + 285 × $0.030 = $21.85. The revised total is $687.76, with all other inputs unchanged.
That is an exposure case, not a revised likely forecast. Likewise, do not lower delivery assumptions merely to fit a budget target. Reduce or redesign planned activity explicitly.
8. Hand off a traceable budget
Attach an assumption register to the worksheet. Each rate, exception and forecast needs an owner, verification status and date. For this fictional example, the register would begin:
FILLED HYPOTHETICAL ASSUMPTION REGISTER Market mix | Planning owner | Untested: 70/30 on every row Delivery | Operations owner | Untested scenario percentages Meta rates and exceptions | Budget owner | Illustrative; verification pending Provider and subscription | Procurement owner | Illustrative; agreement check pending AI allowance | Workflow owner | 300/600 assisted events; fictional units Verification dates | All owners | Not yet verified
Before requesting approval, check that exclusions reconcile to eligible recipients; every step has a planned-event count; delivery percentages apply to the correct rows; and chargeable quantities follow documented pricing treatment. Keep Meta messaging, provider/platform charges and AI usage separate.
The handoff is ready when the budget owner can trace each total back to its units, rates and assumptions without reconstructing the plan—and no unresolved input is presented as a confirmed fact.
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