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

# Comms

> Read and reply to customer texts, see every call and message in one thread, and send bulk SMS.

ArcSolar comms preview

Comms is where your team talks to customers. Each customer has one conversation thread with their texts, calls, emails, quotes, payments and internal notes in order.

Open [**Comms**](https://app.arcsolar.com.au/comms) from the sidebar. It opens as **ArcSolar Comms** with four tabs:

| Tab | Use it to |
| - | - |
| **Messages** | Read and reply to customer SMS |
| **Phone** | Make calls and review call history. See [Calls and SMS](https://docs.arcsolar.com.au/customers/calls-sms.md) |
| **Automation log** | Check which automatic messages were sent or skipped |
| **Bulk SMS** | Send one message to many customers |

Finance and External marketing users see a read-only view without **Automation log** or **Bulk SMS**.

## Find a conversation

The left sidebar sorts conversations into mailboxes:

* **Inbox**: conversations to work on
* **Mentions**: notes where a teammate tagged you
* **Snoozed**: conversations hidden until a set time
* **Sent by me**: conversations you have messaged
* **Automated conversations**: threads with automatic messages
* **All conversations**, **Unassigned** and **Spam**

Above the list, choose **All**, **Open**, **Snoozed** or **Closed**. **Filter conversations** filters by **Read state**, **Assignee**, **Channel** and **Priority**. **Search loaded conversations** finds a name or number.

## Reply to a customer

**1. Open the conversation**

Read the latest messages, calls and notes first. The right panel shows the customer's details and a link to their record.

**2. Assign it to yourself if needed**

If the box says **Assign yourself to reply**, the conversation belongs to someone else. Ask a manager to assign it to you.

**3. Write and send**

Stay on the **Reply** tab, type your message and select **Send**.

**4. Check the status**

Each message shows its status, such as **Delivered**. Failed messages show **Delivery failed**.

![The Comms reply box with Reply and Internal note tabs and the placeholder Assign yourself to reply.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/cu-comms-composer.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=e9abc7bfc6a3e180f27a0093f01fac7a)

The reply box, with Reply and Internal note tabs. Sample data.

Comms sends SMS text only. Images and videos can't be sent or received. Long messages can be split into several SMS, which may cost more.

Always respect opt-outs. If a customer replies STOP or asks not to be contacted, do not message them again.

## Leave an internal note

Select the **Internal note** tab, write your note and send it. Notes are visible to your team, never the customer. Mention a teammate to notify them. They see it in **Mentions** and in their [Inbox](https://docs.arcsolar.com.au/customers/inbox.md).

## Manage a conversation

Select **Conversation actions** at the top of the thread.

![The Conversation actions menu showing View profile, Move to Spam, Unpin conversation, Snooze conversation, Remove priority, Close conversation and Assign conversation.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/cu-conversation-actions.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=c573e18b63ae722437b36faf99cbd828)

Conversation actions. Sample data.

| Action | What it does |
| - | - |
| **View profile** | Opens the customer's details |
| **Move to Spam** | Moves junk out of your mailboxes |
| **Pin conversation** | Keeps it at the top of the list |
| **Snooze conversation** | Hides it **For 1 hour**, **Until tomorrow at 9:00** or **Until next week** |
| **Mark priority** | Flags it as important |
| **Close conversation** | Marks it done. **Reopen conversation** brings it back |
| **Assign conversation** | Gives it to a team member, or **Unassign** |

Snoozing, closing, priority, spam and assigning are for Administrators and Operations.

## Start a new conversation

1. Select **New message** at the top of Comms.
2. Search for the client name or phone number, or type an Australian mobile number.
3. Choose the **From** line if you have more than one. Pick it before you write, because replies always use the conversation's original number.
4. Write your message and send it.

You need an SMS-enabled phone number assigned to you. You can also start a text from a customer: **Actions → Communicate → Send SMS**.

## Send a bulk SMS

**1. Open Bulk SMS**

Select the **Bulk SMS** tab. Your leads are listed under **Recipients**.

**2. Choose who gets it**

Use **Filters** to narrow by **Sales rep**, **Status**, **Purchased** or **Lead source**. Tick customers, or select **Select all**.

**3. Write the message**

Type it under **Message** (up to 1,600 characters). The recipient count updates as you select.

**4. Send**

Select **Send SMS**, check the message in the confirmation, then select **Send SMS** again.

![The Bulk SMS tab with a recipients table of leads and a message box with a Send SMS button.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/cu-bulk-sms.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=ff455d3796076c4ea916fff67e07947d)

Bulk SMS. Sample data.

## Check automatic messages

The **Automation log** shows what ArcSolar sent on its own, and what it chose not to send. Use **Customer messages** or **Team alerts**, then filter by **Outcome**. Each entry shows the message type (for example **Appointment confirmation** or **Quote follow up**), the customer and the result, such as **Sent** or **Not sent**. Select **Open customer →** to check the record.

[Continue with**Calls and SMS**](https://docs.arcsolar.com.au/customers/calls-sms.md)

* Workflow controls (snooze, close/reopen, priority, spam, assign/unassign) are enabled for Administrator, Operations and Developer. Sales representatives can reply but cannot use these controls. Finance and External marketing are read-only; External marketing sees the Phone tab as "Call logs" and neither role sees Automation log or Bulk SMS.
* Reply placeholder "Assign yourself to reply" shows when the user cannot reply to that conversation; closed conversations show "Reopen this conversation before replying".
* Snooze options: "For 1 hour", "Until tomorrow at 9:00", "Until next week". Snoozed conversations show **Wake conversation**.
* New conversation dialog (live data): "Start a new conversation", recipient search "Search client name or phone number", optional "Client name", **From** line picker ("Choose before writing. Replies and retries use their original number."), message. Requires an active, SMS-enabled number assigned to the user. In the demo, **New message** links to Customers instead.
* Bulk SMS message max length is 1,600 characters. Confirmation dialog title "Send SMS to N recipients?" with body "The same message will be sent to your selected customers."


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