Skip to main content
DMLY ships its own set of WhatsApp templates, all named dmly_…. You will find them under Messaging → Templates → System, marked Managed by DMLY. There are around 43 of them and most workspaces only ever need a handful. This page says what each one is and, more usefully, when it is needed, so you can tell at a glance which ones to care about getting approved.

​
The three ways a system template is used

This is the thing to understand first, because it decides whether a template matters to you at all.

Automatic

DMLY sends it itself when something happens: a booking is confirmed, a payment lands. Nothing to set up beyond having it approved.

Automation fallback

It only sends as the out-of-window stand-in for a message inside one specific automation template. Never install that automation and the template never sends.

On request

It stands in when a particular feature is used: a portal login code, a satisfaction rating, asking someone for their phone number.
Two more things apply to every one of them:
  • Category matters. A utility template is transactional and can go to any contact. A marketing template needs the contact’s marketing opt-in and is billed at marketing rates. Meta decides the category in the end, and it holds a few of DMLY’s as marketing however they are declared.
  • Nothing sends until Meta approves it. Submission, approval and what to do about a rejection are all on Message templates.
Not every workspace has every template. A workspace keeps the set it was given when it was created, matched to its business type: a salon is never handed the order-shipping templates. Anything missing is under Templates → System → Available to install. See “A system template I need isn’t there” for the detail.

​
Appointments and bookings

Installed for businesses that take bookings.
The _link versions are the same three messages with a join link. dmly_appointment_confirmation_link, dmly_appointment_update_link and dmly_appointment_reminder_link are utility templates that DMLY picks automatically, instead of the plain version, when the booking has a video or meeting link such as Zoom or Google Meet. You never choose between them. There is no link version of a cancellation. If you run online appointments, install both halves.

​
Sent to your staff

​
Packages and credits

For bookings businesses selling session packs. All three are automation fallbacks, so they only send if you install the matching automation.

​
Payments, invoices and subscriptions

Installed for businesses that take payment.

​
Orders and delivery

Installed for businesses that sell products, or that have a Shopify or WooCommerce store connected.
dmly_order_out_for_delivery, dmly_order_delivered and dmly_cod_confirmation are available, but nothing sends them automatically today. They exist so you can pick them as the out-of-window fallback on a message node in your own automation. Installing them alone changes nothing.

​
Win-back and loyalty

None of these are installed by default. Every one is the out-of-window fallback for one specific automation template, so it only ever sends if you install that automation. All of them are marketing category too, so they need the contact’s marketing opt-in and bill at marketing rates.

​
Team and conversations

Both go to your staff, not to customers.

​
Everything else

dmly_otp is the only authentication template. Meta requires that category for login codes (it cannot be a utility one), and Meta fixes its wording rather than DMLY authoring it.

Message templates

How approval works, and what to do when a template is missing or rejected.

WhatsApp rules and limits

Why a template is needed outside the 24-hour window at all.