Why Tokens?
One of the things that makes Táve so powerful 💪 is your templates. In order for templates to be powerful, you'll want to build out some of these templates with placeholders where your clients' data will go. In Táve, we call these Tokens.
Tokens can be used in emails, contracts, and questionnaires to quickly personalize documents and emails for everyone you work with, without having to create them from scratch for every client. If that's not enough time-saving power for you, you can even use them in automations.
Understanding Tokens
Every token will begin with a prefix telling you what that token is for. It's important to make sure you have the right prefix when you're using tokens as this tells Táve where to get the information from. An example would be {{primary_contact.name}}, which would be a placeholder for the full name of the Primary Contact. Once you have your prefix selected, grab the token you want to use, use it as a placeholder, and Táve will automatically fill it with the information you've previously gathered.
You can search for a token anywhere you see the token lookup icon:
People Tokens
Job Role Tokens
Every job role in your Táve account will have a set of tokens attached to it by default. Here's a list of some of the popular ones below. There are a lot more and you can see a full list of all standard contact tokens here. In this case [prefix] = Job Role Prefix (i.e. primary_contact, secondary_contact, etc.).
If you're not sure what a job role's token prefix is, you'll find it here in Settings › Job Roles.
{{[prefix].address}} - The address of the contact
{{[prefix].birthday}} - The birthday of the contact
{{[prefix].cell_phone}} - The cell phone number of the contact
{{[prefix].company_name}} - The company name of the contact
{{[prefix].custom.[custom-field-token]}} - Any custom fields you've created for contacts will show here
{{[prefix].email}} - The email address of the contact
{{[prefix].facebook}} - The Facebook username of the contact
{{[prefix].first_name}} - The first name of the contact
{{[prefix].home_phone}} - The home phone number of the contact
{{[prefix].instagram}} - The Instagram username of the contact
{{[prefix].last_name}} - The last name of the contact
{{[prefix].mailing_address}} - The mailing address of the contact
{{[prefix].name}} - The full name of the contact
{{[prefix].portal_linked}} - A link for this contact's Client Portal
{{[prefix].tiktok}} - The TikTok username of the contact
{{[prefix].url}} - The URL of the contact's website
{{[prefix].work_phone}} - The work phone number of the contact
In any of the token lookups, you can search by your job role to see all the tokens available to choose from:
Recipient Tokens
When you're sending an email, sometimes the job role can vary depending on who the recipient of the email is. In Táve we have tokens just for recipients. To help, you can replace [prefix] with recipient to use any of the above tokens for each recipient of the email, for example {{recipient.first_name}} will automatically populate with the first name of whoever the email has been sent to (i.e. the recipient of the email).
Another great one to use is {{recipient.portal_linked}} which will populate with the link to the client portal of the person the email was sent out to (i.e. that recipient's own client portal link to login).
Want to grab this email client portal introduction email template? Install it directly from the Template Gallery here.
Event Tokens
Event Type Tokens
Every event type in your Táve account will have a set of tokens attached to it by default. Here's a list of some of the popular ones below. There are a lot more and you can see a full list of all tokens here. In this case [prefix] = Event Type Prefix (i.e. wedding_coverage, consultation, etc.).
If you're not sure what an event type's token prefix is, you'll find it here in Settings › Event Types.
{{[prefix].address}} - The address of the event
{{[prefix].attendees}} - A comma separated list of all attendees
{{[prefix].attendees_clients}} - A comma separated list of all attendees that are clients
{{[prefix].attendees_clients_subjects}} - A comma separated list of all attendees that are clients or subjects
{{[prefix].attendees_subjects}} - A comma separated list of all attendees that are subjects
{{[prefix].attendees_team}} - A comma separated list of all attendees that are team members
{{[prefix].duration}} - The duration of the event (XX hours, XX minutes)
{{[prefix].end}} - The end of the event. IE - 'MM/DD/YYYY @ HH:MMam/pm' (Can change depending on account date format settings)
{{[prefix].end_date}} - The end date of the event. IE- 'MM/DD/YYYY' (Can change depending on account date format settings)
{{[prefix].end_date_long}} - The end date of the event (DAY OF WEEK, MONTH DAY, YEAR)
{{[prefix].end_time}} - The end time of the event (HH:MMam/pm)
{{[prefix].location.name}} - The name of the location for the event
{{[prefix].location.phone}} - The phone number for the location for the event
{{[prefix].map_link}} - The location name linked to the location on Google Maps
{{[prefix].map_url}} - A link to the location on Google Maps
{{[prefix].name}} - The name of this event
{{[prefix].notes}} - Any notes you've taken for this specific event
{{[prefix].start}} - The start of the event IE - 'MM/DD/YYYY @ HH:MMam/pm' (Can change depending on account date format settings)
{{[prefix].start_date}} - The start date of the event IE- 'MM/DD/YYYY' (Can change depending on account date format settings)
{{[prefix].start_date_long}} - The start date of the event (DAY OF WEEK, MONTH DAY, YEAR)
{{[prefix].start_time}} - The start time of the event (HH:MMam/pm)
{{[prefix].sunrise}} - The time of sunrise at the location address for the event's date
{{[prefix].sunset}} - The time of sunset at the location address for the event's date
{{[prefix].weather.humidity}} - The humidity for the event location on that date
{{[prefix].weather.precipitation}} - The precipitation for the event location on that date
{{[prefix].weather.temperature}} - The temperature for the event location on that date
{{[prefix].weather.wind_speed}} - The wind speed for the event location on that date
In any of the token lookups, you can search by your event type to see all the tokens available to choose from:
Primary Session Tokens
Some types of jobs have one event that is the main event. In Táve we call that the Primary Session. To help, you can replace [prefix] with primary_session to use any of the above tokens for the Job's Primary Session.
Primary Session tokens will populate with the details of the event on the job schedule that's been marked as the primary session, regardless of the event type, which makes this a great universal token to use in your email templates and contracts!
Other Helpful Tokens
Job Tokens
Every job in your Táve account will have a set of tokens attached to it by default. Here's a list of some of the popular ones below. There are a lot more and you can see a full list of all tokens here.
{{job.balance}} - The remaining balance on a job ($2,490.00)
{{job.clients}} - The names of all clients on the job (Meghan Christian and Matt Fields)
{{job.clients.first_names}} - The first names of all clients on the job (Meghan and Matt)
{{job.clients_team}} - The names of all team members on the job (Erin and Elyssa)
{{job.custom.[custom-field-token]}} - Any custom fields you've created for contacts will show here
{{job.date}} - The date of the job. This will always match the same date as the primary session. (8/26/2024)
{{job.date_long}} - The date of the job in long format (Monday, August 26th, 2024)
{{job.everyone}} - A list of every contact's full name listed on this job (Meghan Christian, Matt Fields, and Judy Hernandez)
{{job.everyone.first_names}} - A list of every contact's first name listed on this job (Meghan, Matt, and Judy)
{{job.name}} - The full name of this job. If no custom name has been set, it will default to Client Name + Job Type + Long Date (e.g. Matt Fields and Meghan Christian's Destination Wedding Photography on Monday, August 26th, 2024)
{{job.name_only}} - The abbreviated name of this job. If no custom name has been set, it will default to Client Name + Job Type (Matt Fields and Meghan Christian's Destination Wedding Photography)
{{job.total}} - The total revenue for the job ($4.500.00)
{{job.total_cost}} - The total of all expenses on this job ($375.00)
{{job.total_profit}} - The total profit for this job (e.g. $4,125.00)
Brand Tokens
Every brand in your Táve account will have a set of tokens attached to it by default. Here's a list of some of the popular ones below. There are a lot more and you can see a full list of all tokens here. These will always fill with information from the brand this job is assigned to. You can adjust the information for any of your brands here in Settings › Branding.
{{brand.email}} - The email address for this brand
{{brand.email_signature}} - The email signature for this brand
{{brand.location}} - The address for this brand
{{brand.name}} - The name of this brand
{{brand.office_hours}} - The office hours for this brand
{{brand.primary_website}} - The website for this brand
{{brand.phone_label_1}} - The label of the phone 1 for this brand (screenshot below)
{{brand.phone_number_1}} - The phone number 1 for this brand (screenshot below)
Item Tokens (Quotes, Questionnaires, Contracts, Invoices and Orders)
Email in Táve is powerful, and part of that power is the ability to create templates that include links to some of our most powerful features.
Use item link tokens to link your clients to their Quotes, Questionnaires, Contracts, Invoices and Orders. To use these, you'll want to make sure you're using the right email type. Check out the Email Templates article here to see which types show up where in Táve. You'll also want to ensure that the email you're sending out is referencing something. The item link tokens in the email then use that referencing item to populate their information.
Here's a list of some of the popular item link tokens. There are more and you can see a full list of all tokens here.
{{item.link_start}} - Place this token at the start of the text you want to link to the referencing item (be sure to use the {{item.link_end}} token too)
{{item.link_end}} - Place this token at the end of the text you want to link to the referencing item (be sure to have used the {{item.link_start}} token too)
{{item.link_url}} - Populates with the URL of the referencing item
{{item.name}} - Populates with the name of the referencing item
{{item.name_link}} - Populates with the name of the referencing item turned into a link
Those item links tokens will link to the item the email is Referencing, in the example above the email is referencing a quote. Here's how those tokens would then populate on the email:
Creating Additional Tokens
A lot of tokens will be created for you, so you shouldn't need to create too many early on, but there are a few ways you can add tokens into your Táve account. Creating a new Job Role, Event Type, or Custom Field will create an entire set of tokens with it, saving you the process of setting them all up one by one. 😊