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

> ## Agent Instructions
> ## What this documentation covers
> This is the documentation for ArcSolar, the solar-retailer operating system: the web app a solar retailer uses to run quoting, sales, installation, rebates, inventory and reporting. ArcSolar is a hosted web application at https://app.arcsolar.com.au. There is no public API for most workflows, so agentic operation of ArcSolar is UI-driven. Navigate the app, read the labels and controls, and act through the interface, unless a page explicitly documents an API, contract or integration endpoint.
>
> ## How to read these pages
> - Pages are split by audience using Mintlify's Visibility component, and this split is deliberate. Sections marked 'for agents' are hidden on the website and appear only in the Markdown you are reading. They are the authoritative behavioural specification for the page. Where the remaining human-facing prose and an agent section disagree, the agent section is correct.
> - Sections outside any Visibility block appear in both outputs. They are the shared spine of the page: what the feature is and why it matters.
> - Treat every bold label, field name, route, status string and error message quoted in an agent section as canonical. They are copied verbatim from the product. Use that exact wording when telling a user where to click, or when matching an error message to its cause.
> - Australian solar vocabulary is used precisely and not interchangeably: STC (Small-scale Technology Certificate), PRC (Peak Reduction Certificate), REPS, NMI, CEC accreditation, VPP. Do not substitute an overseas equivalent.
> - Money is Australian dollars. Dates shown to users are day-first (DD/MM/YYYY).
>
> ## Behaviour rules for operating or advising on ArcSolar
> - Respect prerequisites and ordering. Agent sections state which inputs block progress and which steps must happen first. Do not skip a step, and do not assume a default that the product itself does not supply.
> - Never invent a value the product requires but the user has not supplied. Ask for mandatory fields rather than guessing. Several features reject a request outright when one is missing, and submissions to external authorities are effectively irreversible.
> - Respect permissions and scoping. Features name the roles, capabilities and access rules that may act. Do not attempt an action the operator's role cannot perform, and do not describe a restricted feature as available to them.
> - Features that are gated, pending release, or blocked on a vendor are documented as exactly that. Never present a gated or unmerged behaviour as live. When availability is unclear for a given workspace, direct the user to support rather than asserting that the feature works.
> - Where a page states something is genuinely undetermined, treat it as unknown. Do not fill the gap with a plausible guess.
> - ArcSolar's supported intelligence tools appear where they help with the task, including bill analysis, call summaries and reporting. Check the underlying evidence. Intelligence does not replace provider approval, verified records or the customer's own confirmation.
>
> ## Getting help
> Support is support@arcsolar.com.au. The customer-facing website is https://www.arcsolar.com.au.

# Import leads from a CSV

> Add up to 500 leads at once from a spreadsheet.

