ZenotiHelp

Use macros in forms

ZTZenoti Docs Team Updated August 20, 2026 5 min readGuide

Form macros are placeholders you embed in a form template that resolve to actual values when the form is sent to or completed by a guest. Macros let you personalize form text with the guest's name, the class they registered for, the center, and other context — without authoring a separate form per scenario.

Audience: Administrators and managers who configure fitness forms (waivers, custom data forms, feedback forms).

Important: Macros used in forms are not the same as macros used in notifications or House Account statements. The three macro sets resolve in different contexts — a macro that works in a feedback form will NOT resolve correctly when used in a notification template, and a notification macro will NOT resolve correctly inside a statement. Always check the macro reference for the surface you are editing. See class notifications for notification macros and statements for statement macros.


On this page


Before you begin

  • You must have the Edit Forms permission to modify form templates.
  • The macro you insert must resolve to a value at send time. If the macro has no value for the recipient (for example, [MembershipName] when the guest has no active membership), the macro renders as an empty string.

Important: The demographic information (such as addresses and zip codes) that a guest enters into a form does not get updated in the saved guest profile. Macros pull values FROM the profile INTO the form; the form is one-way. If you need the profile updated, edit the guest profile directly.

Three macro sets: do not mix them

Important: Zenoti uses three separate macro sets that resolve in different contexts and are NOT interchangeable:

  • Form macros — Resolve when a form is rendered for a guest. Documented in this article.
  • Notification macros — Resolve when a notification template (email, text, push) fires. Documented in Configure notification template customization.
  • Statement macros — Resolve when a House Account statement template renders. Documented in Statements.

A macro from one set will NOT resolve if used in a different context. Verify which set applies before inserting a macro, and use the table from the relevant article.

Common form macros

Macro Resolves to
[GuestFirstName] Guest's first name.
[GuestLastName] Guest's last name.
[GuestFullName] Guest's full name (first + last).
[GuestCode] Guest's unique guest code.
[Today] The date the form is rendered (in the center's local time).
[CenterName] The center the form is associated with.
[OrgName] The organization name.

Guest information macros

Macro Resolves to
[GuestEmail] Guest's primary email address.
[GuestPhone] Guest's primary phone number.
[GuestAddress] Guest's primary address (line 1).
[GuestCity] Guest's city.
[GuestState] Guest's state or province.
[GuestZip] Guest's postal code.
[GuestDOB] Guest's date of birth (formatted per center locale).
[GuestEmergencyContact] Emergency contact name.
[GuestEmergencyPhone] Emergency contact phone.

Class context macros

These macros resolve when a form is sent in the context of a specific class registration. If the form is sent independent of a class (for example, a general waiver), they render as empty.

Macro Resolves to
[ClassName] The name of the class.
[ClassDate] The date of the class session.
[ClassStartTime] The start time of the class session.
[ClassEndTime] The end time of the class session.
[InstructorName] The assigned instructor's name.
[ClassRoomName] The room name.

Center context macros

Macro Resolves to
[CenterAddress] The center's address.
[CenterPhone] The center's phone number.
[CenterEmail] The center's primary email.
[CenterURL] The center's website URL.
[CenterAddlData1] Additional information about the center. Available in the Additional Text field of the center settings (Settings > Invoice & Receipts).

Feedback macro

The [FeedbackLink] macro generates a personalized URL where the recipient can leave feedback. Use it inside an HTML anchor when embedding in HTML-aware notifications or forms. For example:

<p>Please provide your feedback <a href="[FeedbackLink]">here</a></p>

The feedback text can be anything such as "Share your experience with us" and not necessarily be "Please provide your feedback". However, ensure that the text is correctly written between the HTML tags.

Membership and package context macros

These macros resolve when the form is sent to a member with an active membership or package.

Macro Resolves to
[MembershipName] The member's active membership name.
[MembershipExpiry] The membership expiry date.
[MembershipID] The membership's internal ID (rarely needed in customer-facing text).
[PackageName] The most recent active package the guest holds.
[PackageExpiry] The package's expiry date.

How to insert a macro in a form

  1. At the organization level, click the Configuration icon.
  2. Open Fitness > Forms.
  3. Open the form template you want to edit.
  4. In the form body or field labels, position your cursor where the macro should appear.
  5. Type the macro verbatim — including the square brackets — for example: Hello [GuestFirstName],.
  6. Save the form.

The macro renders as plain text in the editor but resolves to a value when the form is sent to a guest.

Macro resolution at send time

When a form is sent:

  1. Zenoti loads the form template.
  2. For each macro in the template, Zenoti looks up the corresponding value on the recipient's profile and on any associated class/center context.
  3. The macro is replaced with the resolved value before the form is rendered or emailed.
  4. If a macro cannot be resolved (for example, [ClassName] on a guest with no associated class), the macro is replaced with an empty string — not left as the literal [ClassName] text.

Tips

  • Preview before publishing. Use the form preview action to verify all macros resolve correctly for a sample guest.
  • Keep it human. Macros are a tool for personalization, not a shortcut for omitting context. Avoid forms that read like "Hello [GuestFirstName], please complete [FormName] for [ClassName] on [ClassDate]." Write naturally: "Hi [GuestFirstName] — quick waiver before your [ClassName] session on [ClassDate]."
  • Test with edge cases. Send the form to a test guest with no active membership, no upcoming class, and no emergency contact. Verify that the resulting form still reads cleanly when macros resolve to empty strings.
  • Do not nest macros. Macros do not resolve recursively. [Greeting:[GuestFirstName]] will not work; use plain prose with the inner macro: Hello [GuestFirstName]!.
Was this article helpful?
Your feedback helps us improve our documentation.