This article is designed to guide both new and existing Qualee clients.
Whether you’re just getting started or looking to make the most of your existing setup, this resource will help you quickly understand the different tokens available in Qualee and how they’re used.
Below, you’ll find a complete list of tokens along with clear explanations and examples of when and why to use each one so you can personalize your messages, automate tasks, and improve your employee experience with ease.
Use Case(s)
Single Journeys > Step > Introduction text box
Actions > Introduction text box
Action Sequences > Action > Introduction text box
Single Journey / Journey Sequence Email Notification field
Journey Sequence > Journey Assignment field
Single Journeys (associated in any Journey Sequence)
Personalized Tokens Cheat sheet
Tokens for Single Journeys & Actions
Field | Token |
First name | {first.name} |
Surname | {last.name} |
Date of birth | {date.of.birth} |
Email address | {email.address} |
Start date | {start.date} |
Job title | {job.title} |
Gender | {gender} |
Department | {department} |
Team | {team} |
Location | {location} |
Manager | {manager.name} |
Secondary Manager | {secondary.manager.name} |
Buddy | {buddy.name} |
Custom Segment | {custom.segment} |
Employee ID | {employee.id} |
Employment type | {employment.type} |
National ID | {national.id} |
Employee phone | {phone.number} |
Race | {race} |
Manager's email address | {manager.email} |
Manager's phone number | {manager.phone} |
Manager's bio | {managear.bio} |
Manager's department | {manager.department} |
Manager's team | {manager.team} |
Manager's location | {manager.location} |
Secondary Manager's email address | {secondary.manager.email} |
Secondary Manager's phone number | {secondary.manager.phone} |
Secondary Manager's bio | {secondary.manager.bio} |
Secondary Manager's department | {secondary.manager.department} |
Secondary Manager's team | {secondary.manager.team} |
Secondary Manager's location | {secondary.manager.location} |
Buddy's email address | {buddy.email} |
Buddy's phone number | {buddy.phone} |
Buddy's bio | {buddy.bio} |
Buddy's department | {buddy.department} |
Buddy's team | {buddy.team} |
Buddy's location | {buddy.location} |
Support Tokens for Journey Sequences
Field | Token |
Participant full name | {participant.name} |
Participant date of birth | {participant.birthdate} |
Participant email | {participant.email} |
Participant start date | {participant.startdate} |
Participant title | {participant.title} |
Participant gender | {participant.gender} |
Participant department | {participant.department} |
Participant team | {participant.team} |
Participant location | {participant.location} |
Participant manager | {participant.manager} |
Participant secondary Manager | {participant.secondarymanager} |
Participant buddy | {participant.buddy} |
Participant custom segment | {participant.custom.segment} |
Participant phone | {participant.phone} |
Participant bio | {participant.bio} |
Participant employee ID | {participant.employeeid} |
Participant race | {participant.race} |
Participant national ID | {participant.nationalid} |
Participant employment type | {participant.employment.type} |
*Note:
Supported Tokens for Journey Sequences only works when used in any Single Journeys included in a Journey Sequence and when a user is invited via the Journey Sequence. It does not work when used directly in a Single Journey via direct invitation.
In other words, a Journey Sequence token is designed to display information of employees participating as a direct invitee/participant in a Journey sequence for the other people who are assigned to complete a Single Journey that is a part of the Journey Sequence. Such as managers, secondary manager, buddy, individual or a segment.
For example;
A Journey sequence contains 5 Single Journeys
Journey #1 - Assigned to employee named "John doe" known as direct invitee
Journey #2 - Assigned to Manager named "Max"
Journey #3 - Assigned to Secondary Manager named "James"
Journey #4 - Assigned to Buddy named "Paulo"
Journey #5 - Assigned to {Team} token that includes 3-5 different people
You can use the Support Tokens for Journeys #2-5 and the people invited in those Journeys will/can see John Doe's information
e.g.
Participant full name = John Doe
Participant email = John Doe's email address information
Participant manager = John Doe's primary manager
Preview: Support Journey personalized tokens (Adminstrator/Journey editor view)
Preview: Support Journey personalized tokens (Support Journey participant view)
