Message templates and WhatsApp templates

JollyBee uses the word template for three related but different things.

Reusable message templates

Under Admin → Communications → Templates, save frequently used subject and body copy for a channel. A Campaign can load reusable copy. The current web automation builder uses inline subject and body fields and does not expose a reusable-template picker.

These are JollyBee content records. Saving a reusable template for WhatsApp does not submit it to Meta and does not make it legal to start a cold WhatsApp conversation.

System invitation copy

The Templates area also exposes the supported system invitation email copy. These messages are used by their invitation workflows rather than behaving like a general campaign audience. The invitation destination remains system-controlled. Preserve useful merge variables, edit the button label and copy as needed, and test the actual invite path.

Meta-approved WhatsApp HSM templates

Open the WhatsApp tab to sync or manage templates approved for the connected WhatsApp Business sender. Those templates carry Meta's name, language, category, status and component structure. Only an approved template on the sender that will deliver the message can initiate a conversation outside the 24-hour customer-service window.

A generic JollyBee campaign currently fills supported positional variables in a WhatsApp template's body. It does not provide a general editor for every Meta component, such as media headers, authentication codes or complex button parameters. Choose a simple approved template compatible with the campaign composer and send a test to a controlled number.

Inside an open 24-hour customer-service window, a plain reply or automation message may be accepted without an HSM. That window belongs to the contact/provider conversation, not to the existence of a reusable JollyBee template.