WhatsApp Max Price explained: what it changes for buyers
What Twilio launched on November 17, 2026
Twilio said on November 17, 2026 that WhatsApp Max Price is now generally available for marketing messages, according to Twilio (November 17, 2026). For a small B2B sender, that changes one thing: a Marketing template can carry a bid, the most you will pay per delivered message, and Meta charges at or below that bid, so act this month only if the checks in the final section pass.
Max Price is an optional bid cap on Meta's per-message charge for WhatsApp Marketing templates, and it runs alongside fixed-rate messaging rather than replacing it. Twilio's key concepts page says the clearing price Meta sets for each delivery "is always less than or equal to your bid" (Twilio docs).
TL;DR: Max Price is live for USD-billed accounts, applies only to marketing templates, and comes with no published clearing price and no published delivery guarantee. Twilio says Meta has blocked marketing templates to US numbers since April 1, 2025, so a bid cannot change the outcome for those recipients.
Our answer for this month is to act only if you can say yes to three questions: is your account billed in USD, are most of your marketing recipients outside the US, and does one named person own bid changes. If any answer is no, treat Max Price as a watch item for now.
Key Takeaways
Twilio's launch is general availability for marketing templates as of November 17, 2026, limited at launch to accounts and WhatsApp Business Accounts billed in USD.
Meta's own documentation still describes Max Price as beta: open beta from October 1, 2026, with general availability tentatively in Q2 2027. Ask both vendors in writing which status governs your account.
A bid is a ceiling, not a fixed price. None of the vendor pages we read publishes a clearing price or guarantees delivery when a bid loses.
Twilio says Meta has blocked marketing templates to US (+1) numbers since April 1, 2025. Bird lists a US marketing rate and does not mention that block, so the two pages conflict for US recipients.
Platform fees stack on top of Meta's rate. Twilio and Bird both list $0.005 per message.
Meta's docs say bid_spec is accepted only until July 31, 2026, so code that still sends it needs to move to optimization_spec.
What changed for buyers
Before this launch, a marketing message sent through the Cloud API carried a fixed cost set by Meta's published rates. Meta says businesses are only charged when a message is delivered, and that rate card changes take effect only on the first day of a quarter, according to Meta (October 1, 2026). Max Price adds an optional path through the Marketing Messages API in which the cost of each delivered marketing message sits between Meta's auction and your bid. Twilio says you can keep your current bid, bid lower in quiet periods, or bid higher in peak seasons.
Fixed rates stay available. Twilio says that until you accept Meta's Marketing Messages API Terms of Service, you can keep sending marketing templates at fixed rates through the Cloud API (Twilio docs). Accepting those terms is therefore a deliberate step, and it belongs with whoever signs vendor contracts.
Meta separate billing: starts November 1, 2026 according to Meta (2026). Max Price traffic can appear as its own billing line, so finance should know before the next invoice arrives.
The change people tend to miss is frequency. Twilio's docs say Max Price "removes the marketing frequency caps that normally limit how often you can contact a specific WhatsApp user," but they do not define those caps (Twilio docs). Meta's 2025 test of a monthly limit on broadcast messages used "30 messages per month" as one example, according to TechCrunch (2025). That was a broadcast test, not the template rule, so do not read it as the limit for templates. Set your own per-person contact limit before you enable a bid, because the platform will not hold that line for you.
Who is affected: Twilio accounts and WhatsApp Business Accounts billed in USD, from launch. Twilio says other currencies will follow later, and the changelog gives no date for them, so the vendor has not published this. Twilio also says currency settings on existing accounts are permanent, and changing currency requires a new Twilio account and a new WABA (Twilio docs).
The dates that decide what to do
| Date | What the source says | Who is affected | Decide before |
|---|---|---|---|
| April 1, 2025 | Meta blocks marketing templates to +1 US numbers, error 63049 (per Twilio) | Senders with US recipients | Your recipient country mix |
| June 18, 2026 | optimization_spec replaces bid_spec (per Meta) | Code using bid_spec | Migration plan |
| July 31, 2026 | bid_spec accepted only until this date (per Meta) | Same as above | Already passed; migrate now |
| October 1, 2026 | Meta open beta starts; marketing rates rise in 7 markets, none in North America | All marketing senders | Rate review against your invoices |
| November 1, 2026 | Separate billing SKU for max-price traffic (per Meta) | Max Price senders | Invoice line mapping |
| November 17, 2026 | Twilio general availability; USD accounts at launch | USD Twilio accounts and WABAs | Pilot decision |
| Q2 2027 (tentative) | Meta general availability, per its own page | All senders | Written status confirmation |
Meta's own page is the source for the beta and availability rows. The US block row comes from Twilio's changelog, and Meta's pages we opened do not mention it.
Who this is for
Teams already sending Marketing templates through Twilio or Meta's Marketing Messages API, from a USD-billed account.
Senders whose marketing recipients are mostly outside the US, or who have a separate plan for US numbers that does not depend on marketing templates.
Operators who can name one owner for bid changes and one person who reads delivery reports each week.
Red flags: most of your marketing reaches US (+1) numbers; your account bills in a currency other than USD and you cannot switch without a new account and WABA; nobody can own bid changes or review delivery data.
How we evaluated these options
We started with each vendor's own launch, pricing and API pages, then used trade press for context on rate changes. Where a vendor page did not state something, the tables say "not stated on page read," which is not the same as "not offered." We did not run any sends or measure any delivery. The weights below reflect what a small B2B buyer decides on this month. They are our judgment, not a vendor benchmark. For a related approach to vendor price comparison, see a walkthrough on vendor price comparison.
| Criterion | Weight | Why it decides the purchase |
|---|---|---|
| Access today (billing currency, onboarding, early access) | 20% | Twilio's launch is USD-only, and Infobip's access is closed early access |
| Reach to US (+1) marketing recipients | 20% | Twilio says Meta has blocked these sends since April 1, 2025 |
| Bid mechanics (unit, ceiling, country multipliers) | 20% | bid_amount is set per 1,000 deliveries in the smallest currency unit, so a unit error misprices every send |
| Delivery and cost trade-off disclosure | 15% | None of the four vendor pages we read guarantees delivery when a bid loses |
| Edit limits and bid propagation | 15% | Twilio and Meta both allow 100 edits per hour on approved templates |
| Published fees on top of Meta's rate | 10% | Twilio and Bird each list $0.005 per message before Meta's fee |
A sender that reaches almost no US numbers should move weight from the second row into the fourth and fifth rows.
What each option publishes
| Feature | Twilio | Meta (Marketing Messages API) | Bird | Infobip |
|---|---|---|---|---|
| Status on vendor page | General availability, November 17, 2026 | Open beta from October 1, 2026; GA tentatively Q2 2027 | Not stated on page read | Closed early access |
| Who can enable it | USD-billed Twilio accounts and WABAs; accept Meta's terms | Onboarded accounts in eligible countries | No enrollment on your side, per Bird's docs | Through an account manager |
| Bid unit | bid_amount, smallest currency unit, per 1,000 deliveries | bid_amount, smallest currency unit, per 1,000 deliveries | Set per language; unit not stated on page read | Smallest currency unit, per 1,000 deliveries |
| Country adjustment | Not supported; Meta's bid multiplier is not offered | Multiplier above 0 up to 10; up to 240 entries | Country overrides; limits not stated on page read | Multiplier above 0 up to 10; up to 50 countries |
| Edits to approved template bid | 100 per hour; 2,400 per day | 100 per hour; 2,400 per day; content edits 1 per day | Not stated on page read | 10 in 30 days; once in 24 hours |
| Adding a bid to an existing template | Not addressed on pages read | Not addressed on pages read | Not addressed on pages read | Not allowed |
| Error and rejection codes | None published for Max Price | 131061 (wrong endpoint); 131065 (unsupported country) | 131065; no fallback to the standard rate | Bids below about 0.9 times rate card rejected; error 7032 |
| Delivery when a bid loses | Not published | Not stated | Not stated | Very low bids can mean very low delivery |
| US marketing recipients | Blocked since April 1, 2025 (error 63049) | Not stated on page read | US marketing fee listed; block not mentioned | Not read |
Read across a row to see how the options differ. Meta publishes the most detail, including error codes, and it owns the platform, so its dates are the ones to reconcile with Twilio's. Infobip publishes the tightest edit limits. Bird is the only one that publishes a US marketing figure, and it is the figure that conflicts with the block.
Signal vs speculation: what is confirmed and what is our read
Confirmed on vendor or trade pages
Twilio: general availability on November 17, 2026, marketing templates only, USD accounts only at launch, and acceptance of Meta's Marketing Messages API Terms of Service required.
Meta: open beta from October 1, 2026; general availability tentatively in Q2 2027; a separate billing SKU from November 1, 2026; LOWEST_COST_WITH_BID_CAP as the only bidding strategy supported with a bid.
Twilio: Meta blocks marketing templates to US +1 numbers from April 1, 2025, with error code 63049 and no timeline for re-enabling.
Trade press: in 2024 TechCrunch reported that Meta would raise marketing rates while cutting utility rates, using India as the example: India marketing rate: $0.0099 to $0.0107 per message according to TechCrunch (2024). Rate changes matter to any bid plan because the baseline moves.
Our read (not confirmed)
Whether Twilio's general-availability label and Meta's tentative Q2 2027 date describe the same stage for your account. Public pages do not settle it.
Whether a bid will clear often enough to matter. No vendor page we read publishes a win rate, and Infobip warns that bids that are too low can mean very low delivery.
Whether Bird's listed US marketing fee and Twilio's US block can both describe your traffic. They cannot both be complete for US recipients, so one page is out of date or incomplete for that case. We cannot resolve which one from public pages.
Some third-party guides say bids will become mandatory on a 2027 timeline. The Meta pages we opened do not say that, so we did not use the claim.
Our read is that for most small senders the first effect is a cost ceiling plus a new operations task, not a large saving. No published figure sizes the saving, so we do not give one.
Pricing and total cost
Pricing checked November 18, 2026.
Twilio's pricing page says it is current as of September 2026. Twilio fee: $0.005 per message in every category according to Twilio (2026). The same page lists Meta's fee for utility and authentication messages at $0.0034 per message in its US calculator default, and it does not mention Max Price at all.
Meta's rate card is linked from Meta's pricing page as CSV and PDF files. We could not read those files in this session, so this article gives no Meta marketing rate for any country. The page does say that the October 1, 2026 update raised marketing rates in seven markets and listed no North America entries.
Bird's page lists its own fee and a US marketing total. Bird's marketing total: $0.030 per US message according to Bird (page undated). That total is Bird's $0.005 fee plus the $0.025 Meta marketing fee as Bird lists it. The two deposit tiers on the same page cut Bird's outbound fee by 10% and 20%.
Infobip's pricing page says WhatsApp is billed per message and offers custom packages through its sales team. It points to a rate calculator that we did not open, so Infobip appears below as Quote-based (Infobip pricing).
| Cost item (US, USD, per message) | Twilio | Bird | Infobip |
|---|---|---|---|
| Vendor fee | $0.005 | $0.005 | Quote-based |
| Meta fee, utility or authentication | $0.0034 | $0.0034 | Quote-based |
| Meta fee, marketing | Not shown on Twilio's page | $0.025 | Quote-based |
| Total, utility or authentication | $0.0084 (sum) | $0.0084 | Quote-based |
| Total, marketing | $0.005 plus Meta's rate (not read) | $0.030 | Quote-based |
| Volume discount | Not stated on page read | 10% and 20% off outbound fee, by deposit tier | Quote-based |
Totals marked "sum" are our arithmetic on the listed fees. Bird's total is its own published figure.
Worked example (hypothetical, not a quote): suppose a team sends 10,000 marketing deliveries a month to non-US recipients from a USD account and sets a template bid of $0.02 per delivery. Twilio's conversion rule turns that into 2 cents, multiplied by 1,000, which is a bid_amount of 2000. The Meta ceiling is 10,000 × $0.02 = $200, and Twilio's $0.005 fee adds 10,000 × $0.005 = $50, for a ceiling of $250 a month. If clearing prices averaged $0.015, Meta's share would be $150 and the all-in total $200. The $0.015 is an assumption for this example, because no vendor publishes a clearing price. A bid change can take up to one hour to take effect on Meta's side, and approved templates allow 100 edits per hour, so do not change a bid in the middle of a live send window.
Vendor profiles
Twilio Max Price
Best fit: Twilio customers already sending WhatsApp marketing through Programmable Messaging, billed in USD, who want a bid on marketing templates without changing provider.
Limitations: USD only at launch. BRL, EUR, GBP, AUD and MXN are not yet supported, and JPY is not supported. Twilio does not support Meta's per-country bid multiplier, so country adjustments have to be handled another way. Twilio's pricing page does not mention Max Price, and the changelog gives no Max Price price.
Implementation: Set bid_amount on a new Marketing template through the API. Approved templates allow up to 100 edits per hour and 2,400 per day, paused or rejected templates allow unlimited edits, and pending templates allow none. Bid changes do not need Meta re-approval.
Primary evidence: Twilio key concepts and the Twilio launch changelog.
Meta Marketing Messages API
Best fit: Teams with engineering capacity to use Meta's Marketing Messages API directly, or through an onboarded provider, and to manage optimization_spec themselves.
Limitations: Onboarding is required, the destination country must be eligible, and the per-message multiplier is "subject to change during the beta period." Meta returns error 131061 if a max-price template is sent to the Cloud API /messages endpoint instead of /marketing_messages, and error 131065 for bid_spec templates sent to unsupported countries.
Implementation: Use optimization_spec with bid_amount and bid_strategy set to LOWEST_COST_WITH_BID_CAP. The effective bid equals bid_amount times the country multiplier. Multipliers must be above 0 and up to 10, with up to 240 entries, and unlisted countries use 1.0. A bid cap is independent of daily or lifetime budgets.
Primary evidence: Meta's marketing messages pricing page and its rate card and pricing overview (both linked earlier in this article).
Bird
Best fit: Teams that want a published per-message platform fee and deposit tiers, and that do not want an enrollment step on their side, since Bird says max price needs no onboarding.
Limitations: Bird's pricing page lists a US marketing rate and does not mention the US block. Meta rejects max-price sends to unsupported destinations with error 131065 and does not fall back to the standard rate. Marketing templates must be authored on your own WhatsApp Business Account, because Bird's managed catalog includes only authentication and utility templates.
Implementation: Bird's docs say you set the max price per language, in the template editor or through the API. The pages we read do not state a bid unit or an edit limit.
Primary evidence: Bird WhatsApp pricing and Bird marketing templates guide.
Infobip
Best fit: Teams that need per-country bid multipliers for up to 50 countries and can join Infobip's closed early-access program through an account manager.
Limitations: Closed early access. Approved-template bids can change only 10 times in 30 days and once in 24 hours. You cannot add a bid to a template created without one, or remove one from an existing template. Order details and request-contact-info templates do not support bids. Per-message bids below roughly 0.9 times the rate card are rejected, and error 7032 means the bid is below Meta's minimum.
Implementation: Bids are whole numbers in the smallest currency unit of your WABA, per 1,000 deliveries. Estimates are available only for WABAs enabled for max price.
Primary evidence: Infobip max price documentation.
Terms used in this article
Bid cap: the most you will pay per delivered message. The actual charge can be lower.
Clearing price: the per-delivery price Meta sets at or below your bid, according to Twilio's docs.
bid_amount: the bid field, expressed in the smallest currency unit per 1,000 deliveries.
optimization_spec: Meta's template-level setting that replaced bid_spec on June 18, 2026.
LOWEST_COST_WITH_BID_CAP: the bidding strategy Meta requires whenever a bid is set.
Marketing template: the Meta category for promotional messages, and the only category Max Price applies to.
WABA: WhatsApp Business Account, the account that holds your number and your templates.
US block: Meta's block on marketing templates to US (+1) numbers, which Twilio says has applied since April 1, 2025.
Where the bid needs an owner
Max Price is a per-template setting, so the work after launch is operational: deciding which template gets a bid, who approves the number, and what data proves it worked. Two proposed workflows show what a configured process would look like. Neither is live, and neither has been run for any customer. For another side-by-side look at tool choice, see a comparison written for SaaS teams.
A proposed US Tech Automations design would start when a marketing campaign segment is approved in the CRM. The workflow checks each recipient's country code, holds any +1 US number out of the marketing send and places it in a review queue, and for the remaining recipients selects the approved template version whose bid_amount a person has signed off. The output is a send log with each message's status, including the 63049 code that Twilio says marks blocked US sends. Prerequisites are API access to the messaging provider, delivery-status webhooks, and a consent field in the CRM export. Human review points are the bid value, approved by a person before it goes live, and the first send of each new campaign.
A second proposed workflow runs on a weekly cost report. The trigger is the report itself, a scheduled pattern like the one in this scheduled-workflow build guide. The workflow compares delivered counts for each bid-capped template against its ceiling and proposes a new bid, but it does not apply one. The output is a change request with the reason attached. The account owner approves each change, and the workflow keeps every proposal within the 100 edits per hour that Twilio and Meta publish for approved templates.
The main alternative is stitching this together in Zapier, Make or n8n, or writing a script in-house. Zapier's help article describes run statuses such as Errored, Handled error and Scheduled, a Logs tab that shows the HTTP status code and endpoint for an errored step, and replay for failed tasks, according to Zapier. Those tools can support run history, retries and error branches when they are configured. Either way, the buyer still has to design and own idempotency so a retry does not send twice, escalation paths, access controls for who can edit bids, and maintenance when the vendor's API changes.
When not to use US Tech Automations: a simpler setup wins in three cases. If you send only utility or authentication messages, Max Price does not apply, and your provider's console or a short script may be enough. If most of your marketing reaches US numbers, Twilio's own recommendation is to move that traffic to SMS or MMS, which no workflow changes (Twilio changelog). If you can set one template bid by hand and read delivery in the provider console each week, a workflow adds cost without adding control.
Common questions
Is WhatsApp Max Price open to every account?
No, not at launch. Twilio says it covers Twilio accounts and WhatsApp Business Accounts billed in USD, and it requires acceptance of Meta's Marketing Messages API Terms of Service.
Does a bid guarantee that my messages get delivered?
No, and none of the four vendor pages we read says it does. Meta says it charges the max price or less for delivery, but its page does not say what happens when a bid loses, and Infobip warns that bids that are too low can mean very low delivery.
Can I send marketing templates to US numbers now?
Twilio's changelog says no for +1 US numbers: Meta has blocked them since April 1, 2025, and sends fail with error code 63049. Bird's pricing page lists a US marketing rate without mentioning the block, so confirm the position with your provider in writing before you plan any US campaign.
Do I have to rebuild existing templates to add a bid?
Infobip's docs say you cannot add a bid to a template created without one, so you would create a new template. Twilio's docs say to include bid_amount when creating a new Marketing template and do not address existing ones, so ask Twilio before you assume either way.
Is a bid the same as a budget?
No. Meta's documentation says a bid cap is independent of daily_budget and lifetime_budget, so a spend limit is a separate decision you still need to make.
Should I move my whole marketing program to Max Price?
No. Max Price is a per-template ceiling for USD accounts with non-US recipients. Keep the rest of the program on fixed rates until a pilot template has run and its delivery and cost reports have been read.
Act this month only if these checks pass
Confirm that your Twilio account and WABA are both in USD. Currency settings on existing accounts are permanent, so a mismatch means a new account and a new WABA.
Pull the country code mix of your marketing recipients. Any US (+1) marketing send fails under the block, so a bid does not lower its cost or change its delivery.
Find out which template version your code calls. Move any bid_spec usage to optimization_spec, because Meta accepts bid_spec only until July 31, 2026.
Set your own per-person contact limit, because Twilio says Max Price removes the marketing frequency caps.
Name one owner for bid changes. Approved templates allow 100 edits per hour and 2,400 per day on Twilio and Meta, and a change can take up to one hour to take effect.
Get three answers in writing: which status governs your account (Twilio's general availability or Meta's beta), what happens when a bid loses, and how Max Price traffic will appear on your invoice from November 1, 2026.
If all six pass, start with one marketing template on a bid, in a segment with no US (+1) recipients, and read the delivery and cost reports before you widen the bid. To see how a configured version of these checks would be set up, see how US Tech Automations configures this.
About the Author

Helping businesses leverage automation for operational efficiency.