Overview
This release introduces two new enhancements: Sequence Tags and the Consent Condition within Automations. Sequences give users visibility and control over delayed, automation-triggered messages. When a contact has a sequence tag applied , the system may schedule one or more delayed message actions, based on the automation configuration within the account. Consent Condition within Automations provides the ability to trigger an automation based off the consent level that is associated with the contact, meaning users can now utilize the contact’s consent level when selecting the conditions for an automation to trigger.
What’s New
Sequence Tags
A new Sequences field has been added to the Contact Column, enabling users to add a specific tag that is associated with a sequence of automations.
Details:
- The Sequence Tag List includes only tags referenced in automation conditions (not automation actions).
- Tags are filtered so the list contains only automation-relevant tags, avoiding clutter from general tagging.
- When a Sequence tag is added to a contact
- Immediate message actions execute normally (no change to current behavior).
- Delayed message actions are scheduled and shown as upcoming messages in the conversation UI (message compressor).
- The Sequence Tag List is dynamically generated and always reflects the latest active automations and available tags, ensuring users can search and see up-to-date triggers.
- After all scheduled messages for a given tag are sent, the tag is automatically removed from the Sequences list.
- Cancelling a Sequence: If a user removes a tag from Sequences, the system cancels all pending scheduled messages tied to that tag, but does not remove the tag from the main Tags list
Benefits:
- Improves timing and relevance of communications by giving teams a chance to intervene before delayed messages go out.
- Users can see exactly what will be sent and when, reducing “black box” automation behavior.
Consent Condition within Automations
The Consent Condition allows users to account for the consent level associated with a contact before triggering an automation, allowing you to create specific automated workflows for contacts that have provided a certain level of consent.
Details:
- The Consent Condition is now available when you create a new Automation.
- Consent Condition can be set based on the consent level that is applied, or the consent level that is missing from the contact
- Standard consent levels are available to select as the condition, as well as ‘No Consent’ or any custom consent you have created.
Benefits:
- Stronger Compliance: Can ensure a certain level of consent is received prior to allowing users to text with the contact.
- Improved Customer Experience: Create specific custom flows for contacts based on the consent they provided, tailored to the work within their consent level or upgrade the consent.
How to Update
No action is needed. Your application will be updated automatically the next time you log in.
