As described in the article “How to Automate Your Pipeline Columns?”, there is a limited list of conditions available for creating appropriate triggers. These conditions are designed to help you trigger automation based on certain criteria or actions related to your accounts or contacts.
Keep in mind that these conditions will be available only in case you use MindBody, POW or Peak integration. However, if you use Zapier integration, automation of the 'Leads' column can be adjusted in the way described here.
Here’s a brief explanation of each condition:
– Account Directly Communicated
You can automate your pipeline columns based on whether there has been direct communication from your account to a contact. This includes 1-1 emails, calls, or texts. Campaign messages are not included, only 1 on 1 communication.
Example of a contact that belongs to this status (satisfies the condition):
You sent a Text message to the contact.
If the Quick Connect feature is enabled, keep in mind that these calls are considered a one-way communication from your account to a contact. All leads initially reached out to via a Quick Connect call will be moved to the Pipeline column with the ‘Account Directly Communicated’ condition.
– Contact Directly Communicated
Similar to the above, this condition focuses on direct communication (email, text, or call). The difference is that this tracks direct communication from a contact to your account.
This condition applies when:
The contact sends a Text message to your smartline.
Please note that we currently can’t track if a contact sent you an email, but you can manually log(record) this action from a contact’s page.
– Booking in Future
With this condition you can segment leads who have or don’t have any booking set for the future.
– Custom Fields
You can use any custom field that you’ve created in your Referrizer account and set the automation for a particular pipeline column. This way, your pipeline automation can be customized, taking leads segmentation to the next level.
UTM Parameters Added to Custom Fields
We’ve now integrated UTM parameters within our custom fields. By using these to map customers who come from paid ads, you can easily set up automation within your pipeline columns to ensure you never lose track of these customers.
Example of a contact that belongs to this status (satisfies the condition):
The source of the particular contact is a UTM Campaign named “50% Off On All Services” that you’ve connected to your Zapier.
– Last Booking Status
This condition allows you to trigger automation based on the last status of a booking. For example, you can automate actions when a booking status changes from “Open” (booked/scheduled) to “Canceled.” Only the status of the latest booking is considered.
Example of a contact that belongs to this status (satisfies the condition):
The contact’s latest booking has been canceled.
– Last Purchased Category (POW integration)
This condition allows you to trigger automation based of the service category most recently purchased.
Example of a contact that belongs to this status (satisfies the condition):
The last purchased service category was IV Drips.
– Last Time Account Directly Communicated
This condition considers the last time there was direct communication (email, text, or call) from your account to a contact. You can set up automation triggers based on this time frame.
Example of a contact that belongs to this status (satisfies the condition):
LAST TIME ACCOUNT COMMUNICATED equals 10
(The last communication was 10 days ago (e.g., the last time you sent a text message to the contact was 10 days ago)).
– Last Time Contact Directly Communicated
Similar to the previous condition, this one focuses on the last time there was direct communication (email, text, or call) from a contact to your account.
Example of a contact that belongs to this status (satisfies the condition):
The last time the contact sent a Text message to you was 10 days ago.
Please note that we currently can’t track if a contact sent you an email, but you can manually log(record) this action from a contact’s page, and this condition will trigger based on the time this action was recorded.
– Last Visit
This condition considers the last time a contact visited your business. All time frames from the List View filter popup are available. The ‘today’ timeframe is excluded because this automation runs once daily.
Example of a contact that belongs to this status (satisfies the condition):
The last time the contact visited your business was within last 30 days.
– Mindbody Member
This condition relates to membership status within the Mindbody integration. You can trigger automation based on whether the contact becomes a member.
Example of a contact that belongs to this status (satisfies the condition):
The contact’s status within the Mindbody system changes to “Member”.
– Number of Bookings
You can automate your pipeline columns based on the number of bookings a contact has ever had.
For example, you can set an automation for the column ‘First Appointment Booked’ and add this condition to bring in all leads who have made first-time bookings or have scheduled their first-class.
Example of a contact that belongs to this status (satisfies the condition):
NUMBER OF BOOKINGS greater than 0
(A contact has at least 1 booking scheduled).
– Past POW Member Yes/No
This condition relates to membership status within the POW integration. You can trigger automation based on whether the contact’s status switches from member to non-member at any time.
Selecting option ‘No’ helps you define contacts who have never been members before.
Example of a contact that belongs to this status (satisfies the conditions):
The contact’s status within the POW system changes from “Member” to “Non-Member”.
– POW Member Yes/No
Similar to “Mindbody Member,” this condition relates to membership status within the POW integration. You can trigger automation based on whether the contact becomes a member or by selecting option ‘No’ if the contact is not a currently active POW member.
Example of a contact that belongs to this status (satisfies the condition):
The contact’s status within the POW system becomes “Member”.
– Past Mindbody Member
This condition relates to membership status within the Mindbody integration. You can trigger automation based on whether the contact’s status switches from member to non-member at any time.
Example of a contact that belongs to this status (satisfies the conditions):
The contact’s status within the Mindbody system changes from “Member” to “Non-Member”.
– Registration Date
This condition can help you automatically segment your leads based on the number of days since they registered.
Example of a contact that belongs to this status (satisfies the condition):
The contact registered within the last 7 days.
– Tag
You can trigger automation based on tags you have created within your Referrizer account.
Example of a contact that belongs to this status (satisfies the condition):
The contact has a certain tag (name of some campaign) assigned to their profile.
– Text Unsubscribed
You can trigger automation based on whether a contact has unsubscribed from receiving text messages.
Example of a contact that belongs to this status (satisfies the condition):
The contact has unsubscribed from your text message advertisements and promotions.
– Type
This condition refers to the type of contact within the Referrizer system, such as Leads, Current or Past Customers. You can automate your pipeline columns based on this type of entity.
Example of a contact that belongs to this status (satisfies the condition):
The contact’s info field labeled “Type” is set to equals “Leads”.