Skip to content
BitByteCore ConnectBook a demo
Open the product menu

Guide · Templates · For the owner who wants utility messages running fast

WhatsApp's Template Library: Meta's pre-written delivery, payment and passcode templates, what you can change, and why a library message can fail at send time

Most of what a business needs to send on WhatsApp is not original. An order is confirmed, a parcel is delayed, a payment is due, a code has to be typed in. Meta keeps a library of templates for exactly these messages, already written and already approved as utility or authentication, so a business fills in the blanks instead of drafting from scratch and waiting on review. Here is what Meta's page says the library holds, how a template is taken from it, what the business can and cannot change, and the one catch that makes a library message fail at the moment of sending.

Published 1 October 2026

What the library is

Pre-written and pre-categorised
Meta describes the library as utility templates for common use cases such as payment reminders and delivery updates, plus authentication templates for verification codes. Each is already classed as utility or authentication, so the question of which category a message falls in, and the risk of Meta reclassifying it, is settled before the business touches it.
Fixed words, open blanks
A library template has fixed content that cannot be edited and parameters that can: the customer's name, the business's name, an order reference, an amount, a date. The business supplies the blanks; the sentence around them is Meta's.
Where it lives
In WhatsApp Manager under Message Templates: Create Template, then Browse Templates. Meta's page says to search by topic or use case or filter from the sidebar, hover a template to see its parameters, pick one, give it a name and a language, fill in the button details and submit. The same library is reachable by a provider's system through Meta's interface.

Customise it and you are back in the queue

Meta's page carries one plain warning: choose Customize template on a library template and it has to go through review before it can be sent, like any template the business wrote itself. The point of the library is to use it as written. If the wording does not fit, that is a sign the message belongs in the ordinary template route described in the template mechanics guide.

The catch: Meta checks the blanks when you send

Because the wording is Meta's, Meta also polices what goes into the blanks. The page says a message sent from a library template is subject to parameter checks at send time, and a value outside the allowed range makes the send fail. Each blank has a type, and Meta's advice when a send fails is to try again with a shorter value.

The types
Address, which must be a valid address; plain text; an amount, which may carry a currency prefix or suffix, decimals and commas; a date in any ordinary written form; a phone number with its spaces, dashes and plus sign; an email address, which must be valid; and a bare number with no spaces. All of them are length-limited.
What it means for the owner
The data feeding the template has to be clean before the first send. A delivery update whose address field holds a note to the driver, or a reminder whose amount field says 'see invoice', fails at Meta rather than arriving garbled. That is a feature, but it has to be known about before a campaign, not discovered during one.
Attachments
Where a library template has a document header, Meta's page says only PDFs are supported.

Forms, for businesses that have earned them

Some entries in the library are not messages but short interactive forms, built on WhatsApp Flows and marked with a Form label in WhatsApp Manager. Meta's page lists two current uses, customer feedback and delivery failure, and says forms are available only to accounts whose messaging limits have been increased. A new number on its starting limit does not see them. What a messaging limit is and how it rises is covered in the messaging limits guide, and what a Flow is in the Flows guide.

What is on the shelf

  1. Two industries, four topics. Meta's filters name e-commerce and financial services as the industries, and account updates, customer feedback, order management and payments as the topics. A clinic or a school will still find the order and payment templates usable; the library is organised by the shape of the message, not the trade.
  2. More than twenty use cases. Among them: order confirmation, order delay, order ready for pick-up, delivery confirmation, delivery update, delivery failed, return confirmation, shipment confirmation, payment due reminder, payment overdue, payment confirmation, payment failed, payment scheduled, auto-pay reminder, account creation confirmation, fraud alert, low balance warning, transaction alert, statement available, receipt attached, and feedback survey. Each is a utility message, the category explained in the template categories guide.
  3. Authentication, separately. The library's one-time passcode templates are the ones Meta already expects businesses to use, and the authentication guide covers their buttons and limits.
  4. Buttons need your details. Where a library template has a website or call button, the business's website address or phone number has to be supplied when the template is created; Meta's page says that for such templates this is not optional.

A newer route, in which Meta writes utility templates on the fly from a plain message, is a separate thing and is described in the Direct Send guide. The library is the older, broader shelf; Direct Send is the shortcut for the handful of messages it supports.

Questions

Do library templates still need Meta's approval?

Used as written, Meta's page describes them as pre-categorised and ready to create from the library. Change the wording with Customize template and the result goes through the normal review before it can be sent.

Can we send a marketing offer from the library?

No. Meta's page describes the library as utility and authentication templates, and via Meta's interface the category for a library template must be utility. Promotions use marketing templates, written by the business and reviewed.

A library message failed although the template is approved. Why?

Most likely a blank held a value outside its type or length: text where an amount should be, an address that is not an address, a field that is too long. Meta checks library parameters at the moment of sending and fails the message rather than deliver it. Meta's advice is to retry with a shorter, correctly typed value.

Why can we not see the feedback form in the library?

Meta's page says the form templates are available only to accounts whose messaging limits have been increased. A number still on its starting limit does not see them; they appear as the limit rises.

Sources

More plain-language notes like this one are on the guides page.

Want your delivery and payment messages running this week?

We set up a business's WhatsApp number on a proper system, pick the library templates that match its order, delivery and payment steps, map each blank to clean data so sends do not fail Meta's checks, and reserve custom templates for the messages the library does not cover. A short call is the easiest way to see whether it fits your business.

Book a demo