Messaging Candidates Using LinkedIn InMail

Teamable works best with email since you can automate follow-ups, personalize messaging, and even handle responses. However, in some instances, you may want to send an InMail message, either as a follow-up or in cases where there is no known email for a candidate. 

On the Profile tab in the Teamable Chrome Extension, you can copy the initial messaging, paste it into a LinkedIn InMail, and then you can mark the candidate as reached through LinkedIn InMail.

Message Candidates via InMail using the Teamable Chrome Extension

Step 1. On any tab in the Extension, if a campaign message is already selected from the dropdown, select the "Record outreach" button on the bottom of the extension.

The variables {First Name}, {Company}, {Sentence}, and {Signature} will be replaced with the candidate's profile information, so please edit the message as needed.

If the Campaign Sender is a teammate instead of yourself, the {Signature} variable will populate with your own user's signature and not the Campaign Sender's signature.

Step 2. You will see the "Success" banner pop-up once the InMail has been recorded on Teamable. You can then paste the copied First Message into the candidate's LinkedIn InMail message.



View the recorded InMail in the Candidate's Profile on Teamable

From the Chrome Extension:

Step 1. Select one of the 'View' options depending on whether or not you have an ATS integrated and the Candidate's Profile page will appear in a new tab.

From the Teamable site:

Step 1. Find the candidate and select the candidate's name on the Candidate Profile Card.

Step 2. Select the History tab.

Please note that the recorded message in the candidate's profile will be the default generated First Message from Teamable and it will not reflect your actual message if you have edited the message after copying it. You will need to view your InMail inbox to view the actual sent message
Did this answer your question? Thanks for the feedback! There was a problem submitting your feedback. Please try again later.