Uploading leads: Lead preparation checklist


This is a short checklist to help you prepare your leads for uploading into a campaign.


Topic Template

▢ Is the Topic Template version you want to use Published?
The bot uses the currently Published version (as opposed to any Draft version) when starting a conversation with your leads. Make sure the version you want your bot to use is Published.



▢ Have you included the required columns?
At minimum, a first name and email address are both needed in order for your Saleswhale bot to begin engaging the lead. These column headers in your CSV file must be named "first_name" and "email."

▢ What other merge tags have you used in the topic template?
Ensure that you include the other relevant columns. To find out the names of these column headers, select “View all column headers” at the “Import CSV” pop-up in your Campaign view.

▢ Are your leads assigned to specific sales reps?
If so, you should include a "lead_owner" column where you’ll input the sales rep’s email address


Lead Data

▢ Are you confident in the integrity of your list?
Verifying the quality of your leads is important to ensure your bot's email can be used for a long time (verifying your leads before enrollment). Any bounce rate greater than 10% could put your email address / domain at risk. If you are unsure about the integrity of your list, we encourage uploading a smaller batch of around 50 emails and checking on the bounce rate.

▢ Do all leads have an email address?
Any leads without an email address will not be enrolled.

▢ Is the data for all merge tags from the topic template within the csv file?
Any leads without data for a merge tag in the topic template will use the merge tags fallback text. For example, if the merge tag "{{account.name}}" is used and a particular lead does not have an account name, the fallback text "your company" will be used in the email message.

▢ Is the data semantically correct to merge into the topic template messaging?

▢ Check for special characters 
Saleswhale’s app currently does not support special characters (e.g. é, ü, ø), these will have to be replaced with characters from the English alphabet.


Sample Template



1 out of 1 found this helpful



Article is closed for comments.