> 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/customers-and-work/scheduling/let-technicians-schedule-backlog-visits.md). # Let technicians schedule backlog visits Normally the office places every backlog visit on the calendar. With technician self-scheduling turned on, technicians get an **Open** tab in the mobile app that lists eligible single-technician backlog visits they're allowed to pick up — each one shows the property and address, the work, any due date, and the visit's arrival window when one is set — and they can add one to their own schedule by choosing a date and then a time: **Pick a time** for an exact start, or **As last visit**, which places it after whatever they already have that day (it reads **First visit** when they have nothing scheduled yet). The visit lands on their calendar immediately, leaves the backlog, and shows up on the Scheduling page like any other scheduled visit. Technician self-scheduling is off until an administrator turns it on and saves. While it is off, technicians keep the existing Day, Week, and Month views and cannot list or book backlog visits. ## Turn it on and choose a default Go to **Settings → Technician App** and turn on **Let technicians schedule backlog visits**. Then pick who can self-schedule by default: * **All technicians** — every technician sees the business's eligible single-technician backlog visits in their Open tab. * **Specific technicians** — only the technicians you select see them. * **No technicians** — nothing is open by default; you open up visits one at a time from the visit itself (see below). Select **Save** to apply your changes. The default applies to every backlog visit that doesn't have its own override. ## Override a single visit When self-scheduling is on, the visit form (create a visit, or edit an unscheduled one) shows a **Technician self-scheduling** field. It reads **Business default** unless you change it — pick **All technicians**, **Specific technicians** (and choose them), or **No technicians** to make that one visit more or less available than the default. For example, with the default set to **No technicians**, you can release just the visits you choose; with the default set to **All technicians**, you can hold back a sensitive visit by setting it to **No technicians**. ## What happens when a technician books one * The visit is scheduled on the technician's chosen date, assigned to them, and removed from the backlog and from every technician's Open tab. With **As last visit** (or **First visit** on an empty day), scheduling places it after their existing visits that day. * The job's timeline records the scheduling, with the technician as the actor. * Visit reminders for the visit's contacts are created the same way as when the office schedules it. * Due dates are advisory: the app warns the technician when their chosen time is past the due date, but doesn't block the booking. * If two technicians go for the same visit, the first booking wins — the second sees that the visit is no longer available and the list refreshes. * Visits that require more than one technician can be self-scheduled too, at an exact time only, and every required slot is filled in the one booking: when the visit's allowed technicians exactly match the required count, that crew is booked together; when more technicians are allowed, whoever claims the visit picks their teammates. Technicians on an older app version don't see crew visits. > **Where to find it:** Settings → Technician App → Scheduling; and the Technician self-scheduling field on the visit form for unscheduled visits ## Related guides * [Work with the scheduling backlog](/customers-and-work/scheduling/work-with-the-scheduling-backlog.md) * [Create a new visit](/customers-and-work/scheduling/create-a-new-visit.md) * [Create visits for many properties at once](/customers-and-work/scheduling/create-visits-for-many-properties-at-once.md) * [Schedule an open visit from the mobile app](/field-operations/mobile/schedule-an-open-visit.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/customers-and-work/scheduling/let-technicians-schedule-backlog-visits.md?ask=&goal= ``` `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.