Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Context (already Implemented ticket) → Existing New Market Setup Requirement: NMS-370 → Communication Preferences; merge push and email

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 checkbox, MarketingPush flag should be set as true for the flows:

    • Communications Preferences

    • Sign-up Flow

    • Updated Agreement

  • Once customer ticks mkt comms checkbox:

    • 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

Under Review with Paula Winter (Unlicensed) :

  • The customer will still see the unique unticked checkbox

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

    • 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:

High Level Estimation

0,5 sprint for Design and Tech Refinement
1 sprint for Development and Testing

Total: 1,5 sprint

Acceptance Criteria:

If the user checks the option “receive marketing notifications” on Sign up, on update agreements modal or on user prefereces, the attributes must be updated on Dynamo:

  • push_subscribe: subscribed

  • marketingPush: true

  • rewardsPush: true

If the user does not check on Sign up or on update agreements modal and uncheck on user preferences, the attributs must br updated on Dynamo

  • push_subscribe: unsubscribed

  • marketingPush: false

  • rewardsPush: false

  • No labels