Default values for personalization tokens in email
planned
B
Brian Pappalardo
For example, if I wanted to start an email with "Hi {{Contact.first_name}}," it would work beautifully for people in Highlevel where we know their first name. BUT if we have people with no value for their first name, then we have "Hi ,". That's not horrible but we do have an awkward space between Hi and the comma. So it's not ideal. What I would like to suggest is being able to add a default value. So if I set the default value to "friend", it would say either "Hi Mary," if we know the first name or it would say "Hi friend," if we don't know the first name. Thanks for considering!
HIGHLVL-I-3431
Log In
S
Shreya Banerjee
marked this post as
planned
Hey Everyone,
We have released this for emails at instance level! Please check the help document linked below to test this out.
D
Damien Elsing
This is a crucial feature, available in almost every other email automation tool. Currently GHL just leaves an blank space such as "Hi ," if the first name is not known, which is not a good first impression. There needs to be a way to set a default or fallback value such as "there" for fields like contact first name.
S
Sales & Marketing
marked this post as
under review
D
Damien Elsing
Sales & Marketing: There are several other threads on the same topic with more votes. - https://ideas.gohighlevel.com/contacts/p/fallback-variables - and https://ideas.gohighlevel.com/contacts/p/fallback-placeholder-value-for-system-fields
D
David Ronka
Totally agree with this recommendation (and ActiveCampaign does this) -- the ability to set a default value for contact.first_name. Love it.