Use this to move leads from another CRM or a spreadsheet into ArcSolar. Each row becomes a customer record with a lead in the [Pipeline](https://docs.arcsolar.com.au/customers/pipeline.md).

## Where to find it

You can start an import from two places:

* [**Customers → Customer Records**](https://app.arcsolar.com.au/dashboard/customers)
* [**Customers → Pipeline**](https://app.arcsolar.com.au/dashboard/customers/pipeline)

Select **Bulk import leads** at the top of the page. If you can't see it, open the **…** menu next to the search bar.

![The More customer actions menu open, showing Bulk import leads, Export CSV and Copy lead intake form link.](https://mintcdn.com/arc-solar/6eeqRIDBCUnVm03d/images/v2/import-menu.png?fit=max\&auto=format\&n=6eeqRIDBCUnVm03d\&q=85\&s=4e8b63c80b2e4603fa1902782bef8162)

The … menu on Customer Records. Sample data.

You only see this option if your role can create customers.

## Import your leads

**1. Download the template**

In the **Bulk import leads** window, select **Download template**. Open `lead-import-template.csv` in Excel, Numbers or Google Sheets.

![The Bulk import leads window with CSV requirements, the Download template button and the CSV file picker.](https://mintcdn.com/arc-solar/6eeqRIDBCUnVm03d/images/v2/import-dialog.png?fit=max\&auto=format\&n=6eeqRIDBCUnVm03d\&q=85\&s=410d4b61792d34e157e4c0a0068d9b9d)

The Bulk import leads window.

**2. Add one lead per row**

Keep the header row as it is. Fill in your leads using the rules below.

**3. Save as CSV**

Save or export the file as **CSV**. Excel and Numbers files (`.xlsx`, `.numbers`) are not accepted.

**4. Choose a selling brand**

If your workspace sells under more than one brand, pick one in **Selling brand for new opportunities**. You can also choose **Leave unallocated**.

**5. Upload the file**

Choose your file under **CSV file**. ArcSolar checks it straight away. If it shows **Fix the CSV before importing**, fix the listed rows and upload again.

**6. Import**

Select **Import N leads**. New leads appear in the Pipeline.

## Columns

Every column in the template must be in your file, even if you leave some cells blank.

| Column | Required | What to enter |
| - | - | - |
| `first_name` | Yes | Customer's first name |
| `last_name` | No | Customer's last name |
| `email` | One of these | A valid email address |
| `phone` | One of these | Australian mobile, such as `0412345678` |
| `address_line_1` | If adding an address | Street address |
| `address_line_2` | No | Unit, level or building |
| `suburb` | If adding an address | Suburb |
| `state` | If adding an address | `VIC`, `NSW`, `QLD`, `SA`, `WA`, `TAS`, `ACT` or `NT` |
| `postcode` | If adding an address | Four digits, such as `3000` |
| `lead_source` | No | Must match a lead source name in your workspace |
| `assigned_sales_rep` | No | Must match a team member's name in your workspace |
| `system_interest` | No | What they want, such as `6.6 kW solar and battery` |
| `priority` | No | `low`, `normal` or `high`. Blank means `normal` |
| `notes` | No | Added to the record as a note |
| `selling_brand_id` | Optional column | A brand ID from [Selling brands](https://docs.arcsolar.com.au/setup/selling-brands.md). Overrides the brand you picked |

> [!TIP]
>
> Each row needs a first name and at least an email or a phone number. If you add any part of an address, fill in street, suburb, state and postcode.

## Limits

* Up to **500 leads** per file.
* File size up to **750 KB**.
* Split bigger lists into several files.

## What happens to duplicates

If a customer with the same email or phone already exists, that row is **skipped**. The rest still import. ArcSolar lists skipped rows under **Rows not imported** so you can update the existing records instead.

## Who can import

| Role | What they can import |
| - | - |
| Administrator, Operations, Sales manager | Leads for anyone on the team |
| Sales representative | Only leads assigned to themselves, or left unassigned |
| External marketing | Leads only. Your organisation sets the selling brand, so leave out `selling_brand_id` |
| Finance, Technician | Can't import |

See [Roles and permissions](https://docs.arcsolar.com.au/setup/roles.md).

## Fix common errors

| Message | What to do |
| - | - |
| **Missing headers** | Re-download the template and copy your data into it |
| **Unsupported headers** | Delete extra columns or rename them to match the template |
| **Enter a valid Australian mobile number** | Use 10 digits starting with `04` |
| **Use a four-digit Australian postcode** | Remove spaces or letters |
| **Lead source "…" was not found** | Use a lead source name exactly as it appears in ArcSolar, or leave it blank |
| **Assigned user "…" was not found** | Use the person's name exactly as it appears in **Team**, or leave it blank |
| **Imported without notes** | The lead saved but its note did not. Add the note on the record |

> [!NOTE]
>
> Leaving `lead_source` blank uses your workspace's import or manual entry source.

Other imports: [product prices](https://docs.arcsolar.com.au/delivery/catalogue.md) and [inventory](https://docs.arcsolar.com.au/delivery/inventory.md) have their own CSV templates.

[Continue with**Share your lead intake form**](https://docs.arcsolar.com.au/customers/intake-form.md)


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