> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neuroncx.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Imports: Bulk Loading Leads and Contact Records

> Seed the Transactions Console with existing patient or prospect data, migrate records from other CRMs, and make imported leads immediately available for workflows.

The Imports channel lets you bulk-load existing patient and prospect records into Neuroncx AI so your team can begin engaging them through automated workflows and agent-assisted outreach without waiting for organic lead capture. Whether you are migrating data from a previous CRM, uploading a new referral list, or seeding a campaign from an external database, Imports gets your records into the Transactions Console quickly and with full source attribution.

## When to Use Imports

Imports are the right tool when you have a batch of lead or patient records outside of Neuroncx AI that need to be worked through your engagement pipeline. Common scenarios include:

* **CRM migrations** — moving patient records from a legacy system to Neuroncx AI as your primary platform.
* **New lead lists** — uploading a referral list from a partner organisation or a segment from a marketing campaign run externally.
* **Event follow-ups** — loading attendee records from a health fair, webinar, or clinic open day for immediate follow-up.
* **Offline bookings** — adding patients who booked through a call centre or in person, so their records exist alongside digitally acquired leads.

## Preparing Your Import File

Neuroncx AI accepts lead records in CSV format. Before uploading, ensure your file meets the required structure to avoid import errors.

**1. Use the Standard Column Headers**

Your CSV file must include the required columns: `name`, `phone`, `email` (optional), `source`, and `notes` (optional). Additional columns are supported as custom attributes — check the import template available in the platform for the full field list.

**2. Validate Phone Number Formats**

All phone numbers must be in E.164 international format (e.g., `+919876543210`). Numbers in local format without a country code will fail validation. Run a format check on your file before uploading if you are working with records from multiple regions.

**3. Set the Source Attribute**

Populate the `source` column with a consistent label that identifies the origin of these records — for example, `referral-partner`, `offline-event`, or `legacy-crm`. This label becomes the source attribute used in the Patient Source Attribution panel.

**4. Remove Duplicate Records**

Deduplicate by phone number before uploading. Neuroncx AI checks for existing records on import, but uploading clean data avoids partial-match conflicts and keeps your pipeline accurate.

> [!WARNING]
>
> Importing records without a valid consent flag may violate data protection regulations in your region. Ensure that every record in your import file includes documentation of the patient's or prospect's consent to receive communications from your organisation before you upload.

## Running an Import

**1. Navigate to Channels → Imports**

Open the Imports section from the Channels menu. You will see a history of previous imports alongside their status and record counts.

**2. Upload Your CSV File**

Click **New Import** and select your prepared CSV file. The platform validates the file structure and previews the first several rows before you confirm the upload.

**3. Map Columns (If Needed)**

If your column headers differ from the standard template, use the column mapping interface to match each of your headers to the correct Neuroncx AI field. Save the mapping as a template if you plan to import from the same source regularly.

**4. Confirm and Submit**

Review the record count and field mappings, then submit the import. Large files process in the background — you will receive a notification when the import is complete.

## What Happens After Import

Once an import completes, each record appears in the **Transactions Console** as a new lead with the source attribute you specified. From there, the leads are available for:

* **Workflow targeting** — include the imported source in segment filters to enrol these leads in an automated WhatsApp or email engagement sequence.
* **Agent outreach** — agents can see the imported records in their Transactions Console queue and begin placing calls or sending messages immediately.
* **Campaign assignment** — tag the imported segment and use it as the audience for an upcoming campaign directly from the Channels dashboard.

> [!TIP]
>
> After a large import, run a quick spot-check in the Transactions Console by filtering by the import source. Verify that names, phone numbers, and any custom attributes have mapped correctly before launching workflows against the new records.

## Tracking Imported Lead Performance

Imported leads are tracked as their own source in the **Patient Source Attribution** panel of the Channels Overview dashboard. This lets you measure how well imported records convert compared to organically acquired leads — a useful indicator of the quality of your external data sources.

If a particular import source consistently shows low conversion rates, investigate whether the records are outdated, whether consent levels are lower, or whether the automated flow needs to be adjusted for a different entry-point intent.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.