Customer is requesting the ability to use dynamic links in a signature. For example, when using the custom teammate field {{teammate.phone_number}}, they would like the number to be clickable.
Guest
Aug 21, 2024
This would be great for email addresses as well, especially for emails configured for Front users or inboxes. If a user's email is firstname.lastname@company.com and the dynamic variable in a company's dynamic signature pulls the user's email, then that email should be optionally clickable.
The difference might be {{user.email}} and {{user.email.link}}
More complex dynamic variables like phone numbers or web links should also be clickable links. This might be solved by creating new custom field types specifically for email, phone, & web links. Web link custom fields would be two fields - one for the web link; one for the link text. Even though phone & email links are just web links, it wouldn't be necessary for users to remember to format "mailto:firstname.lastname@company.com" or "tel://+18009999999". This would also allow Front to validate that email addresses & phone numbers are in the correct format before that field can be saved.
I know this suggestion is more complex than just what's above - Front would need to account for custom web link fields imported via file or via API connection - but I believe this suggestion is valuable.
This would be great for email addresses as well, especially for emails configured for Front users or inboxes. If a user's email is firstname.lastname@company.com and the dynamic variable in a company's dynamic signature pulls the user's email, then that email should be optionally clickable.
The difference might be {{user.email}} and {{user.email.link}}
More complex dynamic variables like phone numbers or web links should also be clickable links. This might be solved by creating new custom field types specifically for email, phone, & web links. Web link custom fields would be two fields - one for the web link; one for the link text. Even though phone & email links are just web links, it wouldn't be necessary for users to remember to format "mailto:firstname.lastname@company.com" or "tel://+18009999999". This would also allow Front to validate that email addresses & phone numbers are in the correct format before that field can be saved.
I know this suggestion is more complex than just what's above - Front would need to account for custom web link fields imported via file or via API connection - but I believe this suggestion is valuable.