Stephani Nicole Project Manager & Dynamics 365 Enthusiast

Outbound Marketing journeys allowed us to create a task, appointment, or call in D365 and assign it to someone in D365.

We would like to see this feature in Real Time Marketing Journeys. The release of 2-way SMS has made this even more desirable. We do need to take it one step further for Real Time though - we need the ability to assign the task, appointment, or call to more than the Journey Owner, Contact Owner, or Contact. We would like to be able to assign the task to 1) a specific Contact that we select, 2) or a related Contact to the Contact and not just Owner, or 3) a Contact based on a condition (i.e. if the inbound message contains 'donation' then assign to Contact X who manages donations, otherwise assign to Contact Y who manages customer service)

For example, when a keyword response is received - create a Task in D365 and assign it to the Relationship Manager for that Contact.

The new keyword feature is amazing! But it only allows a contact to respond to a keyword if directly from the sent message.

We would like a standard trigger that listens for any inbound SMS. Then rather than only being able to respond to a specific message one time, a contact can text anytime and we can setup keywords in one journey rather than multiple times.

We have many use cases where we want to accept payments or donations via SMS.

Can you allow integration between a payment gateway and SMS in D365 Marketing? Ideally, this integration would be easy to configure, like SMS is for real time marketing today.

For example - in Settings there would be a Payment Gateway page. You click NEW to add a payment gateway - add the API secret / code / details - and then check each area of Marketing you want to integrate with (i.e. Events, SMS, Forms, Surveys, etc.)

Then, we could setup a keyword that triggers the payment gateway. For example, Contact could text 'DONATE' to a short code/phone number. That would trigger an automated response to enter payment information/details.

When using a Real Time Journey with a Standard Trigger, we would like to be able to reference an attribute of a related entity for that trigger.

For example, real use case:

We have a real time Journey that uses the standard Event Registration Created trigger. Within an email, we can access a lot of data on this trigger - like the related Event record. We want to create a branch that looks at a data point on that related Event record for the registration.

If Event Type, on the Event record, for that registration is XYZ, then follow Branch 1.

Right now, we only have access to the Registration data points from within a Journey/Branch. We do not have access to data points on the related records which are attributes we can see from within an email.

We can currently create a branch in a real time journey that looks at data on the Contact record. We would like to also access/reference data on related records to the Contact.

For example (real use case):

If the most recent Enrollment record for the Contact is for Department A, then follow Branch 1.

OR

If the owning user's region for the Contact is Southwest, then follow Branch 2.

The addition of Brand Profiles is a GREAT step in the right direction! We would love to see this feature expand to include:

1. Conditional Content - would be nice to create "common" conditions that can be easily used across multiple emails (and other assets), at a brand level like what you did with common personalization tokens where we do not have to define/create form scratch each time.
2. Dynamic Lists - would be nice to create "common" dynamic lists that be easily used across multiple emails at a brand level, like what you did with common personalization tokens where we do not have to define/create form scratch each time.
3. Templates - would be nice to designate various email templates, and other templates, as brand specific. Many teams within an organization create views to see only emails or templates for their brand.
4. Company Address - Emails require an address, that can change based on brand
5. Subscription Center - Each brand may have their own subscription center
6. Colors - This has been a major pain point of the editors - we have to repeatedly add our custom colors - especially painful in the text fields. Other settings now save recently used colors - text does not and when you highlight text, it doesn't show you what color was selected for it.
7. Themes - How amazing would it be if we could select a brand's theme to apply to an email, form, page, etc. Like a template - but at a higher level and for brands.
8. Styles - right now we have to customize the app to add new fields if we want our own unique styles for even standard items like an H1, H2, Paragraph, List etc. Allow us to set these styles at the brand level once and one.
9. Duplicate/Copy - would be nice to select a brand profile, click copy, and save as a new version - would not require re-doing everything from the start.
10. Personalization Tokens - common tokens set at brand level

In real time marketing, if you navigate to a channel tile like Email or SMS in a Journey that has been published, you will see a link to delivery and interaction details. This report/dashboard has the Contact/Lead ID for the interaction or delivery detail. Please make the Contact/Lead a link that quickly takes us to the record vs. making us open a new tab and manually manipulate the URL to access it.

In Real Time Marketing, we are able to upload images. Upon uploading, we can enter information like ALT text, description, etc. I'm not sure why our emails do not pre-populate or default image alt text to use this information? This would be very helfpul.

Example/Use Case:

1. Upload image into Library - enter information like Alt Text
2. Select Image, from Library, in Email
3. Default or prefill the alt text for that image in that email using the alt text entered during upload

Given the great advancements of Real Time Journeys - I question whether we want or need segments and subscription lists like they exist today in D365 Marketing. With a few minor tweaks to Journey tiles, we could avoid a lot of work in terms of training, creation, and maintenance.

Here is a suggestion for a new experience.

Eliminate segments & use Branching:

1. Navigate to D365 Marketing > Real time marketing > Journeys
2. Click New
3. Choose 'Segment' based (but do not require a Segment selection)
4. Populate the rest & click Create
5. Use the Branch tile as the first step in these new 'Segment' based Journeys
6. The branching details will identify the contacts or leads to be communicated to

Eliminate Subscription Lists & use option set:

6. On the tile where the e-mail is selected, add a new yes/no field that allows us to specify if our audience is allowed to subscribe or unsubscribe from this 'Topic'

a. If yes, we can select or create a 'Topic' for our audience to subscribe or unsubscribe to

b. The 'Topic' record can have additional fields like what audiences to show it to on the subscription page

When we use the standard Microsoft event trigger for Marketing Event Registration Canceled - it triggers when a registration record is deleted, not just when the isCancelled flag is marked yes. We only want this trigger to activate when a registration record is truly 'Cancelled'. Deleting a record should not activate this trigger.