Amplifi’s contact import is one of the most capable parts of the platform. Whether you’re onboarding a fresh list, syncing an updated export from another tool, or adding a handful of people by hand, the importer walks you through each step and gives you full control over how your data maps to Amplifi fields.Documentation Index
Fetch the complete documentation index at: https://docs.messagesender.ai/llms.txt
Use this file to discover all available pages before exploring further.
Import methods
You can bring contacts into Amplifi four ways:CSV upload
Upload a
.csv file from your computer. The most common method for bulk list imports.Excel upload
Upload a
.xlsx file directly. No need to convert to CSV first.Paste tabular data
Copy rows from a spreadsheet and paste them directly into the importer. Useful when you don’t want to save a file.
Manual entry
Add a single contact by filling out a form. Best for one-off additions.
File uploads are limited to 100 MB. If your file exceeds this, split it into multiple imports.
The import flow
Regardless of which method you use, the import process follows the same steps:Upload or paste your data
Choose your import method and provide the file or data. Amplifi parses your input and moves to the preview screen.
Review the parsed preview
Check that the rows and columns look correct before proceeding. If the data looks wrong—extra header rows, misaligned columns—go back and adjust your source file.
Name the import
Give the import a descriptive name, such as the list source or date. The name appears in Import History and can be used as a contact filter later.
Apply tags (optional)
Optionally add one or more tags to every contact in this import. This is useful for tracking list origin (for example,
event-2026-spring) or for targeting this group in a future campaign without building a separate segment.Choose textability verification
Decide whether Amplifi should verify each phone number’s textability during processing. Verification adds time but improves the accuracy of your textable audience count. You can skip this step and run verification later.
Map fields
Match your source columns to Amplifi contact fields. The importer auto-detects common columns like “Phone,” “First Name,” and “Email,” but you review and confirm every mapping.Supported destination fields include:
- Phone number
- First name and last name
- Address, city, state, ZIP
- Tags
- Timezone
- Opted-out status
- Custom fields
Background processing
Imports run in the background after you submit. You don’t need to stay on the page or wait for completion. For large lists, processing may take several minutes. To check the status of any import, go to Settings → Import History.Import History
Import History shows every import your organization has run, with the following columns:| Column | What it shows |
|---|---|
| Import name | The name you gave the import |
| Total rows | Number of rows submitted |
| Added | New contacts created |
| Updated | Existing contacts that were updated |
| Errors | Rows that could not be processed |
| Textable | Contacts verified as textable |
| Non-textable | Contacts verified as non-textable |
| Verification progress | How far along textability verification is |
If a row in your file matches a contact already in your account (by phone number), Amplifi updates that existing contact rather than creating a duplicate.
Tips for a clean import
Format phone numbers consistently
Format phone numbers consistently
Amplifi accepts several common phone number formats, but a consistent format in your source file reduces the chance of parse errors. Ten-digit US numbers (with or without country code) work reliably.
Use the import name as a filter later
Use the import name as a filter later
Once an import completes, you can filter your contact list by import name to see exactly which contacts came from that batch. This makes it easy to target or audit a specific list.
Apply tags during import for easy segmentation
Apply tags during import for easy segmentation
Run textability verification for new lists
Run textability verification for new lists
For any list you haven’t previously verified, enable textability verification at import time. This prevents credits from being spent on numbers that can’t receive SMS.
Create custom fields before or during import
Create custom fields before or during import
If your source data has columns that don’t map to standard fields (for example, “Member ID” or “Region”), you can create new custom fields during the mapping step. They’ll be available for filtering and merge fields after the import completes.