What is a shorthand code?
Using shorthand codes on your booking form
Using shorthand codes in your confirmation emails
Standard shorthand codes glossary
What is a shorthand code?
A shorthand code is like a nickname that you give to a piece of information in your booking form. You can then customize your communications to your customers and include those pieces of information by referring to the shorthand codes.
Some shorthand codes have already pre-set by YouCanBook.me and will be used in your communications to your booker like:
- {EMAIL} the email address the booker provides on the booking form
- {FNAME} the bookers first name as entered on the booking form
You can add additional questions to collect information from your customer before the booking.
Shorthand code requirements:
- All capital letters
- Alphanumeric characters only
- Both underscores ( _ ) and dashes ( - ) are allowed
- Between 2 and 16 characters.
- The spelling of the shorthand code in your confirmation & reminder emails must match your booking form
Setting shorthand codes on your booking form
In your settings, navigate to Booking Form Questions. Add a new question, and set the shorthand code for that question.
Using shorthand codes in your confirmation emails
Take that shorthand code you've set on your booking form and add curly brackets around it in your confirmation emails.
Data relative to each shorthand code is pulled into the confirmation email, so the email is personalized for each booker.
If you set a shorthand code for each question on your booking form, these fields will be exported into separate columns in your data export.
Shorthand codes and passing through data
Shorthand codes can be used to pass through specific information about your booker through a webhook or Zapier integration.
Can I use shorthand codes to customise the text on my live booking page?
- Shorthand codes can only be used in communications that occur after the booking in the Notifications section of your settings.
What are the default shorthand codes for YouCanBook.me?
- See the list below. As with your own custom shorthand codes, the standard codes shown below must be spelled and capitalised exactly as below in order for them to work.
Standard Shorthand Codes glossary
Here is a list of all of the standard shorthand codes used by YouCanBook.me in managing bookings, pulling in booker data and formatting dates and times.
Shorthand code | How does it display |
What does it do?
|
{ACCOUNT-EMAIL} | example@test.com |
Shows account email address used to login to YouCanBook.me
|
{ACCOUNT-MOBILE} | 13455551212 |
Account number listed on account settings page
|
{ACCEPT} | [Accept] |
Shows accept button for tentative bookings
|
{ADD-TO-GOOGLE-LINK} | Raw Google Calendar Link |
Raw link that can be translated for bookers to add booking to Google calendar
|
{ADD-TO-GOOGLE} | [ADD TO GOOGLE] |
Add to google button
|
{ADD-TO-ICS-LINK} | raw .ics link |
Raw link that can be translated for bookers to download .ics file
|
{ADD-TO-ICS} | [Download calendar invite] |
Button to download .ics to add to bookers calendar
|
{ADD-TO-MSLIVE-LINK} | Raw outlook.com/live link |
Raw link that can be translated for bookers to add booking to Microsoft Outlook Live calendars
|
{ADD-TO-MSLIVE} | [Add to Office 365] |
Add to Office 365 button
|
{ADD-TO-MSOFFICE-LINK} | Raw outlook.office.com link |
Raw link that can be translated for bookers to add booking to Microsoft Office calendars
|
{ADD-TO-MSOFFICE} | [ADD TO ENTERPRISE OFFICE 365] |
Add to MS Office button
|
{ADD-TO-YAHOO-LINK} | Raw calendar.yahoo.com link |
Raw link that can be translated for bookers to add booking to Yahoo calendars
|
{ADD-TO-YAHOO} | [ADD TO YAHOO] |
Add to yahoo button
|
{BOOKING-ID} | cb6d8942-17d8-464e-b84c-c9dd97a47a5c |
ID of the booken given by YCBM
|
{BOOKING-TITLE} | Booked: John |
Title of the booking set by the calendar event
|
{BOOKING-PAGE-TITLE} | YouCanBook.me |
Show the title of the booking page set under General
|
{BOOKING-PAGE-LINK} | demopage.youcanbook.me |
The URL of the booking page, not hyperlinked
|
{BOOKING-PAGE} | demopage.youcanbook.me |
The URL of the booking page, hyperlinked
|
{BOOKING-PAGE-ID} | 9c40c2ad-2e68-45cd-9a75-2a7a28c43d99 |
the internal ID of the booking page on an account
|
{CANCEL-LINK} | https://demopage.youcanbook.me?c=DUMMY |
Link to cancel the booking for the booker
|
{CANCEL} | Click here to cancel this booking |
Text link to cancel the booking for the booker
|
{CANCELLATION-CODE} | F0E6FF |
Cancellation Ref code for the booking
|
{CANCELLATION-REASON} | Sorry, I won't be able to attend. |
Reason left by the booker for cancelling
|
{CANCELLED-AT} | 2019-02-28T14:40:58.210Z |
Time and date the booking was cancelled
|
{CANCELLED-BY} | OWNER / BOOKER |
Shows who cancelled the booking
|
{CREATED} | Thursday, February 28, 2019 2:24 PM |
When the booking was created
|
{DURATION} | 1 hour |
Booking duration
|
{EMAIL} | example@email.com |
emailed entered on the booking form
|
{EMAIL-QUESTION-CODES} | example@email.com, example2@email.com |
all emails entered in any email field on the booking form
|
{END-BOOKER-ISO-8601} | 2019-03-03T15:38:23.895Z |
Time and date the booking ends for the booker in ISO 8601 format
|
{END-BOOKER} | Sunday, March 3, 2019 3:38 PM (UTC) |
Time and date the booking ends for the booker
|
{END-DATE-BOOKER} | Sunday, March 3, 2019 |
End date for the booker
|
{END-DATE-TEAM} | Sunday, March 3, 2019 |
End date for the team member
|
{END-DATE} | Sunday, March 3, 2019 |
Date the booking ends
|
{END-DATEINMONTH} | 3 |
Month (1-12) the booking takes place in
|
{END-DAY} | Sunday |
Day of the week the booking ends
|
{END-EPOCH-MILLISECONDS} | 1551627399826 |
Milliseconds between 1st Jan 1970 and the end of booking
|
{END-EPOCH-SECONDS} | 1551627399 |
Seconds between 1st Jan 1970 and the end of booking
|
{END-HOUR} | 15 |
The hour of the day the booking ends (1-24)
|
{END-ISO-8601} |
2019-03-03T15:35:52.601Z
|
|
{END-ISO} |
2019-03-03T15:35:52.601Z
|
|
{END-LOCAL-DATE} | 2019-03-03 |
Date the booking ends
|
{END-LOCAL-DATETIME} | 2019-03-03 15:32:51 |
Local time and date the booking ends
|
{END-LOCAL-TIME} | 15:31:44 |
Local time the booking ends
|
{END-MINUTE} | 28 |
Minute the booking ends (1-60 or 0-59)
|
{END-MONTH} | March |
Month the booking ends
|
{END-MONTHINYEAR} | 3 |
Number of month (1-12) the booking ends
|
{END-RFC-822} | 2019-03-03T15:28:13.977Z[UTC] |
Time the booking ends shown in RFC 822 format
|
{END-SALESFORCE} | 3/3/2019 3:28 PM | |
{END-TEAM} | Sunday, March 3, 2019 3:28 PM (Europe/London) |
Time the booking ends in the team member time zone
|
{END-TIME-BOOKER} | 3:26 PM (UTC) |
Time the booking ends for the booker
|
{END-TIME-TEAM} | 3:26 PM (Europe/London) |
Time the booking ends in the team member time zone
|
{END-TIME} | 3:26 PM (UTC) |
Time the booking ends
|
{END-YEAR} | 2019 |
Year the booking ends
|
{END} | Sunday, March 3, 2019 3:40 PM (UTC) |
End date of booking
|
{FORMFIELDS} | First name: John |
Shows all the fields from the booking form
|
{GOOGLEMEET}
|
||
Shows a hyperlinked Google Meet link for the specific booking in email notifications
|
||
{GOOGLEMEET-LINK}
|
||
Shows a non-hyperlinked Google Meet link for the specific booking in calendar events and SMS
|
||
{IF-TEAMS} / {ENDIF}
|
This is an if statement which shows information depending on whether teams is being used
|
|
{IF-TENTATIVE} / {ENDIF}
|
This is an if statement which shows information depending on whether tentative is being used
|
|
{IF-TYPES} / {ENDIF}
|
This is an if statement which shows information depending on whether appointment types are being used
|
|
{IF-UNITS} / {IF-UNITS}
|
This is an if statement which shows information depending on whether units per slot is being used
|
|
{ID} | c0019520-ecad-457b-a7cc-b4ecaee44320 |
The YouCanBook.Me identifier for this booking
|
{IP} | 86.53.169.225 | IP Address |
{LOCATION} | Location of meeting |
Shows whatever calendar owner has put in the Event location field of the settings
|
{MANAGE-BOOKING-LINK} | https://app.youcanbook.me/#/bookingDetails?id=EXAMPLE&profileId=EXAMPLE |
Opens YCBM booking details page
|
{MSTEAMS} | https://test.youcanbook.me/microsoft-teams/ABCD-IlZL-POXC |
Shows a hyperlinked Microsoft Teams link for a specific booking in email notifications
|
{MSTEAMS-LINK} | https://test.youcanbook.me/microsoft-teams/ABCD-IlZL-POXC |
Shows a non-hyperlinked Microsoft Teams link for the specific booking in calendar events and SMS
|
{OWNER-CANCEL-LINK} | https://app.youcanbook.me/#/bookingUpdate?id=EXAMPLE&profileId=EXAMPLE&accountId=EXAMPLE&type=cancel&osec=null |
Link for calendar owner to cancel the booking
|
{OWNER-CANCEL} | Click here to cancel this booking |
Text link for calendar owner to cancel the booking
|
{OWNER-RESCHEDULE-LINK} | https://demopage.youcanbook.me?or=DUMMY |
Link for calendar owner to reshedule the booking
|
{OWNER-RESCHEDULE} | Click here to reschedule this booking |
Text link for calendar owner to reschedule the booking
|
{PRICE} | USD 0.00 |
Price of the booking
|
{REF-NO-DASHES} | ILLJHMVATWSP |
Booking reference with no dashes
|
{REF} | ILLJ-HMVA-TWSP |
Booking reference
|
{REJECT} | [Reject] |
Shows reject button for tentative bookings
|
{RESCHEDULE-LINK} | https://demopage.youcanbook.me?r=DUMMY |
Link for rescheduling the booking
|
{RESCHEDULE} | Click here to reschedule this booking |
Text link for booker to reschedule the booking
|
{RESCHEDULED-AT} | 2019-02-28T14:03:52.585Z |
Time booking was rescheduled
|
{RESCHEDULED-BY} | BOOKER / OWNER |
Shows calendar owner or booker depending on who cancelled
|
{START-BOOKER-ISO-8601} | 2019-03-03T14:11:33.826Z |
Start time for the booker in ISO 8601 format
|
{START-BOOKER} | Sunday, March 3, 2019 2:11 PM (UTC) |
Start time for the booker
|
{START-DATE-BOOKER} | Sunday, March 3, 2019 |
Start date for the booker
|
{START-DATE-TEAM} | Sunday, March 3, 2019 |
Start date for the team member
|
{START-DATE} | Sunday, March 3, 2019 |
Start date calendar owner
|
{START-DATEINMONTH} | 3 |
Day of the month the booking starts
|
{START-DAY} | Sunday |
Day of the week the booking starts
|
{START-EPOCH-MILLISECONDS} | 1551606681668 |
Milliseconds between 1st Jan 1970 and the start of booking
|
{START-EPOCH-SECONDS} | 1551606681 |
Seconds between 1st Jan 1970 and the start of booking
|
{START-FORMAT-h:mm a} | 4:00 PM |
The start date and time in 12-hour format
|
{START-FORMAT-HH:mm:ss} | 15:00:00 |
The start date and time in 24-hour format
|
{START-FORMAT-yyyy-MM-dd} | 2021-04-18 |
To have the start date displayed in a particular pattern (link)
|
{START-HOUR} | 9 |
Shows the hour of the day the booking starts
|
{START-ISO-8601} | 2019-03-03T09:50:40.129Z |
The start time formatted to the ISO 8601 standard
|
{START-ISO} | 2019-03-03T09:50:40.129Z |
The start time formatted to the ISO 8601 standard
|
{START-LOCAL-DATE} | 2020-11-19 |
Shows the date of the booking
|
{START-LOCAL-DATETIME} | 2020-11-19 15:00 |
Shows the start time and the date in seconds and milliseconds
|
{START-LOCAL-TIME} | 9:29 |
Shows start time in booker timezone
|
{START-MILLIS} | 1571571480000 |
Shows the start time of the booking in UNIX time
|
{START-MINUTE} | 35 |
Minutes past the hour that the booking starts
|
{START-MONTH} | March |
Name of the month the booking has been made in
|
{START-MONTHINYEAR} | 3 |
Number of the month (1-12) the booking has been made in
|
{START-RESCHEDULED-FROM} | Thursday, March 14, 2019 4:35 PM (Europe/London) |
Displays original booking time when a booking is rescheduled
|
{START-RFC-822} |
2019-03-02T16:35:06:583Z
|
|
{START-SALESFORCE} | 3/2/2019 4:35 PM |
Start time as it would show on Salesforce
|
{START-TEAM} |
Saturday, March 2, 2019 4:35 PM (Europe/London)
|
|
{START-TIME-BOOKER} | 4:29 PM (UTC) |
Start time and timezone of the booking for the booker
|
{START-TIME-TEAM}
|
Start time and timezone of the booking for the team member
|
|
{START-TIME} | 4:29 PM (UTC) |
Start time and timezone of the booking (booker timezone)
|
{START-YEAR} | 2019 |
The year the booking starts
|
{START} | Sunday, March 3, 2019 2:11 PM (UTC) |
Start time for booker
|
{START+60} | April 4, 2013 11:00 AM |
Adjust the start time + set number of minutes, to quote booker an earlier time to arrive
|
{TARGET-CALENDAR-ID} | test@example.com |
Shows the ID (email address) of the linked calendar
|
{TARGET-CALENDAR-TITLE} | Test's Booking calendar |
Shows the linked calendar email address
|
{TEAM-DESCRIPTION} | *whatever the user has put in team member description* |
Shows the team member description
|
{TEAM-EMAIL} | kayleigh@email.com |
Shows the team member email
|
{TEAM-IMAGE} | *image* Kayleigh |
Shows the team name and image (if image uploaded)
|
{TEAM-NAME} | Kayleigh |
Shows the team name
|
{TENTATIVE-BLOCK} | This booking is not yet confirmed [Accept] [Reject] |
Provides options to accept or reject a tentative booking
|
{TIMEZONE-BOOKER} | UTC |
Shows booker timezone
|
{TIMEZONE} | UTC |
Shows calendar owner timezone
|
{TYPE-DESCRIPTION} | My Service |
Description of the appt type selected
|
{TYPE-IMAGE} | [IMG] My Service |
Shows the image associated with the appt type
|
{TYPE-NAME-NO-GROUP} | My Service |
Shows appt type selected if there are no multiple appt types selected
|
{TYPE-NAME} | this is the appointment type description |
Shows whatever the calendar owner has set as the appt type description
|
{UNITS} | 1 |
Shows units per slot
|
{WHEN} | Saturday, March 2, 2019 4:17 PM (UTC) |
Shows when the booking is
|
{ZOOM} | https://demopage.youcanbook.me/zoom/ABCD-EFGH-IJKL |
Shows a hyperlinked unique zoom link for the specific booking in confirmation emails
|
Comments
0 comments
Please sign in to leave a comment.