La fonction de suggestion automatique permet d'affiner rapidement votre recherche en suggérant des correspondances possibles au fur et à mesure de la frappe.
Some businesses benefit from entering 2 different email addresses for a single contact. For now, they create a custom property "secondary email", but if someone fills in a form with this secondary email, they have to manually merge the contact every time.
I am experiencing a similar issue. Sent an email to a contact through the CRM. Received an email back and it was not logged. Used the forward option, which unfortunately includes my signature and makes it difficult to read.
The first forward did not work. Checked for a duplicate assuming he used another email. No duplicate. I did notice that the email he used was the secondary email for the contact. This is problematic as there is no way to know what the contact will do to respond and having the right information, in the right place, when you need it is critical.
Any thoughts? I am going to post with the secondary email group/email not logging as well.
I agree. There are lots of reasons why it would sense. Divoced parents- primary and secondary e-mail addresses.Personal and professional. Multiple gigs. I have my partner log in and my client email account in HubSpot! But would want to decide whether to send to primary or secondary or both. Don't make that an upgrade feature. It's pretty fundamental. You can count the e-mail addresses. That's how you monetize it.
The fact that we can add multiple email addresses to existing contacts (and select which one is the primary email) is awesome, but the inability to create contacts with multiple email addresses from the get-go makes it a pain to have contacts with multiple emails since any email beyond the first must be added manually.
I don't know how feasible this is, but … the ability to add multiple email addresses both within HubSpot's "Create Contact" window (maybe keeping the same single-line text box, but using a semicolon to separate multiple emails and making the first email in the list the primary email), as well as adding support for multiple email addresses within CSV imports (still in one cell, separated via semicolons, making the first email the primary), would be HUGE.
Pour ajouter un commentaire ici, vous devez être inscrit. Si vous êtes déjà inscrit, connectez-vous. Dans le cas contraire, inscrivez-vous puis connectez-vous.