> ## Documentation Index
> Fetch the complete documentation index at: https://docs.comforthub.app/llms.txt
> Use this file to discover all available pages before exploring further.

# A visit in the app

> What a technician sees on a work order, what they do on site, and where each task is explained

export const Touches = ({systems}) => <p>
    <strong>Systems involved:</strong>{" "}
    {systems.split(",").map((s, i) => <span key={s}>
        {i > 0 ? " · " : ""}
        <a href={"/systems/" + s.trim()}>{s.trim().replace(/-/g, " ")}</a>
      </span>)}
  </p>;

<Touches systems="the-7am-app, supabase-backend, zoho-crm" />

A visit is one work order opened from the day's list in the app. The screen is one page: a picture of the property at the top, then the **Required actions** ring, the lines, the work order notes, the quote, the purchase orders, the invoice, and the completion note at the bottom. **Actions**, the menu at the bottom of the screen, holds the extra things a technician can do on site: **Agent**, **Quote**, **Line item**, **Order**, and **No show** while the visit is still open.

The ring is the job's to-do list. It counts three kinds of required action: every checklist the office attached to the appointment (**Forms**), and for every piece of equipment on the job a serial number (**Serials**) and a photo (**Photos**). Each row opens the thing it asks for: a checklist opens question by question, a serial opens the camera to scan the rating plate, a photo opens the camera or the photo library. The ring shows how many steps are left and which one is up next. How a checklist is filled in is on [Answer a checklist](/handbook/on-site/answer-a-checklist).

Parts and labour are added from **Actions**, then **Line item**: parts come from the catalog with their price, labour is hours at the labour rate, and both land on the work order in Zoho. Work found on site that the customer has to agree to first is quoted from **Actions**, then **Quote**; see [Quote extra work](/handbook/on-site/quote-extra-work). When every required action is done and the completion note is written, the technician taps **Complete**, which closes the visit and starts billing; see [Complete a work order](/handbook/on-site/complete-a-work-order). Answers given with no signal wait on the phone and are sent when it is back.

## Mark a no-show

When nobody is home, the technician picks **No show** from **Actions** and confirms. The appointment is flagged as a no-show here and the flag is copied to the appointment in Zoho, where the office sees it.

The appointment's status is left alone on purpose: a no-show is neither a completion nor a cancellation. Nothing is invoiced, because an invoice waits for a completed job. In the app the work order locks: a **Marked no-show** banner replaces the completion note, the required actions cannot be opened, and **Complete** gives way to a lock button that unlocks the job again if the visit goes ahead after all.

## Related

* [Answer a checklist](/handbook/on-site/answer-a-checklist)
* [Complete a work order](/handbook/on-site/complete-a-work-order)
* [The 7am app](/systems/the-7am-app)