Feature - Agreements v3 - Inclusion of Push in the Upd. Agr.

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

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.

Not doing

Trigger Email notifications to the customer. Responsible: CRM provider

Trigger Push notifications to the customer. Responsible: CRM provider

Acceptance criteria

• Once customer ticks mkt comms checkbox and clicks on Continue:

  • Only native (IOS and android) customers will get marketingPush flag updated to true.

  • Both native and web customer will continue getting marketingEmail flag updated to true

• If customer accept this checkbox via web and then go to comms preferences.

  • The customer will still see the unique unticked checkbox

  • A warning message can inform the customer that he/she needs a mobile phone to get Push notifications

  • 

• If customer accept this checkbox via native and then go to comms preferences.

  • The customer will then see the unique ticked checkbox:

  •