---
schema_version: "1"
id: a9e1c577b983ca827a555bc98776e45b9d4e0e99cd99c8b448e61f6e2abb8453
title: Journeys for Quick Send Messages
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_dm_journeys_for_qs.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_dm_journeys_for_qs.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2270beedf2dd38d05a3544e04ff872ad3d46a4cadde6e4542bb9e67e9a6886ee
description: To create a unique journey for marketing activities when using the Distributed Marketing Quick Send workflow in Marketing Cloud Engagement, follow these steps
products:
  - Marketing
  - Cross Cloud
release: "264"
---
# Journeys for Quick Send Messages

To create a unique journey for marketing activities when using the Distributed Marketing Quick Send workflow in Marketing Cloud Engagement, follow these steps

When you create journeys for Quick Sends, consider the following.

- Journeys created for quick sends can include any number of standard or custom Flow Control, Customer Updates, Sales & Service Cloud, or Custom activities. However, each journey for quick sends can include at most one email or SMS activity only.
- To avoid adding individuals to multiple journeys at the same time, use a unique entry source per journey.
- A contact filter isn’t required for Distributed Marketing, but can be used as needed.
- The contact entry setting must allow for Re-entry always or Re-entry after exiting. No re-entry isn’t supported for quick send messages.
- Journeys enabled as quick send messages are available in all quick send messages that business users can access.

1. In Marketing Cloud Engagement, navigate to **Journey Builder**.
2. Create a Multi-Step Journey.
3. Drag an **API Event** entry source onto the journey canvas.
4. Configure the entry source with the unique event data extension you created for this journey.
5. Drag journey activities onto the canvas.
    
    ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_cross-cloud_products-264-0-0-production-enus/bd617332-480f-48e8-b283-3477883c1320/images/icon_tip.png)
    
    Tip A single **Email** or **SMS** activity is required. Use non-message activities to make quick send messages more powerful for recipients, senders, and the business. For example, add an Engagement Split activity to a quick send journey. If a contact doesn’t open the email, use the Task activity to suggest business users follow up with a phone call. Or they can resend the email.
6. Define the contact entry mode.
    
    ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_cross-cloud_products-264-0-0-production-enus/bd617332-480f-48e8-b283-3477883c1320/images/icon_tip.png)
    
    Tip **Re-entry anytime** or **Re-entry only after existing** is required.
7. Name the journey and add a description.
    
    ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_cross-cloud_products-264-0-0-production-enus/bd617332-480f-48e8-b283-3477883c1320/images/icon_tip.png)
    
    Tip The journey name appears to business users when searching for a message to send. Put uniquely identifiable information for each message in the first 30 characters. For example, use Birthday Template - Summer 2020 instead of Summer 2020 Birthday Template.
8. Activate the journey. The journey can now be enabled as a Quick Send message.