Universal Containers has created a new Loyalty Member Portal for a second Loyalty Program that they have recently launched. A member of the first program has enrolled in the second program and has decided to use the same login for both Loyalty Member Portals. The user cannot access the new Loyalty Member Portal.
How can the Loyalty Administrator verify why the user cannot access the second Loyalty Member Portal?
A company has an existing Loyalty Program, and the marketing team wants to start awarding 10% discounts and 100 points to new members upon sign-up.
What does the Program Administrator need to do for a new member to earn this promotion?
To award new members with a 10% discount and 100 points upon sign-up, the Program Administrator should:
B: Create a record-triggered flow using Journal Type, Journal SubType, Transaction Journal, Credit Points action, and Issue Voucher action. This flow will automate the process of crediting points and issuing discount vouchers to new members as part of the promotion.
Universal Containers (UC) plans to implement Salesforce Loyalty Management for a new Loyalty program; however, its operations team remains skeptical about the Loyalty solutions, such as rules, processes, and benefit types.
Which option should UC consider when planning its implementation to ensure staff is helping to boost adoption and engagement?
To ensure staff buy-in and boost adoption and engagement with the new Loyalty Program, Universal Containers should:
D: Define a company-wide initiative that includes the operations team. Engaging all relevant departments from the outset ensures a holistic approach to the implementation and addresses concerns and skepticism by involving those who will be directly impacted by the new Loyalty solutions.
Ursa Major Solar has recently rolled out its Loyalty Program. The customer support agents need access to Loyalty Program Member's information. The System Administrator at Ursa Major Solar has placed the Loyalty Members Profile Cards on the Lightning Record Page, and all access is granted; however, it is still not visible on the page.
What setting is missing and preventing the visibility of the pages?
In Salesforce Loyalty Management, visibility issues of components such as the Loyalty Members Profile Cards on the Lightning Record Page can often be traced back to configuration settings related to the Loyalty Program itself. While options A, B, and D mention various dashboards (Member Summary, Member Preferences, and Member NPS), these are not directly related to the visibility of profile cards on the Lightning Record Page.
The correct setting that is likely missing and preventing the visibility of the Loyalty Members Profile Cards is the configuration of the Loyalty Program as Primary. This setting is crucial because it defines which Loyalty Program is considered the main one for the organization. Without setting a Loyalty Program as Primary, Salesforce might not properly display related components, such as the Loyalty Members Profile Cards, due to a lack of context about which program's information should be displayed.
In Salesforce, the concept of a 'Primary' program is used in various contexts to denote the main or default record among multiple. Similarly, in the context of Loyalty Management, setting a Loyalty Program as Primary ensures that its related data and components are given precedence and are properly displayed in the user interface, including on Lightning Record Pages.
For reference, Salesforce documentation on Loyalty Management typically covers the setup and configuration of Loyalty Programs, including how to designate a program as Primary. Although the exact steps can vary based on the Salesforce release and customizations, administrators typically need to navigate to the Loyalty Management settings or related setup area, find the specific Loyalty Program configuration section, and select an option or checkbox to designate a program as the Primary Loyalty Program for the organization.
The existing Loyalty Program would need to have its "members-record" transferred from an SQL database into a new Salesforce Loyalty Management org, where its members' records are kept within a data table named "tbl_Member" with the following data contents:
* the program member's personal particular and contact information
* member's current-tier value
* member's tier-points
Which object combinations should be used for data migration of the source's member records into the Loyalty Member org?
For migrating 'members-record' from an SQL database into Salesforce Loyalty Management, the correct combination of objects to use is:
D: 'LoyaltyProgramMember,' 'LoyaltyMemberTier,' 'LoyaltyMemberCurrency,' 'Contact,' and 'Account' Object. This combination covers all necessary aspects of Loyalty Program members' records, including personal information, tier status, and point balances.
