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

# Inbox

> One list of everything that needs you: due tasks, missed calls, mentions and customer uploads.

The Inbox collects your alerts in one place. Start your day here.

Open [**Inbox**](https://app.arcsolar.com.au/dashboard/inbox) from the sidebar. The Inbox button at the top of each page shows how many items need attention.

> [!NOTE]
>
> The Inbox is for alerts. Customer text messages live in [Comms](https://docs.arcsolar.com.au/customers/comms.md).

## What lands in your Inbox

| Type | Example |
| - | - |
| **Tasks** | A follow-up assigned to you is due, overdue or waiting |
| **Missed calls** | A customer called and nobody answered |
| **Incoming calls** | A call came in on your line |
| **Mentions** | A teammate tagged you in a note |
| **Customer uploads** | A customer sent switchboard photos or a bill |
| **Quotes** and **Projects** | Updates on work you are part of |
| **Availability** | Your booking hours need setting up or reviewing |
| **Warnings** | Something that needs checking |

## Work through it

**1. Start with Priority**

The **Priority** tab shows items that still need action. **Other** holds the rest.

**2. Open an item**

Select it to see the details on the right, such as the customer, task and due date.

**3. Act on it**

Use the buttons in the details panel, such as **Open task**, **View customer** or **Open Comms**.

**4. Clear it**

Select **Mark as read**, or dismiss it on this device.

![The Inbox with Priority and Other tabs, a list of alerts, and an AI-detected follow-up open on the right with Open task, View customer and Actions buttons.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/cu-inbox.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=5664f0d0fb74121c6dcca3d27e9ed500)

A task alert open in the Inbox. Sample data.

> [!WARNING]
>
> Marking a task alert as read does not complete the task. Open the task and select **Complete task**. See [Tasks](https://docs.arcsolar.com.au/customers/tasks.md).

## Find and sort alerts

* **Search notifications** finds an alert by its text.
* **Filter notifications** filters by **Notification type**, **Work area** (Comms, Finance, Operations, Reporting, Sales) or **Unread alerts only**.
* **Inbox display options** groups by type or work area, and sorts **Newest first** or **Oldest first**.
* **Mark shown notifications read** clears every alert in view. Tasks stay open.

Read history shows your latest 30 updates.

To choose which alerts also reach you by email or SMS, see [Notifications](https://docs.arcsolar.com.au/setup/notifications.md).

[Continue with**Comms**](https://docs.arcsolar.com.au/customers/comms.md)


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