Loading
Feature Disruption - Service Cloud VoiceRead More
Feature degradation | Gmail Email delivery failureRead More

How to Set Salesforce Field Service Mobile Notifications without Enabling Notification for Assignment

Publish Date: May 15, 2026
Description

In Salesforce Field Service, users can receive notifications for Service Appointments without explicitly enabling the Notification for Assignment setting in Field Service Mobile Settings.

This behavior is triggered by a custom Flow that automatically sets the assigned service resource to follow the Service Appointment record upon assignment. Once a user follows a Service Appointment, Salesforce's standard Chatter feed notification mechanism delivers updates for all subsequent events on that record — including status changes, updates, and comments.

The notifications originate from the FieldService Feed (feed_on_field_service), which is part of Salesforce's custom notification framework for Field Service. This means the service resource receives timely updates on every event of the Service Appointment, even without the dedicated assignment notification setting being enabled in Field Service Mobile Settings.

For reference documentation on push notifications in Salesforce Field Service, see Field Service Push Notifications.

 
 
Resolution
This article explains how Service Appointment notifications are delivered in Salesforce Field Service without the Notification for Assignment setting being enabled, and how to verify the custom Flow configuration responsible for this behavior.

How the Automatic Follow Mechanism Works

When a Service Appointment is assigned in Salesforce Field Service, a custom Flow runs and automatically adds the assigned user as a follower of the Service Appointment record using Salesforce's standard Follow functionality.

As a result of being set as a follower, the service resource receives notifications through the FieldService Feed (feed_on_field_service) for all subsequent events on that Service Appointment — including updates, status changes, and comments — without requiring the Notification for Assignment setting to be explicitly enabled in Field Service Mobile Settings.

The notifications are delivered as custom mobile push notifications, confirmed by the log entry type FieldServiceFeedNotification.getMobileNativeMessageWithoutContextInternal, which indicates that the notification originates from the FieldService Feed clump type (feed_on_field_service) and is triggered by a Field Service event (FTC_INSERTED_FIELD_SERVICE).

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)>


Verifying the Flow Configuration

To identify and verify the Flow responsible for the automatic follow behavior, follow these steps:

  1. Navigate to Setup in your Salesforce org.
  2. In the Quick Find box, search for Flows and open the Flow list.
  3. Look for a Record-Triggered Flow on the Service Appointment object that runs when a Service Appointment is assigned (for example, when the AssignedResource field is populated or when the status changes to Scheduled/Assigned).
  4. Open the Flow and confirm it contains an action that sets the assigned user as a Follower of the Service Appointment record.
  5. If this Flow is present and active, it is the mechanism responsible for the automatic follow and subsequent notifications.


Note: This behavior is triggered by a custom Flow — it is not a standard out-of-the-box Field Service feature. If the Flow is deactivated or deleted, automatic following and the associated notifications will stop.
Knowledge Article Number

001930080

 
Loading
Salesforce Help | Article