Support separate internal and external names for Meeting Types
P
Pieter Cortebeeck
Meeting Types currently use a single name that appears both in the admin interface and in customer-facing experiences, including the booker URL and the meeting selection screen. Admins who use descriptive internal naming conventions to manage and distinguish Meeting Types end up exposing that internal language to prospects.
Meeting Types should support a separate internal name, visible only to admins, and an external label that is shown to guests in the booker and scheduling flows.
Admins need descriptive internal names to manage Meeting Types at scale without creating confusion for prospects who see that same label. Without this, teams are forced to choose between internal clarity and a clean guest experience.
Taylor Jennings
Merged in a post:
Support separate internal and external names for Meeting Types
Meeting Types currently use a single name that appears both in the admin interface and in customer-facing experiences, including the booker URL and the meeting selection screen. Admins who use descriptive internal naming conventions to manage and distinguish Meeting Types end up exposing that internal language to prospects.
Meeting Types should support a separate internal name, visible only to admins, and an external label that is shown to guests in the booker and scheduling flows.
Admins need descriptive internal names to manage Meeting Types at scale without creating confusion for prospects who see that same label. Without this, teams are forced to choose between internal clarity and a clean guest experience.
B
Brynn House
For custom meeting types, I want to be able to add an internal-only meeting label or description that is NOT reflected in the customer-facing URL.
We want to be able to track types that correlate with specific initiatives, without laying that out for a savvy customer, and right now we have to do that in an external spreadsheet.
B
Brynn House
For custom meeting types, I want to be able to add an internal-only meeting label or description that is NOT reflected in the customer-facing URL.
We want to be able to track types that correlate with specific initiatives, without laying that out for a savvy customer, and right now we have to do that in an external spreadsheet.
Tom Leader
It would be fantastic to have two options for the meeting type name, one that shows in the Meeting_Type_CP field and one that is shown to the sales team. For example, we have multiple demo meeting types for different languages, such as "Demo - English", "Demo French" etc. so that the sales team can select the correct option. We'd love to be able to have them all show as "Demo" in SFDC so that we can more easily filter and report by meeting types.