Feature - Agreements v3 - Push notifications

Requested Feature

Set both marketingEmail and marketingPush to true in the Updated Agreement Modal

Description

Change Updated Agreement / Marketing comms checkbox to also consider marketingPush. Currently, it checks only marketingEmail

Ensure Salesforce Push Notifications SDK is enabling customers permission and receiving notification.

Purpose

Capture more customer permissions for marketing push too (beside marketingEmail - agreement v2).

User problem

Customers need to go to comms preferences and enable push notifications. Long journey to enable push.

User value

Customers get push notifications easier.

Assumptions

For emails: CRM providers (Braze and Salesforce) are consuming the marketingEmail and email_subscribe flags from mParticle event.

For push: Existing EMEA CRM providers (not salesforce) consume marketingPush.

• In RBIberia, EMEA whitelabel(app) will need to call salesforce API to enable the customer opt-in and set marketingPush to true only for customers with native devices.

• Sign-up is not calling Salesforce API either. The same treatment needs to be applicable in the sign-up.

• RBIberia verified that there is no legal issues to handle both push and email in a single checkbox.

• Despite of the existing Integration of salesforce sdk, there is an issue when receiving notifications that requires a treatment to display them on the foreground for the user. Expected refactory to handle pushNotificationReceived.

Not doing

Trigger Email notifications to the customer. Responsible: CRM provider

Trigger Push notifications to the customer. Responsible: CRM provider

Acceptance criteria

• If customer sets the mkt comms checkbox, the following should be set :

  • User opted-in in salesforce → enablePush

  • marketingPush=true (dynamodb and mparticle)

  • marketingEmail=true(dynamodb and mparticle)

• For the flows:

  • Sign-up Flow

  • Updated Agreement

    • If the customer has at least one false flag (marketingEmail or marketingPush), modal should be displayed to try capturing both flags as true

  • Communications Preferences

Before enabling Push in salesforce, it’s necessary to check if the customer is using IOS/Android and if he/she is already enabled. isPushEnabled

No modal should disturb customer journey asking for him/her to allow push in the device OS.

Communications Preference:

The app should inform OS permision requirement message in Communication Preferences screen.

If the customer is using a device, but he/she already allowed to receive mkt comms when he/she was using web, then the app should be able to identify it and enable his/her current device in salesforce. This check can be done in Comms Preference screen, and another Info/Warning message can give a feedback about this to the customer.

• Once customer ticks mkt comms checkbox:

  • Both native (IOS and android) and web customers will get marketingPush (and existing marketingEmail) flag updated to true. A unique checkbox must be visible:

• Customer that has only one flag true ( either marketingEmail or marketingPush) will see the unique unticked checkbox. This scenario may not be common, but may happen due to migrated users

  •