# 30 June: Meta Per-Message Pricing Rollout + Utility Free Within Service Window

### ✨ **What’s Changed**

#### **New Per-Message Pricing Model**

1. Starting **July 1, 2025**, Meta is moving from **per-conversation** to **per-message** pricing.
2. Our system has been updated to support this new pricing structure.

#### **How Per-Message Pricing Works**

Charges will apply **per delivered message** based on type:

* Marketing template messages
* Authentication template messages
* Utility template messages *if sent outside the 24-hour customer service window*

Example:

* If you send 1 marketing message and 2 utility messages **outside** the service window you will be charged for **3 messages.** (1 marketing + 2 utility).
* If you send 1 marketing message and 2 utility messages **inside** the service window you will be charged for **1 message** (only the marketing message is charged; utility messages are free inside the window).

[Know More](https://docs.gallabox.com/pricing-and-billing-modules/new-per-message-pricing)

#### **Broadcast UI Update**

The checkbox in **Broadcasts** related to the old pricing model will be **removed.**

#### **Message Credits Page Update**

A new **"Per Message Transaction"** tab will be added to track per-message charges effective from July 1, 2025. The existing **"Conversation Transactions"** will continue to be displayed for 6 months before being deprecated.

This change ensures your Gallabox account is fully aligned with Meta’s new pricing approach, giving you clear visibility into your messaging costs under the updated model.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://changelog.gallabox.com/june-2025/30-june-meta-per-message-pricing-rollout-+-utility-free-within-service-window.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.