> ## 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.

# Lead management

> See how many leads came in, how they were followed up and how many converted.

**Open:** [**Reporting → Lead management**](https://app.arcsolar.com.au/dashboard/reporting?reportTab=lead-management).

| Role | What the report covers |
| - | - |
| Administrator, Operations, Finance | All leads |
| Sales representative | Leads assigned to you |
| External marketing | The customer records shared with you. This is the only report you see |

## Choose the period

Use **Reporting period** at the top right: **Last 30 days**, **Last quarter** or **Last 12 months**. Leads are grouped by the date they were received.

## What it shows

**Summary:** **Leads received**, **Contacted**, **Qualified** and **Converted**.

**Disposition breakdown:**

* **Lead dispositions** shows where each lead stands now. Each lead counts once.
* **Call outcomes** shows the result of each call made to those leads in the period.
* Sort by **Most common** or **Alphabetical**, show **Count** or **Percentage**, and switch between chart and table.

**Source quality & follow-up:** one row per **Lead sellers** (lead seller or sub-source) or per **Sales reps**. Columns are **Received**, **Contacted**, **Qualified**, **Converted**, **Conversion**, **No calls in period** and **Calls**. Select a column heading to sort. Use the search box to find a name.

## Read it fairly

* **Contacted** means a first response was recorded: a call, SMS or a manual update.
* A missed call does not mean the lead was poor.
* Recent leads and small numbers need more time before you judge them.
* A lead stays credited to the person or Meta connection that brought it in.

External marketing users also see an **All accounts** button. It shows lead delivery, sales outcomes and Meta connection status across every business that shares records with you.


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