Full Access Salesforce Salesforce-Loyalty-Management Tutorials

When a tier is changed manually in Salesforce Loyalty Management, an Administrator should execute the following two actions:

Process Member Benefit Action (A): This action ensures that any benefits associated with the new tier are correctly processed and applied to the member. It's essential for maintaining the integrity of the loyalty program and ensuring members receive the appropriate benefits for their new tier.

Assign Member Tier Benefits Action (C): This action assigns the benefits specific to the newly assigned tier to the member. It's crucial for updating the member's benefits to align with their new tier status, ensuring they receive all entitlements associated with their new level.

Creating a scheduled job to perform the tier change (option B) and processing Transaction Journals batch job (option D) are not directly related to the manual tier change process. The focus should be on ensuring that member benefits are correctly assigned and processed in response to the tier change.

Salesforce documentation on Loyalty Management would provide detailed guidelines on managing tier changes, including the actions required to ensure member benefits are correctly updated.

For Northern Trail Outfitters' Loyalty Program offering, the Administrator should configure:

B: One qualifying currency to track points that can be redeemed for products.

C: A tier system based on cumulative spending to gamify and reward top spenders with exclusive benefits.

E: Promotions to create special offers or rewards that can enhance the Loyalty Program's appeal and engagement.

To provide Cloud Kicks' customer base, who are heavy mobile users, with access to member program information, the consultant should Enable Experience Cloud and customize the Loyalty Member Portal (A). Experience Cloud (formerly known as Community Cloud) allows for the creation of branded, mobile-responsive portals that can be customized to meet specific business needs, including providing loyalty program members with access to their program information, account status, rewards, and more. This approach leverages existing Salesforce capabilities and does not require the development of a new mobile app, making it a cost-effective and efficient solution.

For the scenario described, where a loyalty program wants to send an immediate notification after a voucher is added to a member's account, the entry event in Salesforce Marketing Cloud needs to trigger off of the creation of a record in Salesforce that contains the necessary data attributes for personalization.

Option C is the most suitable choice because it specifies an entry event based on the "Voucher," "Contact," and "LoyaltyProgramMember" objects. This approach aligns with the requirements because it directly utilizes the "first name" from the Contact object and the "membership number" from the LoyaltyProgramMember object, which are necessary for personalizing the notification message.

Moreover, Option C would likely require the least amount of development effort because it leverages existing Salesforce data and related objects without the need for additional configuration or data extensions. In contrast, other options would require the setup of a data extension or custom objects that may not be directly tied to the triggering event, thereby increasing the complexity and development effort.

In Salesforce Marketing Cloud, Journey Builder is the tool that would be used to create this customer journey. It allows for the configuration of entry events based on data changes in Salesforce, such as the addition of a voucher to a member's account. The real-time nature of this trigger is essential for the immediate notification requirement.

According to Salesforce's official documentation, using Salesforce data as the entry source for a journey allows for real-time messaging based on record creation or updates. This means that as soon as a voucher record is created or updated in Salesforce, the entry event can trigger and begin the journey, which will send the personalized notification to the member.

In practice, setting up this entry event in Journey Builder would involve specifying the criteria for the trigger (in this case, the creation of a voucher) and mapping the necessary data fields for personalization. This is consistent with Salesforce's best practices for creating personalized, real-time customer engagements through Journey Builder.

Salesforce's documentation on Journey Builder and real-time event triggers provides further details on how to configure these types of journeys and can be referred to for step-by-step guidance and the latest feature updates.