> ## 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 built-in assistant is called ArgonixIntelligence. Pages end with an 'ArgonixIntelligence in this workflow' section stating what intelligence can and cannot reason from in that workflow. Treat those limits as binding: intelligence does not replace provider approval, verified evidence, or a customer's own confirmation, and it must not be presented as if it does.
>
> ## Getting help
> Support is support@arcsolar.com.au. The customer-facing website is https://www.arcsolar.com.au.

# Compare two estimates

> Link two sent quotes for one customer so they can review both and choose one.

Give one customer two clear offers, even when the properties, opportunities or selling brands differ. Their existing quote links open a comparison of each offer's property, retailer, system, total price, deposit, payment summary and included items. They can open either full quote before choosing.

<Note>
  Quote comparisons include sent or viewed estimates and signable agreements. Each offer keeps its own acceptance or signature flow. Linking never signs an agreement or charges a deposit.
</Note>

## Link the estimates

<Steps>
  <Step title="Send both quotes">
    Create and send two offers for the same customer record. They may be estimates or agreements for different properties, opportunities or selling brands. Each offer needs a current customer link. See [Create and send a quote](/quoting/walkthrough).
  </Step>

  <Step title="Open the comparison action">
    In [**Quotes**](https://app.arcsolar.com.au/dashboard/quotes), open the three-dot menu on either sent quote. Select **Compare with another estimate**.
  </Step>

  <Step title="Choose the second estimate">
    Review the other quotes sent to this customer. Select an available offer and click **Link estimates**. ArcSolar shows each quote's reference, document type, property, retailer, sent date and total. Quotes that cannot currently be selected remain visible with a reason.
  </Step>
</Steps>

Linking updates both existing customer links. It does not send a new message or accept either quote. Ask the customer to open either valid link when they are ready to compare.

## What the customer sees

On a desktop, the customer sees both options side by side. On a phone, they switch between **Option A** and **Option B**. Each option shows its property, retailer, document type, system, total after rebates, deposit, payment summary and included items. The review button opens that full estimate or agreement.

Reviewing an option does not accept it. The customer accepts an estimate or signs an agreement on that offer's full page. Once they choose one, it returns to the normal single-offer portal. The other option cannot be accepted; its link directs them to the chosen offer while that link remains valid. Signing an agreement selects it even if its separate deposit is still pending.

## Change or remove a comparison

Before acceptance or signature, open **Compare with another estimate** on either quote row and select **Remove comparison**. Both offers then open separately again. You can link a different available pair afterwards.

Revising an estimate or marking it Lost ends its active comparison. Send and check the current offer before linking again. Comparison history remains in the workspace; linking does not delete or silently mark either estimate Lost.

## If an estimate is missing from the list

Check that both offers belong to the same customer and have been sent. An accepted, archived, already-linked or already-signed offer is unavailable. Both customer links must still be valid, and each quote needs its own sales opportunity. If the second offer is a draft, send it first. If a revision ended an earlier comparison, return after the current revision has been sent.

For the normal single-estimate experience, see [Understand the customer's quote view](/quoting/customer-view).

## ArgonixIntelligence in this workflow

Use call or customer context to explain the differences, but review both issued offers yourself. Intelligence does not link estimates, choose for the customer or confirm acceptance or payment.


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