What Meta prices is a relationship between two timestamps: an outbound message sent when that contact has written nothing in the previous 24 hours [3]. Non-template traffic has been free since November 1, 2024, and utility templates that answer a user inside an open window have been free since July 1, 2025 [4]. A message counter cannot produce that figure, because the billable property belongs to the conversation, not to the row.
Getting it out of a Chatwoot database takes some care. The author uses a window function rather than a correlated NOT EXISTS, on the grounds that the correlated version will exhaust the connection pool on any real messages table [8]. Two details in the query are the actual deliverable. History is pulled for 33 days but counted for only 30, because messages near the boundary otherwise appear to have no preceding inbound and inflate the bill [9]. And the frame is bounded at one row preceding, so a message cannot open its own window [10].
Run it and the naive benchmarks fall apart in a measurable direction. At Israel's $0.0053 utility rate, multiplying all 89,479 messages gives $474.24 against an actual Meta line of $156.89, an overstatement of 3.02x [1]. The more careful mistake, pricing only the outbound half, gives $232.75, still 1.48x too high [2]. That is the difference between a benchmark and an invoice.
The composition of the quote is the part worth sitting with. Twilio's own $0.005 applies to inbound messages as well as outbound, across all 89,479 [11], which makes it $447.40, or 74% of the $604.29 total [3]. The Meta line that everyone models is the smaller quarter. All in, the month blends out to $0.00675 per message [6].
Geography does more work than architecture here. Germany's utility rate is over ten times Israel's [14], so the same 29,602 templates would cost at least $1,568.91 there, above what the Israeli operator would pay if every one of them were reclassified as marketing [5]. Meta makes that classification call, not the sender [18], and the reclassification alone is a 2.47x move on the bill [4].
Two cautions on reuse. The $67.53 and $166.77 figures for a 10,000-message month hold this operator's ratios, 49% outbound and 67% of that outside the window [19][7], and those ratios are exactly what differs between a support desk and a notification pipeline. And the accounting in the material we have is one-sided: the Twilio column is priced to the cent, while the operational cost of running WAHA and Chatwoot yourself is asserted rather than counted.
