Adding a list

Only an owner or an admin can add a list. Adding a list calls nobody. The people wait, unchecked, until you check the list.

Do this

1. Open People, then Lists, then press Add a list.
2. Upload. Drop your file or choose it. It must be a CSV file whose first row holds the column names. You see the first 5 rows and the number of people.
3. Match columns. For each column, check what we guessed from its name. Change it from the menu. The phone number is the only column we must have. Choose Extra detail I want to keep (and name it) for anything else you want on the person. Choose Skip this column to leave one out.
4. Where it’s from. Name the list. Say who sent it to you (a vendor, or Not from a vendor). Choose the campaign that will call it, or choose later. If your file has no consent columns, you can type how everyone agreed, for example “web form”.
5. Import. Press Import. Large files take a minute. You then see how many people were added and how many were skipped, with the first problems listed by row.

The columns we understand

Column on the screen	What it is
Phone number (required)	A US number. We read many formats.
First name, Last name	Used on screen and for the name check.
State, ZIP code	Help us work out the time zone.
Date of birth	Needed only if the campaign has a minimum age.
Language	Matches the person to agents who speak it.
Your own ID	Your reference for this person.
When consent was given, Where consent came from, Consent certificate link	The proof the person agreed to be called. See below.
Extra detail I want to keep	Any other column, kept on the person under the name you give it.

The import also reads timezone and priority columns, but the add-a-list screen has no menu entry for them today. Send those through the API.

Why the consent columns matter

If we cannot find proof that a person agreed to be called, the check holds them back with the reason “No proof of consent”. Most people in a file with no consent columns will be held back. For each row that has consent, we store it with the person. The accepted sources are trustedform, jornaya, web_form, verbal and manual. A trustedform or jornaya row needs its certificate link. See consent proof.

Importing the same file into the same list again repairs a failed consent send. People already in the list are left as they are, and the consent in every row is sent again. If the result says some proofs were “turned away”, fix those rows and import again.

Note

The add-a-list screen makes a new list every time you use it. Pressing Try again after an error on the Import step reuses the list it just made. To import again into a list you made earlier, use the import call in /api/docs (POST /v1/lists/{id}/import).

What gets skipped

• A bad phone number. The row is skipped. The first 50 are listed with their row and column.
• A repeated number in the file. Added once. The rest are skipped.
• A number already in the list. Left exactly as it was.
• A bad state, ZIP code or date of birth. The person is added. That one value is dropped, with a warning.

The result also lists any proof of consent that was turned away, with the last 4 digits of the number and the reason.

Limits and file format

• Up to 50 MB and 500,000 rows in one upload. The server enforces this after you press Import, so split a bigger file.
• Separators: comma, semicolon or tab on the screen.

Note

The import service also accepts a pipe-separated file, but the screen’s preview detects only comma, semicolon and tab. Save a pipe-separated file as a comma or tab file before uploading it on the screen.