ZenotiHelp

Notification Templates

ZTZenoti Docs Team Updated November 3, 2026 8 min readGuide

Notification templates define the reusable email, SMS, WhatsApp, and push messages that AI Lead Manager sends from your workflows. This article explains the template types, how to create and design a template, how to insert dynamic macros, how to send test notifications, and how template versioning works.

Audience: Administrators who configure lead communication for the organization.


On this page


Before you begin

  • Your organization must have AI Lead Manager enabled.

  • Notification templates are an organization-level configuration. A template you create is available to every center in the organization β€” templates cannot be defined per center.

  • You need the following permission to view and manage settings:

    Permission: View on Lead Settings β€” Required to access AI Lead Manager configuration. Admin path: Lead Management > AI Lead Manager > Lead settings

  • To use a notification template in automation, you also need an active workflow with a Send Email or Send SMS action node. See Create and publish workflows.

  • For email templates, the lead must have a valid email address and must have consented to receive email notifications. For SMS templates, the lead must have a valid phone number and must have consented to receive SMS messages. If either condition is not met, the send step fails or is skipped.

How notification templates work

A notification template is a saved message that a workflow sends automatically when a lead reaches a Send Email or Send SMS action node. AI Lead Manager supports four channels:

  • Email β€” Rich messages designed with a visual drag-and-drop editor.
  • SMS β€” Plain-text messages with macro support.
  • WhatsApp β€” WhatsApp messages.
  • Push β€” Push notifications.

When a workflow reaches a send action, Zenoti resolves the template's macros against the lead and workflow context β€” for example, [LeadName] becomes the lead's full name β€” and then delivers the message through the configured provider. If the lead has no email address or phone number for the chosen channel, the step fails with a validation error. If the lead has not consented to receive notifications, the step is skipped without error.

Template types

AI Lead Manager recognizes five template types. You can only create and delete Custom and Inline templates. Basic and Themed templates are protected so the system-provided messages stay intact.

Template type Description Can you create it? Can you delete it?
Basic System-provided default template No No
Themed Pre-designed template No No
Custom A reusable template you build and save in your library Yes Yes
Inline A template embedded directly in a single workflow step Yes Yes
Draft A template that has not yet been finalized β€” β€”

Steps

Create a notification template

  1. Go to Lead Management > AI Lead Manager > Workflows.
  2. Open the workflow you want to edit, or select Create workflow to start a new one.
  3. Add or select a Send Email or Send SMS action node on the canvas.
  4. Select Create new to begin creating a new template.
  5. Choose the channel for the template β€” Email, SMS, WhatsApp, or Push.
  6. Enter a name in the Template Name field.
  7. For SMS, WhatsApp, and push templates, enter the message body. For email templates, enter a subject, then design the message body using the visual editor (see Design an email template with the visual editor below).
  8. Insert macros wherever you want dynamic, lead-specific content (see Available macros).
  9. Select Save to save the template to your library.

Note: The channel you choose at creation cannot be changed later. To send the same message on a different channel, create a separate template for that channel.

Select an existing template

  1. Go to Lead Management > AI Lead Manager > Workflows and open the relevant workflow.
  2. Select a Send Email or Send SMS action node.
  3. Use the Basic, Themes, or Custom tabs to browse available templates.
  4. Select a template to preview it, then select Continue to apply it to the action node.

Design an email template with the visual editor

Email templates use a visual drag-and-drop editor for rich design. Within the editor you can:

  • Build the layout with drag-and-drop content blocks.
  • Apply a responsive design that adapts to different screen sizes.
  • Switch to an HTML/CSS editing mode for fine-grained control.
  • Upload and manage images.
  • Preview the message in real time by selecting Preview.
  • Save and reuse custom blocks and modules.
  • Insert merge tags that map to notification macros using the Add Macros button β€” these resolve to the same lead values as the macros described in Available macros.

SMS, WhatsApp, and push templates use plain text and do not use the visual editor.

Add macros for dynamic content

Macros are placeholders that pull live values from the lead and workflow context when the message is sent. Insert a macro by selecting Add Macros and choosing from the macro catalog, or by typing the macro name directly β€” for example, [LeadName] β€” at the point in the message where the value should appear.

The macro catalog is maintained centrally via the macros service, so new macros can become available without any change to the editor. See Available macros for the current set.

Send a test notification

Before you rely on a template in production, send a test to confirm the content and macro resolution appear correctly.

  1. Open the template you want to test inside the workflow action node.
  2. Select Send Test Email or Send Test SMS depending on the channel.
  3. In the Select employees picker, choose a recipient. The picker is pre-loaded with employees from the current view:
    • Center or general view β€” shows employees for the current center only.
    • Organization or zone view β€” shows employees across all centers in scope. When you select a recipient in these views, the employee's associated center is included in the request so the sender address can be resolved correctly.
  4. Send the test.

