> ## Documentation Index > Fetch the complete documentation index at: https://docs.deepblocker.ai/llms.txt > Use this file to discover all available pages before exploring further. # Add the people you will call > Add one person at a time or import a CSV, with the consent fields DeepBlocker needs before a call, plus tags and filters. The people you test are contacts. Each one needs a name, a phone number, a role and a consent record. Without consent, a person is left out of every campaign. > [!NOTE] > > Before you start: you need written authorisation to test these people. Calls go to your own staff only. See [Before you test anyone](https://docs.deepblocker.ai/before-you-start.md). ## Before you start * A list of your own staff with phone numbers in international format, for example +44 7700 900123. * Their consent to security testing calls, and how it was given. * Departments and tags you want to filter by later. Groups are tags; there is no separate group. ## Steps: add one person **1. Open People** On the Red Team tab choose the **People** segment and click **Open people**. The page is titled **Contacts**. Click **Add Contact**. **2. Fill in Basic Information** **Name**, **Role** and **Phone Number** are required. Add an **Email** so the person gets a short training note after a call they fail, when coaching is on. **Department**, **Location** and **Manager** are optional. The manager is picked from your other contacts. **3. Record consent** Under **TCPA Consent & Compliance**, switch on "Contact has provided consent for security testing calls". Then set **Consent Scope**, **Consent Method** and, if useful, **Consent Details**. **4. Allow help desk impersonation, if you run help desk tests** Switch on **Can be impersonated in help desk tests** to let a test use this person's name, department and manager when it rings your help desk. The person is not phoned in a help desk test; only your help desk is. **5. Set a call window and tags, then save** **Earliest Call Time** and **Latest Call Time** default to office hours; pick a **Timezone**. Under **Tags**, type a tag and press Enter. Save the contact. ## Steps: import a CSV **1. Click Import** On the **Contacts** page click **Import**. A window opens with a drop area, "Drop your CSV file here" or "click to browse", and a **Download Template** button. **2. Prepare the file** The first line is the header. The import accepts this header, in this order: ```csv theme={null} name,phone,email,role,department,location,tags ``` The window lists the rules under **CSV Format Requirements**: required columns name, phone, role; optional columns email, department, location, tags; phone with the country code. **3. Drop the file and check the preview** The window shows **Preview (First 5 rows)**. Rows missing a name, phone or role are skipped. Read the note **TCPA Compliance Required**: by importing, you confirm that consent has been obtained for every person in the file. **4. Import** When it finishes you see **Import Complete** with the counts. Any rows that failed are listed under **Import Errors**. ### An example file | name | phone | email | role | department | location | tags | | - | - | - | - | - | - | - | | Priya Shah | +44 7700 900101 | [priya.shah@example.com](mailto:priya.shah@example.com) | Finance Manager | Finance | London | finance | | Tom Okafor | +44 7700 900102 | [tom.okafor@example.com](mailto:tom.okafor@example.com) | Service Desk Analyst | IT | Manchester | helpdesk | | Hannah Reid | +44 7700 900103 | [hannah.reid@example.com](mailto:hannah.reid@example.com) | Executive Assistant | Executive Office | London | exec-office | | Daniel Kowalski | +44 7700 900104 | | Warehouse Lead | Logistics | Leeds | logistics | Keep one tag per person in the file. Add more tags on the contact afterwards. ## Every column and field | Name | What it means | Default or limit | | - | - | - | | **Name** | The person's name, as the caller will use it | Required | | **Phone Number** | International format with country code | Required | | **Role** | Their job title | Required | | **Email** | For the coaching note after a failed call | Optional | | **Department** | Used for filters and for help desk impersonation | Optional | | **Location** | Free text | Optional | | **Manager** | Another contact. Used in help desk cover stories | Optional | | Consent switch | "Contact has provided consent for security testing calls". Required for all calling activities | Off | | **Consent Scope** | **Security Testing**, **Training** or **Awareness** | Security Testing | | **Consent Method** | **Electronic**, **Written**, **Verbal** or **Imported** | Electronic | | **Consent Details** | A reference or note about the consent | Optional | | **Can be impersonated in help desk tests** | Lets a help desk test use this person's name | Off | | **Opt-Out Status** | "Contact has requested to opt-out of future calls". Shown when editing | Off | | **Earliest Call Time** / **Latest Call Time** | The hours this person may be called | 09:00 onwards | | **Timezone** | The person's timezone, also used by quiet hours when the workspace sets none | | | **Risk Level** | **Low**, **Medium** or **High**. Shown when editing | | | **Tags** | Free words for grouping and filtering | | ## Filters The search box reads "Search by name, email, phone, or role...". Next to it are filters for **Department**, **Tags** and **Risk Level**, and lists for **TCPA Status** (consented, not consented, opted out), **Phone Status** (**Verified**, **Unverified**), **Status** (**Active**, **Inactive**), **Email** (**Has Email**, **No Email**) and **Campaign History** (**Has Participated**, **Never Contacted**). ## What "TCPA" means in the wizard On the **Authorise and launch** step the wizard shows **TCPA Consented** with the number of people who will be called. If some of the people you picked have no consent, it shows "\[n] contacts excluded" and "These contacts will not be called due to missing TCPA consent." Fix the consent on the contact and come back. ## What happens next Pick the people on the **Who is called** step of a campaign. Fair testing rules may hold or skip a person; see [Fair testing rules](https://docs.deepblocker.ai/vishing/fair-testing.md). For research on a person before a call, click **Research this contact (OSINT)** when editing them. ## Problems > [accordion] The import says 'Missing required columns' > > The header must contain name, phone and role, spelt exactly like that. Download the template from the window and paste your rows under its header. > [accordion] The import says 'Please select a valid CSV file' > > The file must be a .csv. Export from your spreadsheet as CSV, not as .xlsx or .numbers. > [accordion] Some rows were skipped > > A row is skipped when it has fewer values than the header, or when name, phone or role is empty. A comma inside a value also shifts the columns, so keep values free of commas. > [accordion] A person was not called > > Check three things: the consent switch is on, **Opt-Out Status** is off, and they are not in **Excluded people** under [Fair testing rules](https://docs.deepblocker.ai/vishing/fair-testing.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.