What is preventing the drip feed from triggering?

Northern Trail Outfitters is implementing drip feed dispatching. When testing the new functionality, the drip does not dispatch appointments as expected. A consultant is engaged to troubleshoot the issue.

What is preventing the drip feed from triggering?

A. The appointment status is going from Scheduled to Completed.

B. The status on completed appointments can only be Canceled, Completed, or Cannot Complete.

C. The default drip feed setting is overriding the drip feed rate on a service territory.

D. Other scheduled jobs are dispatching appointments and exceeding the drip feed value.

View Answer

Answer: C

Explanation:

Drip feed dispatching in Salesforce Field Service is about releasing work orders to technicians in a steady stream rather than all at once. It allows dispatchers to have better control over workloads and scheduling.

From the options given:

C. The default drip feed setting is overriding the drip feed rate on a service territory.

This is the most likely reason. If there’s a default setting in place, it could override the specific settings applied to a service territory. When configuring drip feed for specific service territories, it’s important to ensure that the default settings don’t conflict with the custom configurations.

Here’s a brief overview of the other options:

A. The appointment status is going from Scheduled to Completed.

Drip feed dispatching is about controlling when appointments are released or dispatched to technicians, not about the status transition of the appointment itself.

B. The status on completed appointments can only be Canceled, Completed, or Cannot Complete.

While these are standard statuses for completed appointments, they are not directly related to the mechanism of drip feed dispatching.

D. Other scheduled jobs are dispatching appointments and exceeding the drip feed value.

While it’s possible that other scheduled jobs could interfere with the drip feed, this scenario is less likely than a configuration issue, like having the default setting overriding the service territory-specific setting.

Thus, the correct answer is C. The default drip feed setting could be overriding the custom configuration for a particular service territory, preventing the drip feed from working as expected.