Important: Test sending is rate-limited to 50 test notifications per user per 24 hours. If you reach the limit, Zenoti displays a message indicating the quota has been exceeded. Wait until the 24-hour window resets before sending more tests.

Search for a template

Use search to find an existing template by name or content. Matching is case-insensitive and partial:

  • For SMS templates, search matches the template name and body.
  • For Email, WhatsApp, and push templates, search matches the template name and subject.

Delete a template

You can delete only Custom and Inline templates. Basic and Themed templates are protected and cannot be deleted. Deleting a template does not affect messages that have already been sent β€” those records reflect the version that was active at send time.

Important: Deleting a Custom template that is currently referenced by a published workflow will cause that workflow's send step to fail at runtime. Verify no active workflows depend on the template before deleting it.

Available macros

The following macros are available for use in any template. Each macro is resolved from the workflow execution context using a JSONPath expression at send time. The catalog is extensible, so additional macros may appear without requiring an app update.

Macro Resolves to
[LeadName] The lead's name
[Email] The lead's email address
[Phone] The lead's phone number
[AssignedTo] The employee the lead is assigned to
[LeadSource] The lead source
[LeadStage] The lead's current stage
[LeadType] The lead type
[LeadPriority] The lead's priority
[CenterName] The center associated with the lead
[CreatedDate] The date the lead was created
[LastContactedDate] The date the lead was last contacted
[FollowUpDate] The lead's follow-up date
[LeadScore] The lead's AI score
[LeadNotes] The lead's notes
[CustomFields] Values from custom lead fields

Worked example: To build a follow-up email for a guest named Maria Lopez assigned to Priya at the Downtown center, you might write a subject of We'd love to see you back, [LeadName] and a body of Hi [LeadName], thanks for your interest at [CenterName]. Your dedicated consultant [AssignedTo] will follow up with you on [FollowUpDate]. When the workflow sends the message, it resolves to: "Hi Maria Lopez, thanks for your interest at Downtown. Your dedicated consultant Priya will follow up with you on the scheduled date."

How template versioning works

Notification templates are versioned to preserve a history of what was sent and when.

  • When you update a template, Zenoti does not overwrite the existing version. Instead, it marks the previous version inactive and assigns the new version a new template ID.
  • The channel of a template cannot change across versions. If you need to send the same content on a different channel, create a new template for that channel.
  • Because each update creates a new version, messages that were already sent continue to reflect the version that was active at the time they were sent.
  • Only Custom and Inline templates can be updated through the editor. Basic and Themed templates cannot be updated.

Tips

  • Name templates descriptively. Use names that include the channel and purpose β€” for example, "Follow-up SMS β€” High priority" β€” so team members can identify the right template quickly when building workflows.
  • Test with a real employee account. When you send a test notification, choose an employee whose contact details are fully configured so you can verify both delivery and macro resolution in the actual message.
  • Create one template per channel. If you want the same message sent by both email and SMS, create two separate templates β€” one per channel β€” and connect each to its respective action node in the workflow. Mixing channels in a single template is not supported.
  • Review templates before deleting. Before deleting a Custom or Inline template, search for workflows that reference it and update those workflows to use a different template. Deleting a template referenced by an active workflow causes that send step to fail.
  • Use the visual editor's preview feature. Select Preview inside the email editor to see how the message will appear on desktop and mobile before saving. This helps catch layout issues before the template reaches guests.

Troubleshooting

Problem Likely cause Resolution
The send step fails at runtime with a validation error The lead has no email address or phone number for the selected channel Open the lead's Details tab and add the missing contact information, or update the workflow to check for contact data using a Branch condition node before the send step
The send step is silently skipped The lead has not consented to receive notifications on this channel Confirm the lead's consent status in the lead record. If consent was not captured, update the lead's consent settings or use a custom form with a consent field
Macros appear as literal text in the received message The macro syntax is incorrect or the field has no value for this lead Check that each macro uses the exact format shown in the Available macros table. If the lead field is empty, populate it before the workflow runs
Test send fails with a rate limit message You have sent 50 or more test notifications in the past 24 hours Wait until the 24-hour window resets, then retry
A published workflow no longer sends email after a template update The template was deleted or the new version has a configuration error Open the workflow's Send Email node and verify that a valid template is selected. Re-save or republish the workflow if needed
Was this article helpful?
Your feedback helps us improve our documentation.