Loading
Agentforce Field Service and Operations
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Group Nearby Appointments Service Objective

            You are here:

            1. Salesforce Help
            2. Docs
            3. Agentforce Field Service and Operations

            Group Nearby Appointments Service Objective

            Use the Field Service Group Nearby Appointments service objective to reduce the number of mobile workers assigned to the same area on a given day. This objective ensures mobile workers maximize their presence in high-volume areas by completing all appointments within a specific area before moving to the next. It’s ideal for organizations with a large number of appointments per mobile worker, where multiple workers typically start from the same home base and cover the same geographical areas.

            Required Editions

            Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
            The Agentforce Field Service and Operations core features, managed package, and mobile app are available in Enterprise, Unlimited, and Developer Editions.

            Package icon This is a Field Service managed package feature.

            Note
            Note

            This objective is supported only when you’re using Enhanced Scheduling and Optimization. Relevance groups isn’t supported for this objective.

            By prioritizing this objective, the scheduling engine identifies geographical clusters so that a single worker manages the entire workload for a cluster, reducing inefficient "ad-hoc" stops in favor of dedicated area coverage. This clustering eliminates path overlap and maximizes productivity by ensuring one mobile worker "owns" the area for the day.

            When You’re Using Enhanced Scheduling and Optimization

            The enhanced engine dynamically groups nearby appointments into geographic clusters based on location and proximity. The Group Nearby Appointments service objective applies a penalty equivalent to 120 minutes of travel for every service appointment (or resource absence) that falls outside a cluster. To use the Group Nearby Appointments objective effectively, you need to balance it with Minimize Travel, because these two goals can compete with each other.

            The Minimize Travel objective operates on a standard scale of 120 minutes where every minute of travel is assigned a penalty based on the weight you provide. For example, if you assign Minimize Travel an objective weight of 1,000, the engine divides that weight by the 120-minute scale, resulting in a penalty of 8.33 points for every minute of driving.

            To control how much extra driving you're willing to tolerate before the engine schedules an appointment outside a cluster, you must adjust the weight of the Group Nearby Appointments objective relative to the per-minute travel penalty. For example, if you’re willing to accept up to 10 extra minutes of driving to keep a worker in the same area, you calculate the weight by multiplying the per-minute travel penalty by your desired time threshold. Using the previous example, where the per-minute penalty is 8.33, set the Group Nearby Appointments weight to 83.3 (8.33 points × 10 minutes). By setting the weight to 83.3, or rounding up to 85 to create a slightly stronger preference, the engine prioritizes keeping a worker in the same area unless the travel savings from breaking the cluster exceeds 10 minutes.

            At this setting, the engine keeps the worker in the same geographic area unless assigning the appointment outside the cluster reduces travel time by more than about 10 minutes.

            When You’re Not Using Enhanced Scheduling and Optimization

            This service objective isn’t supported.

            See Also

             
            Loading
            Salesforce Help | Article