Home visits
Field teams dispatch appointments to customer addresses and track progress and proof of work.
Field teams dispatch appointments to customer addresses and track progress and proof of work.
Where to find it
Web: open Bookings. Desktop: Business → Bookings, using the same record paths. Disabled modules or missing read permission remove the navigation entry.
| Screen / tab | Web path | Usage | Desktop |
|---|---|---|---|
| Home visits | /field-service | List, view or tab | Native screen |
Start working
Step 1
Dispatch with appointment/address.
Step 2
Assign or reassign a worker.
Step 3
Advance status.
Step 4
Complete with proof/signature or cancel.
Settings
Option-by-option configuration and screen paths: Settings guide.
- Service area ·
/settings/field-service
Permissions and limits
Before you start
Out-of-area dispatch is refused. Required signatures can prevent completion.
Role capabilities: Read (read), Write (write), Delete/archive (delete), Manage (manage), Export (export), Own records only (own_records_only).
Own-record restrictions apply equally to lists, records and Era. Record state or missing data can refuse an otherwise permitted action.
Ask Era
Show today’s visits by worker and status.
Select relevant records for Era context. Era respects modules/roles; external or confirmation-sensitive work can stop for approval. Use era tools in the terminal to inspect currently available tools.
Automation and events
These declared events are available to module-event triggers. Subscribing does not configure the next operation; choose recipients, conditions and actions separately.
Operation details
The inventory includes record, configuration, visitor and background flows. IDs support Era/automation; not every row is a menu button. Asterisks mark required inputs. Unmapped rows do not imply a visible control.
| Operation and ID | Inputs | Permission | Screen or flow |
|---|---|---|---|
Dispatch a visit · field_service.dispatch | Appointment *, Who goes, Address | Write | /field-service |
Send somebody else · field_service.reassign | Visit *, Who goes * | Write | /field-service |
Update the visit · field_service.advance | Visit *, Now * | Write | /field-service |
Finish the visit · field_service.complete | Visit *, What was done, Signature, Photos | Write | /field-service |
Call off the visit · field_service.cancel_visit | Visit *, Why | Write | /field-service |
Related guides
Settings
Options, screen paths and defaults.
Workflows
Operations managers connect triggered blocks on a canvas with conditions, loops and approval waits.
Bookings
Bookings — modules and detailed settings
Technical sources
packages/os-kernel/src/modules/field-service.ts, packages/os-kernel/src/modules/index.ts, apps/studio/lib/os/navigation.ts, apps/studio/lib/os/settings-groups.ts, apps/era-station/apps/web/src/era/business/screens.ts.
Screen pictures
Status summary
Five cards summarize Total, Pending, Confirmed, Completed and Cancelled within the queue period (from seven days ago onward). Dispatch, today, tomorrow and on-the-road tabs remain. Completed or cancelled visits take precedence over their booking status.