> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-text-agents/channels/legacy-line-billing.md). # Billing on legacy lines How billing works on WhatsApp lines connected before Dapta moved to connecting directly with Meta. {% hint style="info" %} This page is for customers whose WhatsApp line was connected **before** Dapta moved to connecting directly with Meta. If you connected recently, [WhatsApp billing](/ai-text-agents/channels/whatsapp-billing-and-meta-charges.md) is the page you want. {% endhint %} ## Which lines are these A **legacy line** is one connected through Dapta's previous WhatsApp provider, before new numbers connected directly with Meta. You will find them in **Channels**, on the **WhatsApp (legacy)** card, under **Manage numbers**. | | Legacy line | Direct line | | ----------------------------- | --------------------- | ---------------------------------------- | | Where you find it in Channels | **WhatsApp (legacy)** | **WhatsApp** (directly with Meta) | | Used for new lines? | No | Yes | | Does it keep working? | Yes, unchanged | Yes | | Who charges for the agent | Dapta, in credits | Dapta, in credits | | Who charges for delivery | Dapta, in credits | Meta, in money, to your own Meta account | ## What this means for you * **It keeps working exactly as it does today.** Your agent answers, your templates send, your sequences run. * **One invoice: ours.** Dapta bills messaging in credits alongside everything else. There is no Meta payment method to set up. * **Dapta absorbed Meta's 1 October 2026 increase.** You were not charged a surcharge for it. * **Legacy prices are not changing for now.** If that has to change, we will tell you in advance. * **No retirement date has been announced.** You do not have to reconnect to keep working. ## Prices in credits The cost per message sent, in Dapta credits, by destination country and category. The categories are explained in [Which template type do you need](/ai-text-agents/channels/template-types.md). | Country | Marketing | Utility | Authentication | Service | | ------------------------ | --------- | ------- | -------------- | ------- | | Colombia | 26 | 18 | 16 | 4 | | Mexico | 91 | 56 | 50 | 6 | | Peru | 147 | 88 | 79 | 37 | | Argentina | 129 | 85 | 77 | 19 | | Brazil | 131 | 73 | 66 | 18 | | Chile | 186 | 123 | 110 | 27 | | North America | 52 | 32 | 28 | 18 | | Rest of Latin America | 155 | 103 | 93 | 89 | | Egypt | 225 | 144 | 129 | 38 | | France | 300 | 161 | 145 | 51 | | Germany | 286 | 179 | 161 | 48 | | India | 21 | 9 | 59 | 2 | | Indonesia | 86 | 42 | 285 | 11 | | Israel | 74 | 39 | 35 | 11 | | Italy | 145 | 88 | 79 | 23 | | Malaysia | 182 | 42 | 38 | 14 | | Netherlands | 334 | 167 | 151 | 186 | | Nigeria | 108 | 67 | 60 | 65 | | Pakistan | 99 | 53 | 48 | 30 | | Russia | 168 | 100 | 90 | 83 | | Saudi Arabia | 85 | 53 | 47 | 41 | | South Africa | 79 | 42 | 38 | 35 | | Spain | 129 | 80 | 72 | 77 | | Turkey | 23 | 20 | 17 | 6 | | United Arab Emirates | 71 | 41 | 37 | 40 | | United Kingdom | 148 | 83 | 75 | 81 | | Rest of Africa | 47 | 33 | 30 | 76 | | Rest of Asia Pacific | 153 | 99 | 89 | 47 | | Central & Eastern Europe | 180 | 129 | 117 | 52 | | Middle East | 71 | 41 | 37 | 46 | | Western Europe | 124 | 88 | 79 | 83 | | Other | 126 | 71 | 64 | 30 | ### How templates and service messages are billed * A **Utility**, **Marketing** or **Authentication** template is charged **once per message**. * When the customer replies to a template, or starts a conversation, one **Service** message is charged for the whole conversation. * A conversation covers every message exchanged within **24 hours** of the customer's last message. * If the customer writes again **after 24 hours**, a new conversation opens and a new Service message is charged at the rate for their country. ## Should you move to a direct connection? You can, and for high-volume template sending it is usually cheaper. In exchange you take on the Meta side: your own payment method, and Meta's delivery charges billed straight to you. For comparison only, using 1 USD = 1,000 Dapta credits. A "credit equivalent" is a unit of comparison — Meta charges money, not credits. | Category, Colombia | Legacy line (Dapta credits) | Direct with Meta | Difference | | ------------------ | --------------------------- | ---------------- | ---------- | | Marketing | 26 credits | 12.5 equivalents | \~51.9% | | Utility | 18 credits | 0.8 equivalents | \~95.6% | | Authentication | 16 credits | 0.8 equivalents | \~95% | This is the Colombia example, not a universal rate, and it covers **templates only**. It is not a reduction of your Dapta subscription. Rates differ sharply by country — check yours before assuming the same difference. There is no equivalent percentage for service messages: on a legacy line Dapta's Colombia service charge is 4 credits per conversation, while Meta charges per delivered message. The two cannot be compared as a percentage. {% hint style="warning" %} Moving an existing number is a coordinated change, not a one-click switch. Talk to your Dapta account team before starting so templates, sequences and scheduled sends are checked first. {% endhint %} {% content-ref url="/pages/4UzZiIFvS8tHwW343c2h" %} [WhatsApp billing](/ai-text-agents/channels/whatsapp-billing-and-meta-charges.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dapta.ai/ai-text-agents/channels/legacy-line-billing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.