Currently, the meeting confirmation email only supports a limited set of personalisation tokens from standard Contact, Company, Host, and Meeting properties.
However, any additional properties added to a meeting booking form cannot be used as tokens in the confirmation email.
This creates a disconnect between the information a contact provides when booking and the information that can be reflected back to them in the confirmation. If a user enters important details on the meeting form, there is often no way to include those details in the confirmation email, reducing its usefulness and increasing the risk of booking errors.
For example, we use HubSpot Meetings to allow contacts to book telephone appointments. As part of the booking form, we ask for their phone number. Ideally, the confirmation email would include a message such as:
“We’ll call you on: [Phone Number]”
Unfortunately, although the phone number is collected during the booking process, it cannot be inserted into the confirmation email because custom meeting form properties are not available as tokens.
This limitation affects many other use cases as well, including:
- Preferred contact number
- Meeting topic or reason for enquiry
- Customer reference numbers
- Product or service selections
- Any custom qualification questions added to the meeting form
It would be incredibly valuable if all properties included on a meeting booking form could be used as personalisation tokens within the meeting confirmation email. This would allow businesses to create more accurate, relevant, and helpful confirmations without requiring additional workflows, custom emails, or manual follow-up.
Since the data has already been provided by the contact and captured by the form, it seems logical that it should also be available for use in the confirmation email generated from that booking.
Use case: A contact books a phone appointment, enters their phone number in the meeting form, and receives a confirmation email showing the exact number that will be called. This allows them to immediately spot and correct any mistakes before the meeting takes place.
This enhancement would make meeting confirmations significantly more flexible and useful for a wide range of scheduling scenarios.