> ## 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. # Start guide > Get to know ArcSolar through one customer, one conversation and one quote. ArcSolar customers preview ArcSolar connects customer conversations, quotes and installation work. Start with a customer record and follow the work from there. ## Find your bearings Sign in to your workspace. **Rep Overview** shows what needs attention; **Customers** holds your customer records; **Quotes** holds your offers. Use app search with **⌘ J** on Mac or **Ctrl J** on Windows. [Workspace basics](https://docs.arcsolar.com.au/reference/workspace.md) covers navigation and personal settings. ## Work with a customer 1. Open **Customers → Customer Records** and search before adding someone new. 2. Check their contact details, installation address and assigned rep. 3. Read **Activity** before making a call or sending a message. 4. Leave a clear next action in **Tasks**, with an owner and a date. [Customer records](https://docs.arcsolar.com.au/customers/records.md), [calls and SMS](https://docs.arcsolar.com.au/customers/calls-sms.md), and [tasks](https://docs.arcsolar.com.au/customers/tasks.md) cover the details. ## Prepare your first quote Collect the [site information](https://docs.arcsolar.com.au/quoting/site-information.md) and electricity bill. Open **Quick Create Quote**, choose the customer, review their energy use and select the system. Check the total, payment schedule and customer preview before sending. Use a manager-approved practice record while learning. Stop at the preview; sending a quote or contacting a real customer creates real work. ## Take the next step * **Joining sales?** Follow the [seven short onboarding lessons](https://docs.arcsolar.com.au/sales-onboarding.md). * **Setting up a business?** Start with [organisation setup](https://docs.arcsolar.com.au/setup/onboarding.md) and the [setup checklist](https://docs.arcsolar.com.au/setup/checklist.md). * **Running delivery?** Read [the customer journey](https://docs.arcsolar.com.au/quickstart.md), then [projects and jobs](https://docs.arcsolar.com.au/delivery/projects.md). [Continue with**Create a quote**](https://docs.arcsolar.com.au/quoting/walkthrough.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.