> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/mobile/open-a-visit.md).

# Open a visit in the mobile app

Open a visit to see everything a technician needs on site: scheduled time, customer, property, address, work orders, technician instructions, contacts, property phone number, asset groups, files, property notes, access info, and previous jobs or visits. If the office set an arrival window, it appears below a neutral-clock scheduled time; exact arrival-window visits do not use the red target or red start-time styling. If the window ends before you clock in, it turns red and says **Missed** until you arrive.

## Actions at the top

Depending on the visit and your permissions, the top of the visit includes actions for Add Summary or Edit Summary, Create Work Acknowledgment or View Work Acknowledgment, Start Inspection, On My Way, Clock In, and Clock Out.

If an action is missing but you need it for field work, contact your business's administrator to review your mobile role and permissions.

Clocking in logs the time that you began the visit and unlocks field actions such as Start Inspection. Asset Groups can be opened from the visit if you need to view or update equipment — tap a group to see its Assets — though most technicians will update assets through the inspection report flow.

## Property and contact details

Use the map icon to open directions. Tap phone numbers to call. If the visit has multiple contacts, open the contacts row to review the full list.

When an administrator enables **Add and edit contacts** under Settings > Team > Technician App, open **Contacts** to see every contact for the customer. You can create a customer contact or edit any contact's details, customer-level roles, and roles for the current property. This does not add or remove contacts on the visit. Without this opt-in setting, the existing visit contacts remain read-only.

Property details, notes, and access info are shared with the back office. Edits made from mobile update the same property record the office sees.

## Files and history

Property files remain with the property across jobs. Job files are only for the current job. The Previous Jobs and Visits section lets technicians review past work, visit notes, job files, inspection reports, services completed, and which technicians performed the work.

## Other techs here today

If another crew is scheduled at the same property today, the visit shows an Other techs here today card. Expand it to see their work type, status, and timing.

> **Where to find it:** Mobile app > Visits > tap a visit card

## Related guides

* [Use On My Way, Clock In, and Clock Out](/field-operations/mobile/on-my-way-clock-in-clock-out.md)
* [Add files, notes, and access info on mobile](/field-operations/mobile/add-files-notes-and-access-info.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.withessential.com/field-operations/mobile/open-a-visit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
