Improved control over communication preferences

    We have improved how partners manage communication preferences to help reduce duplicate messages, unnecessary costs, and supporter frustration.

    Some partners have identified cases where supporters hold multiple customer records with the same phone number but different email addresses. When communications are sent, this can result in the same person receiving duplicate SMS or emails. 

    What has changed

    We have introduced a new Bulk Importer file type called Communication Preferences Update.

    This new file type allows admin operators to bulk update communication preferences for existing customers by supplying only the fields that need to be changed. It is designed specifically to help partners quickly manage and correct communication settings without re importing full customer records.

    To provide clearer distinction between use cases, the existing Bulk Importer file type Communication Preferences has been renamed to Communication Preferences Migration. This file type should now be used only when importing communication preferences from external customer data platforms.

    Why this matters

    These improvements have enabled partners to:

    • Reduce duplicate SMS and email sends
    • Lower communication costs
    • Improve supporter experience by avoiding repeated messages
    • More easily manage communication preferences at scale
       

    Communication preferences fields

    The Communication Preferences Update file supports lottery based communication subscriptions across the following channels:

    • Email
    • Phone
    • SMS
    • Push notifications
    • Mail
    • Web push

    Each record is matched using the existing customer identifiers already stored in the Jumbo platform, ensuring updates are applied accurately and safely.

    What partners need to do

    Partners experiencing duplicate communications can now use the Communication Preferences Update bulk importer to adjust supporter preferences without impacting other customer data.

    If you need support preparing your file or understanding which importer to use, please reach out to your Jumbo support contact.

    Example CSV file fields

    Field

    Description         

    Type            

    Required           

    customer_encoded_idUnique encoded ID of the customer on the Jumbo platformtexttrue
    lottery_idThe lottery ID to update the communication preferences for (set to 0 if the platform does not have COMM_PREFERENCES_BRAND_ENABLE set to true)integertrue
    emailbooleantrue
    phonebooleantrue
    sms
     
     booleantrue
    pushbooleantrue
    mailbooleantrue
    web_pushbooleantrue
    Was this article helpful?
    0 out of 0 found this helpful