Remove form field properties from HubSpot meeting link descriptions
We have an issue where our customer meeting links are showing the properties we use as tokens in the meeting title.
For some unknown reason, these properties display randomly at the bottom of the meeting invitation in the customer's calendar invite. HubSpot advised that these cannot currently be removed, nor can the way in which they display be modified.
Frankly, they make the invite look unprofessional and the placement looks random and unintentional (mainly because it is).
The customer predominantly helps their customer to fill up the form fields of the meeting on behalf of them instead of sending the link to them to fill up and those are values they don't want them to see.
This is still needed till this day! For medical places this could be against HIPPA, especially now that people are allowed to add guests. There is no reason non default information needs to be included. Please atleast make this optional especially for companies that have partners scheduling meetings for people using meeting links. It is 2024, and the HubSpot meetings still lack so many options.
agree! We use meeting links internall to hand info over, however, having the internal notes/info is super messy and doesnt not make a great Customer Experience so we have to find another option
As an update- our workaround to this was to create a scheduling system with a separate form for most of the intake questions. Once they've filled out that form, it conditionally redirects them to the correct calendar where they input just name, phone number, and email. It's still pretty limiting (it's not like we can set this up for all of our scheduling purposes, what about B2B) and they have to submit their email twice, I wish HS would fix this
We're also using meeting links on behalf of SDRs. This is a bad look to the customers when we include source information and other internal properties in the meeting booking links. Should DEFINITELY be able to turn this off. HUBSPOT PLEASE HELP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.