Add emails to a classic program

You can add emails to step resources after your program is created in classic programs.

• The emails must be in a shared folder.
• Emails are added for program steps where subject lines, from and reply to address and scheduling options are set as part of the step configuration process.
• Emails can be associated to multiple steps.

1. Choose a template from the gallery to create a program.
2. Click Add in the Step resources panel to associate emails to your program.
3. Drag the email into the desired track and click Configure on the step.

To change an email for a step, click the Add templates link on the step configuration page.

Delete an email by clicking the X beside the email name in step resources.

The fields then become enabled, and you can change the Send Email Details as necessary.

Reconfigure or change resource when fields are not available

If you want to reconfigure or change the resource, and the fields are not available, access the Email message template resource menu and select the template again from the New email from template resource section.

Add SMS to a classic program

You can select a published SMS message that is associated with one or more SMS text to join programs and use it to configure a program step. This allows SMS clients to automate their SMS message sends. Only one SMS message can be associated to each step, but that message can be associated with multiple SMS text to join programs. Acoustic Campaign is integrated with SMS Campaign Manager (mGage) to facilitate the sending of SMS messages.

Before you begin

Before you can associate SMS content to a step in your program, make sure that the following perquisites are complete:

• SMS is enabled for your organization and database including SMS UB events.
• SMS text to join program is set up in mGage.
• SMS content is prepared and published in the mobile send experience.
• The mobile SMS admin configures the SMS campaigns and program types in mGage.
• The SMS content creator builds the SMS message draft, including tags, and selects Publish, making the SMS message available for use in programs or API.

Note: The SMS step only displays if the attached database or query is enabled for SMS.

Procedure

1. Open a program.
2. Click Edit program settings.
3. Choose a contact source by selecting a mobile-enabled database or query of that database.
4. Select Add contacts when the following events occur: and choose a behavior.

   Note: You can select any query containing profile, channel, behavioral, or relational table criteria. Universal behaviors (UB) or in-queries are not supported as a program entrance query. You can also add event-based triggers based on universal behaviors for program entry.

5. Click Add behavior and choose the behavior type you want to add. Universal behaviors must be configured.

   Note: In order to choose a specific app within the app group for Universal Behavior attributes, you need to retrieve the app key from your mobile app developer.

6. Click Save and edit flow to return to the program flow.
7. Add the SMS message step to the program flow.
   • Actions can be placed on the step and decisions can be placed before or after the step.
   • Step checks SMS consent record. If consent has been lost for the SMS text to join program, the contact is exited from the program.
8. Hover over the step and click Configure.
9. Select a text to join program name from the menu.
10. Review the content of the SMS message.
11. Click Edit if you want to use the advanced setting option. You can set the specific time of day you want the SMS message to send.
12. Click Apply to save and complete the step configuration.
13. Activate the program.

When the SMS message is sent, any tags included during the SMS message creation process are added to any Program level tags.

Note: Contacts must be opted-in to SMS to receive SMS messages. If a contact has entered a program but has opted out of SMS by the time they arrive at the step, they are immediately exited from the program. This applies to email and mobile app message steps.

If you want to change the message associated to the step, open the Configure SMS screen and click Change.

Add mobile app messages to a classic program

Mobile app messages published in the mobile send experience can be used in both programs canvas and classic programs. The following mobile app message types are supported in programs:

• Simple
• Simple + Inbox
• Simple + Data Extensions
• Simple + Inbox + Data Extensions
• In-App
• Inbox-Only
• Data

Before you begin

Before you can associate mobile content to a step in your program, make sure the following perquisites are complete:

• Your org is enabled for mobile.
• Mobile app message content is prepared and published in the mobile send experience.
• Mobile universal behavior events are included in the mobile app message enablement process.
• Your database is enabled for mobile by your org admin.

  Note: Only one mobile database is allowed per organization.

• Users are enabled by the org admin.
• Apps and app groups are created.
• A mobile app message-enabled user creates the message draft, including any tags, and saves the draft so it can be added to a program in the mobile app.

Procedure

Note: Steps 1-6 are exactly the same as for adding SMS to a classic program.

1. Open a program.
2. Click Settings.
3. Choose a contact source by selecting a mobile-enabled database or query of that database.
4. Select Add contacts when the following events occur: and choose a behavior.

   Note: You can select any query containing profile, channel, behavioral, or relational table criteria. Universal Behaviors (UB) or in-queries are not supported as a program entrance query. You can also add event-based triggers based on Universal Behaviors for program entry.

5. Click Add behavior and choose the behavior type you want to add. Universal Behaviors must be configured.

   Note: In order to specify a specific app within the app group for UB attributes, you need to retrieve the App Key from your mobile app developer.

6. Click Save and edit flow to return to the program flow.
7. Drag the mobile app message step resource to the programs canvas or onto the start track in classic programs.
8. Select Click to configure to add the step details. If you are using a placeholder step, select the Actions pull-down to choose Send mobile app message.
9. Click Configure.
10. Select the app group that your published message is associated with, choose your mobile app message from the list, and click Select.
11. The Configure Mobile App Message window opens with the details associated with the selected mobile app message draft. The content details configured in the mobile app message draft for the selected mobile app message are not editable, except for the Delivery Name.

    Note: Included tags do not display on the Configure Mobile App Message page or in the Insight panel.

12. Click Apply to finalize the configuration and save. After the Step is configured, the delivery name and settings are locked and cannot be changed without creating a new step and selecting a mobile app message.
13. After activation, you can change to another message by deactivating the program, launching step configuration, and clicking the mobile app message Change link to select a new message.

When the mobile app message is sent, tags included during the message creation process are added to any Program level tags.