In Salesforce Field Service, keeping users updated on Service Appointments is crucial for operational efficiency. This article explains how notifications are sent to users without explicitly enabling assignment notifications.
Upon assigning a Service Appointment, it appears that the assigned user is automatically set to follow the Service Appointment. This behavior suggests the presence of an Apex trigger or some customization that initiates the following action for assigned resources. Further investigation reveals the usage of a Flow designed to handle this process. This Flow ensures that when a Service Appointment is assigned, the respective user is automatically set to follow it. The user gets timely notifications and updates.
For a comprehensive understanding and configuration details regarding notifications, please refer to the Salesforce documentation on Field Service Push Notifications.
The automatic following mechanism for Service Appointments (SA) is facilitated by a Flow. This functionality is working without enabling the notification in Field Service Mobile Settings due to the custom Flow that follows the Service Appointment. Once the SA is followed, the Service Resource will get all the notifications on every event of SA.
When reviewing the logs (example below), you can see that the notifications in the Salesforce instance are originating from the FieldService Feed. Specifically, custom notifications are enabled within the org, which is confirmed by the log entry here:
FieldServiceFeedNotification.getMobileNativeMessageWithoutContextInternal:
<message: [$_SFDCGDPR_] updated Service Appointment #SA-Dummy on Work Order Line Item #WOLI-Dummy>
<Clump:<clump.type: feed_on_field_service>
<clump.userId: _SFDCGDPR_>
<size:9>
<payloads:<0:<Event: <FieldServiceEventType: FTC_INSERTED_FIELD_SERVICE(db=374)>
001930080

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.