Pause Event (Action)

Modified on Tue, 27 Aug at 3:02 PM

The Pause Event is a distinct workflow tool designed to temporarily halt the progress of a contact at a particular stage until a specific condition is satisfied. This functionality is especially useful when you need to wait for triggers such as a tag, an appointment, an event, a specific time, or a response from the contact.

Pause Event Image

Pause For


The Pause For feature provides various options depending on the desired outcome.

Time-Based Events:

  • Delayed Timing

  • Event/Appointment Timing

CRM Events:

  • Condition Met

  • Contact Reply

  • Trigger Link Clicked

  • Email Interaction

Pause For Image


Time-Based: In a time-based Pause Event, the contact remains paused for a specific duration until a condition is met or the contact responds.


Time Delay: The Time Delay option allows you to set a pause duration in minutes, hours, or days. Once this period elapses, the contact proceeds to the next step in the workflow.


Time Delay Image


Advanced Scheduling: Enabling Advanced Scheduling restricts movement to the next step only if the event falls within the specified year, month, day, and time frame.

Resume On: This option lets you specify a particular day of the week for resuming the workflow.


Advanced Scheduling Image


Resume Between Hours: This feature allows setting a specific time range during the day for resuming the workflow.


Resume Between Hours Image


Additional Filters: Use Additional Filters to fine-tune events based on specific years or months, making the filtering process more accurate.


Additional Filters Image


Event/Appointment Timing: The Event/Appointment Timing Pause Event delays the contact based on the details of an upcoming event or appointment. For instance, you can hold a contact at this stage until they respond to a Yes/No question or until a scheduled appointment reminder needs to be sent.


Pause Until: The Pause Until option lets you decide whether the action should occur before or after the event or appointment.

  • After: Often used for post-event actions such as surveys or feedback requests.

  • Before: Useful for setting reminders prior to an event, with timing options like minutes, hours, or days before.

  • Exact Time: This option triggers actions exactly at the event time, rather than using a relative time frame like minutes or hours before or after.

Pause Until Image


NOTE: If the timing for the Pause step is already in the past, you can choose how the contact should proceed:

  • Move to the next step.

  • Skip to a specific step.

  • Bypass all outbound communications until the next Pause or Event Start Date action (e.g., Email, SMS, call, voicemail).


CRM Events:

  • Condition: Hold the contact until a specific condition is met.

  • Segment: Useful for scenarios like requiring the contact to be located in Texas, USA, before moving to the next step.

CRM Events Image


Add New Condition or Segment: New conditions or segments can be added using the + buttons.

Add Condition Image


Contact Reply: The Contact Reply feature pauses the workflow until the contact responds to a specified event.

Contact Reply Image


Trigger Link Clicked: The Trigger Link Clicked option allows users to pause the workflow until the contact clicks a specified trigger link. Multiple trigger links can be selected.

Trigger Link Image


Email Event: This feature lets you choose the email event that will trigger the workflow to proceed.

Email Event Image


Select One or More Email Events: You can choose multiple email events that will trigger the next action if the contact's response matches the criteria.

Select Email Event Image


Timeout: The Timeout option sets a duration within which a response is expected from the contact. This period can be configured in minutes, hours, or days.

Timeout Image


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article