- What Are Custom Tokens?
- Legacy vs New Tokens
- How to Use Tokens
- Token Types
- Client
- Business
- Date & Time
- Purchase Tokens (Integration-based – fitDEGREE, MindBody, Wellness Living, Mariana Tek)
- Appointment Tokens (Integration-based)
- Class Registration Tokens (Integration-based)
- Class Attendance Tokens (Integration-based)
- Class Summary Tokens (Integration-based)
- Form Tokens
- Legacy Tokens (Old Format)
- Helpful Notes
Custom Tokens let you personalize messages in your automations, emails, and SMS.
They automatically fill in details like your client’s name, class info, or appointment time, so you can send one message that feels personal to every client.
What Are Custom Tokens? #
Custom Tokens are placeholders that pull in real-time data from LenzVU or integrations (like MindBody, Wellness Living, Mariana Tek or fitDEGREE).
Think of them as shortcuts that automatically personalize messages.
For example:
Hi {Client::FirstName|there}, your class starts at {ClassRegistration::Time}.
If the client’s first name is “Alex,” the message becomes:
Hi Alex, your class starts at 10:00 AM.
If the name isn’t available, the fallback (“there”) will be used:
Hi there, your class starts at 10:00 AM.
Legacy vs New Tokens #
LenzVU now uses Custom Tokens, which replace the older Dynamic Variables.
You can still use your old tokens, they’ll continue to work.
But the new format is more powerful, flexible, and easier to use.
How to Use Tokens #
You can use Custom Tokens anywhere you write a message, inside:
- SMS
Just type or paste a token where you want the data to appear.
Example:
Hi {Client::FirstName}, your appointment with {Appointment::AssignedStaff} is on {Appointment::Date} at {Appointment::Time}.
Token Types #
We’ve grouped the tokens by what they relate to, so you can find what you need faster.
Client #
Use these to personalize messages with your client’s info.
| Token | Description | Example |
|---|---|---|
| {Client::FirstName} | Client’s first name | “Hi {Client::FirstName}” |
| {Client::LastName} | Client’s last name | “Dear {Client::FirstName} {Client::LastName}” |
| {Client::Email} | Client’s email | “Confirmation sent to {Client::Email}” |
| {Client::Phone} | Client’s phone number | “We’ll call you at {Client::Phone}” |
| {Client::DateOfBirth} | Date of birth | “Happy birthday on {Client::DateOfBirth}!” |
| {Client::DaysToBirthday} | Days until next birthday | “Your birthday is in {Client::DaysToBirthday} days!” |
| {Client::StreetAddress} | Street address | “Shipping to {Client::StreetAddress}” |
| {Client::City} | City | “Located in {Client::City}” |
| {Client::Country} | Country | “From {Client::Country}” |
| {Client::EmergencyContactName} | Emergency contact name | “Emergency contact: {Client::EmergencyContactName}” |
| {Client::CompanyName} | Company name | “Company: {Client::CompanyName}” |
Business #
Use these to reference your business details in messages.
| Token | Description | Example |
|---|---|---|
| {Business::Name} | Business name | “Welcome to {Business::Name}!” |
| {Business::Email} | Business contact email | “Reach us at {Business::Email}” |
| {Business::Phone} | Business phone number | “Call us at {Business::Phone}” |
Date & Time #
These update automatically with the current date and time.
| Token | Description | Example |
|---|---|---|
| {Now::Date} | Current date | “Today is {Now::Date}” |
| {Now::Time} | Current time | “It’s currently {Now::Time}” |
Purchase Tokens (Integration-based – fitDEGREE, MindBody, Wellness Living, Mariana Tek) #
Use these if your account is connected to an external booking or sales platform.
| Token | Description | Example |
|---|---|---|
| {Purchase::Date} | Date of last purchase | “Last purchase: {Purchase::Date}” |
| {Purchase::PackagePurchased} | Name of purchased package | “You bought: {Purchase::PackagePurchased}” |
Appointment Tokens (Integration-based) #
Note: Appointment tokens are not available for Mariana Tek
| Token | Description | Example |
|---|---|---|
| {Appointment::Date} | Appointment date | “Your appointment is on {Appointment::Date}” |
| {Appointment::Time} | Appointment time | “Time: {Appointment::Time}” |
| {Appointment::Name} | Appointment name/type | “Type: {Appointment::Name}” |
Class Registration Tokens (Integration-based) #
| Token | Description | Example |
|---|---|---|
| {ClassRegistration::Name} | Name of the upcoming class | “You’re registered for {ClassRegistration::Name}” |
| {ClassRegistration::Date} | Date of the upcoming class | “Class on {ClassRegistration::Date}” |
| {ClassRegistration::Time} | Time of the upcoming class | “Time: {ClassRegistration::Time}” |
| {ClassRegistration::InstructorFullName} | Full name of the instructor | “Instructor: {ClassRegistration::InstructorFullName}” |
| {ClassRegistration::InstructorFirstName} | First name of the instructor | “Instructor: {ClassRegistration::InstructorFirstName}” |
Class Attendance Tokens (Integration-based) #
| Token | Description | Example |
|---|---|---|
| {ClassAttendance::Name} | Name of the last attended class | “You attended {ClassAttendance::Name}” |
| {ClassAttendance::Date} | Date of the last attended class | “Attended on {ClassAttendance::Date}” |
| {ClassAttendance::Time} | Time of the last attended class | “Time: {ClassAttendance::Time}” |
| {ClassAttendance::InstructorFullName} | Full name of the instructor | “Taught by {ClassAttendance::InstructorFullName}” |
| {ClassAttendance::InstructorFirstName} | First name of the instructor | “Instructor: {ClassAttendance::InstructorFirstName}” |
Class Summary Tokens (Integration-based) #
| Token | Description | Example |
|---|---|---|
| {ClassSummary::TotalClassesAttended} | Total number of classes the client has attended | “You have attended {ClassSummary::TotalClassesAttended} classes” |
| {ClassSummary::TotalClassesAttended:30} | Total classes attended in the last 30 days | “You attended {ClassSummary::TotalClassesAttended:30} classes this month” |
| {ClassSummary::TotalClassesMissed} | Total number of missed classes | “You missed {ClassSummary::TotalClassesMissed} classes” |
| {ClassSummary::TotalClassesMissed:30} | Total missed classes in the last 30 days | “Missed {ClassSummary::TotalClassesMissed:30} classes this month” |
| {ClassSummary::ClassAnniversaryDate} | Anniversary of the client’s first class attended | “Your class anniversary is on {ClassSummary::ClassAnniversaryDate}” |
Form Tokens #
| Token | Description | Example |
|---|---|---|
| {Form::Link?<form_id>:<duration-in-min>} | Link to a form (with expiration) | “Please fill out your form: {Form::Link?10:60}” |
Legacy Tokens (Old Format) #
If you’ve been using Dynamic Variables before, those are now called Legacy Tokens.
They still work exactly the same, so you don’t need to update your existing automations right away.
However, we recommend switching to the new token format for more flexibility and future compatibility.
| Token | Description | Example |
|---|---|---|
| {instructor_name} | Fitness instructor’s name | “Hi {instructor_name}, your class is ready!” |
| {class_name} | Name of the class | “Reminder: Your {class_name} class starts soon.” |
| {class_date} | Date of the class | “Your class is scheduled for {class_date}.” |
| {class_time} | Time of the class | “Your class starts at {class_time}.” |
| {first_name} | Client’s first name | “Good morning, {first_name}!” |
| {last_name} | Client’s last name | “Hello {first_name} {last_name},” |
| {current_date} | Current date | “Today is {current_date}.” |
| {current_time} | Current time | “The time now is {current_time}.” |
| {recent_active_membership_name} | Active membership name | “Your {recent_active_membership_name} membership is expiring soon.” |
| {recent_active_membership_expiration} | Membership expiration date | “Your membership expires on {recent_active_membership_expiration}.” |
Helpful Notes #
Integration tokens only work if your account is connected to that platform.

