Nickname in Main Name Reference Field

SOLVE
StephenGoldsmit
Member

I would like to see a slight change to the information that is available on the top left portion of a contact page.

Right now there is a space for a picture and right below it is the person's name, as entered in the contact record.  The name only has space for the first and last name.  I would suggest adding the option for adding the nickname in this field so when I am on the phone with someone or drop them a note, I am aware that there is a nickname that they prefer to be referenced by.  If there is nothing in the nickname field, the name would appear as it does now, if there is a nickname,it  would appear in a (for my name) Stephen "Steve" Goldsmith format.  This will help me not accidently calling "Ted," Alfons or other such errors one could make.  Hope you can see the merit of and incorporate this change in the near future.

 

Regards,

 

-S-

0 Upvotes
1 Accepted solution

Accepted Solutions
MelindaNelson
Solution
HubSpot Employee

Hi @StephenGoldsmit

 

Thank you for posting your idea in the Community. I can see how this would be useful. I found this similar post in the Ideas Forum. I would recommend upvoting that idea and adding your usecase. 

 

Creating a nickname in the top section of the left record sidebar is not currently supported, but you could:

I hope this suggeston helps! Let me know if you have any additional questions!  

 

Thanks,

Melinda | (She/Her)

Customer Support Specialist

View solution in original post

1 Reply 1
MelindaNelson
Solution
HubSpot Employee

Hi @StephenGoldsmit

 

Thank you for posting your idea in the Community. I can see how this would be useful. I found this similar post in the Ideas Forum. I would recommend upvoting that idea and adding your usecase. 

 

Creating a nickname in the top section of the left record sidebar is not currently supported, but you could:

I hope this suggeston helps! Let me know if you have any additional questions!  

 

Thanks,

Melinda | (She/Her)

Customer Support Specialist

View solution in original post