Adding individual contacts using the Chrome extension

How to run email lookups for individual contacts.

In this guide:

If you're running a more targeted search for contacts, our Chrome extension button allows you to perform email lookups for individual LinkedIn profiles.

Before looking up contacts on the Chrome extension, be sure to create a sequence first since sequences need to be created in order to add contacts.

Finding an email address for an individual contact

When you click the Interseller icon button on a contact's LinkedIn profile, this will run an email lookup for that contact. If more than one email address appears in the lookup window, you will need to select one email address from the list to add into a sequence.

Follow these steps to lookup an individual contact:

  1. Click the Interseller button on the contact's profile.
  2. In the Chrome Extension pop-up window, select the email address you would like to use for the contact.
  3. Next, click the down arrow next to the sequence title to select the sequence you want to add the contact to. You can either scroll through the list or type in the field to search for the sequence. You will also see an option to toggle between viewing "My Sequences" or "All Sequences".
  4. From there, click Save Contact at the bottom of the window to add the contact to your sequence.

Indicator messages in the Chrome extension

If the contact that has been added, messaged, or responded on Interseller before, this information will be highlighted in a yellow box. This is especially helpful for checking to see if a contact exists as a duplicate in other sequences.

If there's a connected integration and the same email address exists in the integration, this will also highlight the contact as a duplicate in the integration in a yellow box. This is helpful to know if the same contact already exists in your connected CRM/ATS.

If the contact is blocked, has unsubscribed, or if their email previously bounced, this information will also be highlighted in a red box. This is to help warn and prevent you from sending messages to contacts who are currently blocked, have previously unsubscribed, or whose emails have previously bounced from your sequences.

Finding a contact's address on their LinkedIn profile

Our Chrome Extension will warn you when we find an email address that matches the address listed on a contact's LinkedIn profile. 

This will prevent our system from charging a lookup as long as the email preference matches the type of address listed on their profile.

Contact found in existing sequence warning

Our Chrome Extension will warn you when we find an email address that matches a contact in one of your existing sequences. 

This will prevent our system from charging you a lookup as long as the email preference matches the address in the sequence and the address we have found in the extension.

Reporting an incorrect email address

If an incorrect email address is found through the Chrome extension, you can report it from the lookup window or within the contact record in an email sequence. You can  select the "Report incorrect email address" option and click the "Report" button.

When an incorrect email is reported, our data team will be notified to investigate the issue.

Note: The "Report incorrect email address" option will only appear for emails found through the Chrome extension within the past 2 years. This will not be visible if the contact was added manually or through CSV imports. 

Adding information for custom fields

If you have additional custom fields you would like to fill in for the contact, you can scroll down in the pop-up window to add those in.

Personalizing messages

Once you save the contact's email to a sequence, you can personalize your initial message to the contact directly from our extension. You can always edit your personalized messages for contacts in the preview tab of the sequence.

Check out our personalization guide for more details.

Note: You can only personalize messages from our extension while doing an individual email lookup.

Did this article answer your question? Thank you for your feedback! There was a problem submitting your feedback. Please try again later.