Punctuation (or descriptive text) around personalization tokens

[Yo_Be_Low]

When you add a personalization token to an email (e.g. first name), and the default if there is not value for the personalization token is "" (blank), it's difficult to add punctuation around the token. For example, say you want an email to read: "Alice, welcome to our world" where Alice is the first name and ", welcome to our world" is the accompanying text. That works fine if the contact has a first name. But if they don't, it will read ", welcome to our world". Clearly not acceptable.

Of course, you can set the default if there is no value to be "Greetings" or some other language that makes sense with ", welcome to our world" after it. But it would be cleaner and more flexible (because you're allowing a "" default) if the leading comma could be conditional upon the existence of a first name value.

Maybe in {{ personalization_token("contact.firstname", "") }} there could be an additional syntax to allow a text string after "contact.firstname", e.g. ("contact.firstname"<", ">, "") so that the text string ", " would be added after contact.firstname, but not if there was not if there was no value for contact.firstname

[CP-BWG]

There are several ideas like this in different feature requests.  Hubspot - this is a simple request, just give the ability to prepend or postpend the personalization token and make everyone's life easier.  I can;t understand how this hasnt come up as a majo issue before, as nearly every personalization token involving a name would be in a greeting, and would have some sort of punctuation around it. @hubspot