Understanding the Problem

The issue arises when MobileConnect prevents duplicate sends to a mobile number associated with multiple contacts. For example, if three contacts have the same mobile number, MobileConnect delivers only one message to the device.

This poses a challenge when trying to send personalized messages, such as a price increase notification, to each contact. The message needs to be tailored to each dealership the contact is associated with.

Example Use Case

Consider the following example:

• Dealer 1: $150 price increase, Contact 1, 1234567890, Subscriber Key 003AA1234
• Dealer 2: $200 price increase, Contact 1, 1234567890, Subscriber Key 003AA1235
• Dealer 3: $110 price increase, Contact 1, 1234567890, Subscriber Key 003AA1236

In this scenario, the contact should receive three separate messages, each with the price increase information for the respective dealership.

Root Cause of the Issue

The root cause of the issue is MobileConnect’s default behavior of preventing duplicate sends to the same mobile number. This is designed to prevent spamming and ensure a good user experience.

Possible Solutions

One possible solution is to use a prioritization method to send messages based on value. For example, if a contact has multiple associations, the message with the highest value could be sent first.

Another solution is to create multiple segments until all contacts are exhausted. This would involve creating separate segments for each contact and sending the message to each segment individually.

example.apxt

/* Example code to create multiple segments */
var contacts = [/* list of contacts */];
var segments = [];
for (var i = 0; i  < contacts.length; i++) {
  var segment = {
    /* segment definition */
  };
  segments.push(segment);
}

Managing Subscriptions

Managing subscriptions is also crucial in this scenario. Contacts should be able to opt-out of receiving messages for specific dealerships or altogether.

This can be achieved by using a preference center where contacts can manage their subscriptions and preferences.

Heads up: make sure to comply with applicable laws and regulations, such as GDPR and TCPA, when sending messages and managing subscriptions.

Checklist for Implementation

• Identify contacts with multiple associations
• Use a prioritization method to send messages based on value
• Create multiple segments until all contacts are exhausted
• Implement a preference center for managing subscriptions
• Comply with applicable laws and regulations
• Test and optimize the implementation

Frequently Asked Questions

What is the maximum number of associations a contact can have?

There is no maximum number of associations a contact can have, but it's recommended to keep it manageable for performance and user experience reasons.

Can I use a single segment for all contacts?

No, using a single segment for all contacts would not allow for personalized messages to be sent to each contact.

How do I handle opt-outs and subscriptions?

Use a preference center to allow contacts to manage their subscriptions and preferences.

What laws and regulations do I need to comply with?

Comply with applicable laws and regulations, such as GDPR and TCPA, when sending messages and managing subscriptions.