You can add multiple leads, contacts, or customers and schedule them for messaging by importing a CSV (comma-separated values) file into Conversica.
This article covers uploading your prepared CSV file into Conversica using the Lead Uploader. If you are looking for information on preparing your CSV file, see Preparing CSV Files for the Lead Uploader.
- Uploading your CSV file
- Mapping your file to Conversica columns
- Reviewing your import selections
Uploading your CSV file
When you have prepared your CSV file, you are ready to import your data into Conversica:
- Log into your Conversica instance.
- Go to Lead Manager.
- Click Upload Leads.
Choosing a conversation and file (step 1 of 6)
- Click Select Conversation and select a conversation from the list.
- Click Choose File and select the file from your device.
- Click Upload.
- Click Next.
Previewing the file (step 2 of 6)
- Preview the data to ensure it is formatted correctly. If you encounter any errors, Click Cancel to exit the tool and resolve the errors within the file. Then try to upload the file again.
- Once you are satisfied with the preview, click Next.
Mapping your file to Conversica columns
Over the following screens, you will map the headers from your CSV file to the corresponding Conversica column to set the lead date, rep assignment, contact list, and variables. The Lead Uploader will automatically suggest which Conversica column to map your data based on the title of the CSV column headers.
Mapping columns (step 3 of 6)
This section contains the minimum data mapping required to launch your file.
- Email - map the header containing the email address to the Email column.
- First Name - Depending on how the first and last name is formatted in the CSV file, you can choose from three options to format the contact name:
- Separate: if the first and last names are in different columns in the CSV file
- First Last: if the value is formatted as First Name, Last Name
- Last First: if the value is formatted as Last Name, First Name
Do not contact
Important: To remain compliant with anti-spam regulations, you must ensure you have consent to communicate with each contact you import into Conversica. You should not message contacts who have previously opt-out of communication with your business.
Depending on your CSV file source, your file may contain a header that identifies opt-outs. Standard header examples may include Do Not Contact, Do Not Solicit, Do Not Email, Do Not Call, DNC, etc. The corresponding column values are typically True/False or Yes/No. Each data source defines these values differently, so make sure you clearly understand how your data source uses them to express a contact's opt-out status.
Mapping to the Do Not Contact column
If your CSV file contains a do not contact header, map it to the Do Not Contact column.
Select which values to communicate a contact's opt-in/opt-out preference by choosing True, False, Yes, or No values for the following options:
- Do not message leads with the value
- Message leads with the value
Select None if your file does not contain a Do Not Contact header. By selecting none, you ensure you have the consent to contact each person on your CSV list.
Map additional column headers to the appropriate Conversica fields. These include but are not limited to:
- Home Phone
- Cell Phone (required for SMS First conversations)
- Work Phone
- Lead Created Date
- Lead Source
- Source ID
*Automotive Sales and Service conversations
Assigning reps to contacts (step 4 of 6)
Choose how to assign contacts to a Conversica rep by selecting one of the following options:
- Use Basic Mapping - Basic mapping is selected by default and allows you to auto-assign contacts to Conversica reps and distribute them equally across your team.
- Use Advanced Mapping - To assign contacts to specific reps in Conversica, map the CSV file header and the Rep Name column. Select which reps to include in the Round Robin for any leads not assigned to an active Conversica user.
Choosing conversation variables (step 5 of 6)
If the conversation you selected has customizable conversation variables, you can either take no action and use the default variables or customize the variables on this screen.
If you want to customize the conversation variables:
- Select and map to the matching column from the CSV file.
- Choose 'custom' and write a custom value.
- Click Next.
Note: You may see the option to select a contact list with existing customizations.
Remember that any mappings made in Advanced Settings will override the customizations in the contact list (if selected). Therefore, we advise that you choose either the "Select Contact List" or the mappings in Advanced Settings when applying conversation customizations.
Reviewing your import selections
Review your import selections carefully on the summary screen for accuracy. This is your chance to resolve any errors before the file is launched, and contacts are automatically scheduled for messaging.
Reviewing the file summary (step 6 of 6)
Here's a checklist of essential sections to review before you launch your file:
- File information: verify you uploaded the correct file
- Lead Health: Review the total valid leads and invalid leads contained in the file.
- Mapping: Confirm the CSV column headers are mapped to the appropriate Conversica columns.
- Conversation Preview: See a summary of the conversation objective and preview the messaging for different exchanges in the conversation flow.
Once you are satisfied with the file preview, you're ready to launch it.
- Click Yes to verify you approve the file.
- Click Yes to confirm your selection.
- Click Submit.
The system will automatically process the file, and leads will be visible within 5-10 minutes.
Q: What if my CSV file contains a column with no corresponding Conversica field to map?
A: The column data will not be imported into Conversica.
Q: I accidentally closed the Upload Leads tool. Did I lose my work?
A: No. Reopen the Upload Leads tool, and you'll be able to pick up where you left off.
Q: I uploaded my leads. How long does it take for my file to launch?
A: Files are automatically scheduled and launched within 5-10 minutes.