---
schema_version: "1"
id: 98ff94539e80437c150d255068e15999808005b6cc80cca35a24e82a4fedd2b0
title: Create an Appointment Bundle Policy
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/fs_set_up_bundling_bundle_policy.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_bundle_policy.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bc2b1d8590a79e51aebbcd4615b5a15e2893cb51f01af98f8ee533e5b29e481c
description: Use the default policy, or create multiple policies. You can use the policies for manual bundling, automatic bundling, or both.
products:
  - Field Service
release: "264"
---
# Create an Appointment Bundle Policy

Use the default policy, or create multiple policies. You can use the policies for manual bundling, automatic bundling, or both.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">The Agentforce Field Service and Operations core features, managed package, and mobile app are available in <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d46180e69">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d46180e69 ">To create items:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d46180e69 ">Customize Application</td>

          </tr>
        </tbody>
      </table>

1. If your service appointments have custom fields, make sure to give the fields read access. See [Appointment Bundling Limitations](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_limitations.htm&release=264.0.0&type=5 "Review the limitations of Appointment Bundling.").
    1. From Setup, in the Quick Find box, enter Users, and then select **Permission Sets**.
    2. Click **Field Service Integration**.
    3. Click **Object Settings**.
    4. Click **Service Appointment**.
    5. For each custom field, select **Read Access**.
2. From the App Launcher, open **Appointment Bundle Policies**.
    
    If you don’t see Appointment Bundle Policies in the App Launcher:
    
    1. From Setup, in the Quick Find box, enter Users, and then select **Profiles**.
    2. On the Salesforce admin profile, click **Edit**.
    3. From Profile Detail, click **Edit**.
    4. Under Tab Settings, set the bundle tabs to **Default On**.
        
        ![Tab Settings](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_field_service-264-0-0-production-enus/3f7dceb9-dd70-454a-b49e-bbb4526a158d/support_field_service/images/fs_bundle_tabs.png)
    5. Save your changes and refresh your browser.
3. On the Appointment Bundle Policies page, click **New**.
4. Give the policy a unique name.
5. To make this policy available when the dispatcher manually bundles service appointments in the Classic Dispatch Console, select **Manual Bundling**.
6. To make this policy available when automatic bundling is triggered, select **Automatic Bundling** and enter the details. Automatic bundling includes two modes, Automated Bundling and Live Bundling. You can have manual bundling and automatic bundling enabled at the same time.
    
    1. For Priority, enter a unique policy priority number. The priority determines the order that the policies are applied.
    2. For Limit Amount of Bundle Members, enter the maximum number of bundle members to include, up to 200.
    3. For Limit Duration of Bundle, enter the maximum duration of a bundle, in minutes. The recommended limit is 240 minutes.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_field_service-264-0-0-production-enus/3f7dceb9-dd70-454a-b49e-bbb4526a158d/images/icon_note.png)
    
    Note The Limit Amount of Bundle Members and Limit Duration of Bundle fields are relevant only for automatic bundling, not for manual bundling.
7. For Filter Criteria, select an active recordset filter to determine the bundle members. Only the service appointments that meet the criteria are bundled.
8. To make sure that enough time is allocated for the bundle, calculate the difference between the bundle’s start time and the bundle’s end time. If that amount of time is shorter than the bundle’s duration, replace the duration with a predefined constant value.
    1. Under Duration Calculation, select **Time Calculation by Bundle Duration Field**.
    2. For Bundle Start Time Field Name, select the bundle service appointment field used for the bundle’s start time.
    3. For Bundle End Time Field Name, select the bundle service appointment field used for the bundle’s end time.
    4. For Constant Time Value, enter the bundle's total time as a constant value, in minutes.
9. Save your changes.

- The Allow Scheduling Dependencies in Bundle field isn’t supported.
- Deleting a bundle policy that’s in use isn’t recommended.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_field_service-264-0-0-production-enus/3f7dceb9-dd70-454a-b49e-bbb4526a158d/images/icon_note.png)

Note Don’t create triggers that update fields in any of the Appointment Bundling policies. If your configuration includes these triggers, you must delete them and apply a different configuration solution. For example, if you have a trigger that calculates duration, delete the trigger and create an aggregation duration downscale policy instead.

- **[Create an Appointment Bundle Sort Policy](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_sort_policy.htm&release=264.0.0&type=5)**  
    Use the default policy, or create multiple sort policies. For manual bundling, define a policy for sorting the bundle members within a bundle. The sorting is applied when bundling and unbundling service appointments. For automatic bundling, define a policy that determines the order that’s used to examine the bundling candidates.
- **[Create an Appointment Bundle Restriction Policy](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_restriction_policy.htm&release=264.0.0&type=5)**  
    Use an appointment bundle restriction policy to define restriction fields so that only service appointments with the same field values can be bundled together. Use the default policy, or create multiple restriction policies. For automatic bundling, you must have at least one restriction policy.
- **[Create an Appointment Bundle Propagation Policy](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_propagation_policy.htm&release=264.0.0&type=5)**  
    Create a policy to determine when and how the bundle service appointment updates the fields of the bundle member service appointments. And you can create multiple propagation policies for each bundle policy. Each propagation policy controls how one bundle member service appointment field is populated.
- **[Create an Appointment Bundle Aggregation Policy](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_aggregation_policy.htm&release=264.0.0&type=5)**  
    Use the default aggregation policies, or create policies to determine when and how bundle member service appointments update the bundle service appointment fields. And you can create multiple aggregation policies for each bundle policy. Each aggregation policy controls how one bundle service appointment field is populated.
- **[Create Appointment Bundle Aggregation Duration Downscales](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_aggregation_downscale_policy.htm&release=264.0.0&type=5)**  
    Account for one-time tasks that are part of a bundle by downscaling the duration of the bundle member service appointments. You can create multiple aggregation duration downscales.
- **[Create Appointment Bundle Policy Service Territories](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_st_policy.htm&release=264.0.0&type=5)**  
    Define one service territory for each bundle policy. Only service appointments in the defined service territory can be added to the bundle. For automatic bundling, you need at least one Appointment Bundle Policy Service Territory. For manual bundling, Appointment Bundle Policy Service Territories are optional.

#### See Also

- [Appointment Bundling Limitations](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_limitations.htm&release=264.0.0&type=5 "Review the limitations of Appointment Bundling.")
- [Default Appointment Bundle Policy](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_default_policies.htm&release=264.0.0&type=5 "If no policies exist, a default appointment bundle policy is created along with some of its related policies. Access Appointment Bundle Policy from the App Launcher. Access the remaining policies from the Related tab of the appointment bundle policy.")
- [Create Appointment Bundle Aggregation Duration Downscales](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_aggregation_downscale_policy.htm&release=264.0.0&type=5 "Account for one-time tasks that are part of a bundle by downscaling the duration of the bundle member service appointments. You can create multiple aggregation duration downscales.")