If you've ever built a WhatsApp template, waited for approval, and then needed a second version with a different image, you know the drill. Clone the template, change the image, send it off to Meta, and wait all over again. For every single variation.

That's done. Two changes landed together, and they work hand in hand.

A rebuilt builder with a live preview

Creating and editing WhatsApp templates now happens in one modern layout. Category, type, naming, body, media, buttons, and variables all sit together in a single screen that matches the templates and folders experience you already use.

The same builder runs everywhere you author now - AI template generation uses it, and the builder you open from Reputation uses it too. One interface to learn, not three.

The best part is the live phone preview on the side. As you type your header, body, media, and buttons, the preview updates to show exactly how the message lands on WhatsApp.

Catching a layout problem while you're building costs you a few seconds. Catching it after Meta approves the template costs you a whole new approval cycle. This saves you that.

Media that changes for each contact

Here's the big one. Media header fields no longer need a single hard-coded link. You can now point them at a custom field or dynamic value, and at send time the right image, video, or document resolves for that specific contact.

So instead of cloning a template for every asset, one approved template serves everyone. Send every customer their own invoice, their own ticket, their own personalised image, all from the same template.

And it works across your send surfaces: workflows and automations, conversations, bulk actions, calendar appointments, reputation review requests, and missed call text back.

Personalised images in bulk

This is the use case worth stealing. Pair dynamic media with an image personalisation service like NiftyImages, and a single bulk action renders a unique image for every recipient.

Build the design once with a name placeholder, use the personalised image link as your media header value, and let it resolve per contact at send time.

Shaun opens WhatsApp to an image reading "Here's a special offer for you, Shaun." Varun gets the same design reading "Here's a special offer for you, Varun." One template, one bulk send, thousands of individually rendered images.

It goes beyond names, too. Personalised discount codes, event tickets with the attendee's seat, course certificates, renewal dates, or a product image matched to what that contact last bought.

How to use dynamic media

For per-contact documents like invoices, contracts, or IDs:

1. Store a publicly reachable HTTPS link on a contact custom field.
2. In your template's media or header field, map to that custom field instead of pasting a fixed link.
3. Send from a workflow, bulk action, or conversation. Each contact receives their own file.

For personalised images at scale:

1. Create your image design in a service like NiftyImages, with a placeholder for the contact's name or any other detail.
2. Use the personalised image link as your media header value, with the contact's detail supplied dynamically.
3. Run a bulk action. Every contact receives an image rendered just for them.

One requirement worth noting: the resolved value has to be a publicly reachable link that Meta can download. Private Drive links, anything behind a login, and empty fields will fail. The good news is they fail clearly, so you'll never find out the wrong document went out by hearing it from your client.

Where to find it

• Template builder: Settings, then WhatsApp, then Templates, then Create or Edit.
• Reputation: Reputation, then Settings, then WhatsApp Requests, then Open WhatsApp Template Builder.
• Missed call text back: Settings, then Phone System, then Voice, then Voicemail and Missed Call Text Back, then Customize.

Open Settings, then WhatsApp, then Templates, build one, and try a personalised image on your next bulk send. Once you've done it the first time, you'll wonder how you ever managed cloning a template for every asset.