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

# Configure when the customer must be present

> Understand how customer presence affects visits, notifications, and schedule protection.

Mark a service as requiring customer presence when access or delivery depends on the customer being available. Presence changes both the field team's expectations and the timing promise Sweeply can send to the customer.

## How Sweeply resolves presence

For each order task, Sweeply uses the first available value in this order:

1. An explicit value on the order task
2. The linked subscription task value
3. The service default

If any task on an order requires presence, the complete visit requires customer presence.

## Effect on before-delivery messages

Your notification settings contain separate timing profiles:

* **Customer must be present** defaults to an arrival buffer around the scheduled visit.
* **Customer does not need to be present** defaults to communicating the service date only.

When a presence-required notification communicates a time interval, automatic planning preserves that interval. A date-only notification preserves the communicated service date.

## Change the default

<Steps>
  <Step title="Open the service">
    Go to **Settings** > **Services** and edit the service.
  </Step>

  <Step title="Set Customer present">
    Turn the setting on when the customer normally must be available for this service.
  </Step>

  <Step title="Review existing recurring work">
    A changed service default affects tasks that still inherit it. Explicit order or subscription task values continue to override the default.
  </Step>
</Steps>

<Note>
  Customer presence does not by itself choose a time. It determines which communication profile and customer promise apply after Planning schedules the order.
</Note>