This job sends a prepared message to a single contact, for example when he subscribes to a group or replies to a message.

This job sends single messages. All of the single messages share the same message ID. This means that only one sendout appears in the outbox. Single messages are evaluated collectively in the single message statistics. The message must be saved as a prepared message. After sendout, a prepared message remains saved in the system.

Hint:

The designation (C) means contact-related. In general, you only combine contact (C) events with contact (C) jobs. For more information, see Contact (C) vs. System (S) Automations​

Recommended Automations​

An automation is a combination of an event plus a resulting job. The following combinations are recommended. It is possible to create other combinations, as well, but not all combinations of events and jobs result in meaningful system behavior.

  • Subscribed to Group (C) + Send Prepared Message to Contact (C): This automation sends a prepared message to each new subscriber. The prepared message is sent after the opt-in process is complete. The prepared message does not replace the opt-in messages.
    For this combination, check ​Use Event Parameter​ for the following fields: ​Group Name​ and ​Contact​.

  • Member Added to Group (C) + Send Prepared Message to Contact (C): This automation sends a prepared message to every new group member when he is added to the group.
    For this combination, check ​Use Event Parameter​ for the following fields: ​Group Name​ and ​Contact​.

  • Message Reply Received (C) + Send Prepared Message to Contact (C): This automation sends a prepared message to a contact who replies to an email message.
    It is necessary to configure the ​Reply Handling​ in the group settings. In the group settings, select ​Initiate an event-based automation​ from the drop-down list in the ​Replies​ field. The must be done in every group in which this automation should apply.
    For this combination, check ​Use Event Parameter​ for the following fields: ​Contact​ and ​Group Name​.

  • Event-based Automation Finished (S/C) + Send Prepared Message to Contact (C): This combination creates a multi-step automation. When a first defined automation is finished, sendout of a prepared message is initiated.

General

​Name​

Displays the name of the automation that is defined in the ​Edit Event​ window.

​Description​

Displays the description of the automation that is defined in the ​Edit Event​ window.

​Event​

Displays the event that is defined in the ​Edit Event​ window. Every time this event occurs, Engage executes the dependent job.

​Job​

Defines the job. Engage executes this job automatically every time the event occurs. For a list of all available jobs, see ​All Available Event-Based Jobs​.

Define Job​

This area defines the specific parameters of the job.

  • Message: This drop-down list defines the prepared message. All prepared messages saved in the system are displayed here.

  • Contact: This input field defines the contact who receives the prepared message. Use the symbol to select one contact.

    • Use Event Parameter: When selected, this checkbox sends the prepared message to the contact involved in the event. See the Recommended Automations above for examples.

  • Parameters: This area creates parameters that insert information from the event into the prepared message. See Add Event Data to a Prepared Message​.


Define Delay​

In this area, you can define a time delay between the event and the resulting job. If you define a delay, the system waits the specified amount of time after the event takes place before executing the event-based job. If you do not define a delay, the system executes the job immediately after the event takes place.

Hint:

Engage calculates the selection for an event-based job when the job is executed, not when the event takes place. When you define a delay, the selection is calculated after the delay


  • ​Delay:​ Defines whether there is a delay between the event and the resulting job.

    • ​No: ​There is no delay between the event and the resulting job. When Engage registers the event, the system executes the job immediately.

    • ​Yes: ​Creates a delay between the event and the resulting job.
      ​Unit:​ Defines the unit of time with which Engage calculates the delay.
      ​Value:​ Defines the duration of the delay.

Actions

The following actions are available: