> For the complete documentation index, see [llms.txt](https://docs.doku.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.doku.com/subscription-and-billing/paychat/bill-broadcast/template-and-broadcast.md).

# Template & Broadcast

{% embed url="<https://youtu.be/nBRJkHt-kZY?si=of2ta9XpbhADHqRQ>" %}

## Overview

**Template My WhatsApp Business** is a centralized feature where merchants can create, manage, and monitor message templates used for WhatsApp communication. These templates are pre-approved by Meta and ensure consistent, compliant, and scalable customer engagement across various use cases.

Merchants can easily select templates based on their needs—whether for billing, notifications, or promotions—and use them either via dashboard or API. The template management page allows filtering by status, type, and language, enabling faster execution and better organization.

### What You Can Do

* Create and submit templates for approval.
* View the status of each template (Approved, Rejected, or Pending).
* Filter templates by language, type, or status.
* Use templates directly via dashboard (for “Billing” types) or integrate via API (for all types).

### Template Label

With labeled templates, merchants can manage message types more effectively and comply with WhatsApp’s messaging guidelines while maintaining a structured communication strategy.

* Billing: Enables merchants to send payment-linked messages directly through WhatsApp. This is ideal for recurring bills, order invoices, or any situation where payment collection is needed in a seamless, chat-based experience.
* **Receipt**: Automatically send a digital receipt to customers after a successful payment. This helps build trust and provides clear proof of transaction.
* **Promotion**: Share promotional content such as discounts, flash deals, or product launches directly with your customers to boost engagement and sales.
* **Information**: Deliver important information to customers, including updates, alerts, or even authentication-related messages for secure interactions.

### Template Line of Business (LOB)

In PayChat, a **Template LOB (Line of Business)** refers to the business category associated with each WhatsApp message template. This classification helps ensure that all templates comply with Meta’s policies and are aligned with the merchant’s approved business use case.

Template LOB:

* Education
* Retail
* Finance
* Commerce
* Other

### Template Category

* **Marketing**: Promotional messages, offers, and announcements.
* **Utility**: Informational updates, service alerts, or status notifications.
* **Authentication**: Messages for verifying user identity (e.g., login codes).

### Guidance

{% @supademo/embed demoId="cmbyvm36u01lzug0ivxmniv85" url="<https://app.supademo.com/demo/cmbyvm36u01lzug0ivxmniv85>" %}

***

## Bill Broadcast via DOKU Dashboard

Bill broadcast via dashboard enables merchants to send billing messages directly through the [DOKU dashboard](https://dashboard.doku.com/bo/paychat/whatsapp-business)—without the need for any system or API integration. This feature is designed to accommodate merchants who operate without a backend system, allowing them to reach customers efficiently with just a few clicks.

### Terms

1. Merchant has [Activate WhatsApp Business](/subscription-and-billing/paychat/whatsapp-business-waba/activate-whatsapp-business.md)
2. Merchants can perform **bill broadcast** via the  [DOKU dashboard](https://dashboard.doku.com/bo/paychat/whatsapp-business).
3. Merchants must have a sufficient balance to initiate a broadcast.
4. Dashboard-based broadcasts are limited to templates **labeled "Billing"**. For other template types, merchants may use the WhatsApp API. To make a template read [Template & Broadcast](/subscription-and-billing/paychat/bill-broadcast/template-and-broadcast.md)

### Guidance

{% @supademo/embed demoId="cmbyzj8if02gaug0injl78p5x" url="<https://app.supademo.com/demo/cmbyzj8if02gaug0injl78p5x>" %}

***

## Broadcast via API

Bill broadcast via API allows merchants to send billing or transactional messages programmatically using their own system. This method supports **all template types**, offering full flexibility for a wide range of use cases—such as billing reminders, order updates, promotional messages, and more.

By integrating with DOKU’s WhatsApp Business API, merchants can automate broadcasts at scale, personalize messages based on customer data, and trigger notifications in real time. This is ideal for businesses with an existing system or platform seeking a seamless and scalable messaging solution. API access also includes delivery status tracking and message performance reporting.

### Terms

1. Merchant has [Activate WhatsApp Business](/subscription-and-billing/paychat/whatsapp-business-waba/activate-whatsapp-business.md)
2. Merchants must have a sufficient balance to initiate a broadcast.
3. Merchant connect trough the API Below
4. Merchant must have a template message. To make a template message read [Template & Broadcast](/subscription-and-billing/paychat/bill-broadcast/template-and-broadcast.md)

{% hint style="info" %}
You can see more detail about Broadcast Via API [here](https://developers.doku.com/paychat-api/send-whatsapp-message)
{% endhint %}


---

# 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.doku.com/subscription-and-billing/paychat/bill-broadcast/template-and-broadcast.md?ask=<question>&goal=<user_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.
