On October 15, 2026 HighLevel rebuilt its WhatsApp template builder and added two things that save real work: media headers can now resolve to a different image, video or document for each contact, and a new "limited time offer" template shows a live countdown and a copy-code button inside the WhatsApp message. The per-contact media change means one approved template can serve every customer's own invoice, ticket or personalised image, instead of cloning a template for each asset and waiting for Meta to approve each copy. Details, limits and what to test are below.
What changed in the GoHighLevel WhatsApp template builder?
GoHighLevel rebuilt the WhatsApp template builder into one screen for category, body, media, buttons and variables, used everywhere including AI template generation, with a live phone preview.
| Change | What the changelog says |
|---|---|
| One rebuilt create and edit screen | Category, type, naming, body, media, buttons and variables live together in one redesigned builder, matching the templates and folders experience used elsewhere. |
| Same builder everywhere | AI template generation runs through the same builder, and the builder opened from Reputation uses it too. |
| Live phone preview | The preview updates as you edit header, body, media and buttons and shows how the message lands on WhatsApp. |
| Dynamic media URLs | Media header fields accept custom fields and dynamic values, not only one static public URL. At send time the value resolves for that contact and Meta receives a concrete URL for that message. |
The reason it matters, per HighLevel: previously a different image or document meant a different template, and every new template goes to Meta for approval. Now a single approved template can serve each contact's unique file.
| Before | Now | |
|---|---|---|
| A different file per contact from one template | ✕ | ✓ |
| Live phone preview while building | – | ✓ |
| Countdown offer template | – | ✓ |
| Set the offer expiry when you send | – | ✓ |
Source: HighLevel changelog, October 15, 2026. A dash means the entry does not say
What is the new WhatsApp limited time offer template?
It is a marketing template type with a countdown clock that WhatsApp draws inside the message and a discount code the customer can copy with one tap. HighLevel describes it this way:
- Where you create it. Under the Marketing category in the template builder, with an offer heading, an image header and a body with variables.
- The countdown. Counts down inside the customer's chat to the expiry you set, and turns red in the final hour. It is native WhatsApp rendering, not an image.
- The buttons. A Copy code button and a URL button to your offer. Meta requires both on this template type, so they cannot be removed.
- The expiry. Set when you send, not when you build, so one approved template runs campaign after campaign without new Meta approval between campaigns.
- Where you can send it from. Conversations, bulk actions, workflows and calendar sends.
Who benefits from per-contact media in WhatsApp?
Per-contact media in WhatsApp helps businesses that send a different file to each person, such as order invoices, appointment images, event tickets or listing photos.
| Business | A per-contact file that now fits one template |
|---|---|
| Ecommerce and retail | An order confirmation or invoice PDF for each customer |
| Clinics and med spas | A personalised appointment image or a document for each patient (check privacy rules first; see GoHighLevel and HIPAA) |
| Events and ticketing | A ticket image per attendee |
| Real estate | A listing image for the property each contact asked about |
The examples above are ours; HighLevel's entry mentions invoices, tickets and personalised images.
What should you test before using the new WhatsApp templates?
Before using the new WhatsApp templates, submit each one to Meta for approval, test the dynamic media field with a real file URL, and decide what happens when the field is empty.
- Submit the template to Meta and wait for approval. The update reduces how many templates you need. It does not remove approval.
- Test the dynamic media field. Send to a test contact whose custom field holds a real, public file URL. Confirm the right file arrives.
- Handle empty fields. Decide what happens when a contact has no value in the custom field. Test it. The entry does not describe this case.
- Check consent. WhatsApp marketing needs opt-in. A discount countdown is marketing. Keep your consent records.
- Read the Execution Logs for the workflow that sends it, to confirm the step ran and the message was delivered.
The steps are our recommendation. If WhatsApp messages are not showing in conversations, that is a separate problem we cover for clients through support plans; the automation service builds the sending workflows.
Related updates: the full digest and AI Studio checkout. Messaging costs are in GoHighLevel SMS and email costs.
Frequently asked questions about GoHighLevel WhatsApp templates
Can a WhatsApp template in GoHighLevel send a different image to each contact?
Yes, since October 15, 2026 a WhatsApp template in GoHighLevel can send a different image to each contact. Media header fields accept custom fields and dynamic values, so the file resolves per contact at send time.
Do I still need Meta approval for each template?
Yes, the change reduces how many templates you need, because one approved template can serve many files. It does not remove approval for a new template.
What is a limited time offer WhatsApp template?
A marketing template with a live countdown that WhatsApp draws in the chat and a copy-code button. You set the expiry each time you send.
Can I remove the Copy code or URL button?
No, HighLevel says Meta requires both on this template type.
Where can I send a limited time offer template from?
Conversations, bulk actions, workflows and calendar sends, per the changelog.
Does AI template generation use the new builder?
Yes, HighLevel says AI template generation now runs through the same builder from start to finish.
Is WhatsApp marketing safe to send without opt-in?
No, marketing messages need the recipient's consent and Meta's template rules. Keep opt-in records. We are not lawyers; check your own obligations.