web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / What's the reason for ...
Customer experience | Sales, Customer Insights,...
Suggested Answer

What's the reason for not allowing multiple email addresses for contact in RTM journey

(1) ShareShare
ReportReport
Posted on by Tommi Oksanen 28
Hi all,
 
I came across this limitation in RTM journeys vs. audience configuration (emphasis added):
For contacts, only one recipient email address can be used. This is done to remove consent ambiguity. In outbound marketing, a contact record may store several email addresses with one consent for the entire contact. But in Customer Insights - Journeys, consent is given per each email address.
 
Can anyone explain the logic behind this? I'm not buying the /consent ambiguity/ thing mentioned, as we easily(ish) could create a contact point consent for each of the email addresses stored on the contact record.
 
I have multiple customers who each use different email address fields for different needs (address types, business functions and so on). I do not see any way for them to consolidate all email addresses to a single field for all marketing activities.
 
Also, are there any plans to change this feature to support multiple email addresses?
 
Thanks,
Tommi
I have the same question (0)
  • Suggested answer
    Haig Liu Profile Picture
    Haig Liu Microsoft Employee on at
    Hi Partner,
     
    1.RTM journeys are based on contact points, which means that consent is stored per destination and per channel, e.g. for email channels, only one email address will be included.
    2.Why /consent ambiguity/?
    Because Customer Insights - Journeys needs to differentiate between RTM and outbound marketing.
     
    3.Will subsequent updates allow multiple email addresses?
    There is currently no word on this, but DoNotEmail and DoNotBulkEmail were recently updated and it's not certain if this will change.
  • Tommi Oksanen Profile Picture
    Tommi Oksanen 28 on at
    Thanks for your reply.
     
    I still disagree with the consent ambiguity thing. Take the following scenario.
    There is abolutely no ambiguity in what the contact has opted in for. The customer should be able to use the 2nd address just as they have been using in the outbount side.
     
    To me the current sitation feels like the product team made a huge reorganization on the email address consent management & email/journey settings, and decided to proceed with the easiest option, i.e. support for just one email address.
     
    I really do not see what kind of believeable arguments I could make to my customers to scrap all their other email addresses and consolidate all the communications to that one emailaddress1 – no matter what the their customers' preferences or business reasons have been. If any fellow architects have any good arguments, I'll gladly take them.
     
    If anyone from the Marketing product team is reading this, I'd really be interested in hearing your take.
     
    BR,
    Tommi

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 213 Super User 2026 Season 1

#2
CU11031447-0 Profile Picture

CU11031447-0 100

#3
NeerajPawar Profile Picture

NeerajPawar 71

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans