Ask about any job, crew or permit in plain English. The assistant reads the whole record, proposes the change, and by default waits for a person to approve it.
Opening to installers in waves.
Ask about a project and SunrAI reads its tasks, files, photos, messages and schedule before it answers.
Yes. Both open tasks look finished: the was uploaded at 9:12 AM, and the confirms the interconnection application was received.
Want me to propose marking both tasks done? Phase follows the tasks: Whitcomb would move to Procurement.
Source: Files, Building permit.pdf, uploaded today at 9:12 AM.
Source: Messages, utility email, interconnection application received at 8:55 AM.
Sample data.
The assistant does real work on your pipeline. By default it asks first, and a person owns anything that can't be undone.
| Kind of work | The assistant | You |
|---|---|---|
| Answers | Reads any job, crew, photo or message to answer you. | Nothing to approve.Reading changes nothing. |
| Task changes | Proposes them as a dry run, showing exactly what would change. | Approve or dismiss.By default every change waits for approval, is logged, and can be undone for 24 hours. |
| Messages, cancellations, lead conversions | Can propose them. | Always your call.These can't be undone, so they never run without a person. |
Sample data.
Describe the report you need. SunrAI builds it as a draft view, and you decide whether to keep it.
Sample data. In SunrAI, a view stays a draft until you save it.
The assistant reads every job, photo and message, so it can do real work. What keeps it safe is how it's allowed to act.
Questions about any job, a morning briefing, the list of what's due. Reading changes nothing.
Task changes arrive as a dry run. A person approves, the approval is logged, and the change can be undone for 24 hours.
Sending a message, cancelling an appointment or converting a lead always takes a person.