β¨ What you can do
- Upload contacts from a CSV file.
- Match CSV columns to contact fields.
- Create new contact fields for extra CSV columns.
- Review how many contacts will be imported or skipped.
- Confirm consent before importing contacts.
- Apply existing or new tags to imported contacts.
- Choose how duplicate phone numbers should be handled.
- Add contacts directly to Contacts.
- Optionally create a new powerlist for AI dialing or manual dialing.
- Track import progress while the file is being processed.
πͺ Import Steps
The import process is organized into six main steps:
Each step helps you prepare the contact list before the final import.
1οΈβ£ Step 1 β Upload CSV
Start by dragging a CSV file into the upload area or clicking the upload box to choose a file from your computer.
- The file must include a header row β for example
Phone,First Name,Last Name,Email,City, or other column names. - The importer uses these headers to understand what each column means.
- If the file has no header row or no contact rows, the system shows an error and asks you to upload a valid file.
2οΈβ£ Step 2 β Map fields
After the file is uploaded, the system shows the columns found in your CSV. Match each column to a contact field, ignore it, or save it as a new field.
The system tries to auto-detect common fields, especially phone number, name, and email. Change the mapping if the system selected the wrong field.
π½ Mapping options per column
For each CSV column, use the dropdown to:
- Map it to an existing contact field.
- Choose β ignore β to skip that column.
- Select + New field to create a custom contact field and keep that data.
Map at least one column to Phone. We canβt dial without one.The Review button stays disabled until a phone column is mapped. The system also checks how many rows have valid phone numbers. If the selected phone column looks mostly empty or invalid, the importer warns you and may suggest a better column. Creating new contact fields If your CSV has extra columns that do not match existing contact fields, save them as new contact fields during the mapping step. Examples of useful custom fields:
- Lead Source
- Insurance Type
- Appointment Date
- Customer Stage
If your file does not have a consent column, leave this set to β none, all rows assumed consenting β and continue with the main consent confirmation in Step 4.
3οΈβ£ Step 3 β Review cleanup
The review step shows a preview of what will happen before the import begins. You will see:- How many contacts will be imported.
- How many rows will be cleaned out or skipped.
- The total number of rows in the file.
- A cleanup breakdown for missing phone numbers, invalid phone numbers, and non-consenting rows.
- A small sample of clean rows that are ready to import.
- Any new fields that will be created.
4οΈβ£ Step 4 β Consent confirmation
Before importing, you must confirm that the contacts have given permission to receive communications from your business. This confirmation is required because calls, SMS, and marketing communication may be subject to TCPA and carrier compliance rules. You cannot continue until the consent checkbox is selected.5οΈβ£ Step 5 β Tags and duplicates
The tags and duplicates step lets you organize contacts and decide how the system should handle existing phone numbers. Applying tags You can apply existing tags to all imported contacts. You can also create new tags during the import. Tags help you:- Find contacts later.
- Organize lists.
- Trigger automations or workflows.
For most imports, Skip duplicates or Update existing is recommended.
6οΈβ£ Step 6 β Powerlist
After contacts are prepared, choose where they should go.
Creating a powerlist
If you choose to create a powerlist:
- Enter a powerlist name. The system may pre-fill the name based on your file name, but you can edit it.
- Choose how the powerlist should be used:
If you select AI Dial, you must choose an active AI voice agent.
β Import complete
When the import finishes, the success screen shows a summary. The summary may include:- Number of contacts imported.
- Number of existing contacts updated.
- Number of rows cleaned out.
- Destination β for example Contacts, Manual powerlist, or AI Dial powerlist.
π« Rows that may be skipped
Some rows may not be imported. Common reasons include:
The review and progress screens help you understand why rows were cleaned out.