Branch on a tag - Campaign “Decisions” settings

The Cloze Campaigns feature is included as part of the Cloze Business Platinum Plan

There are several types of decision options that can be automated with a Campaign. For example, a Campaign could branch based on a lead source and provide different content for each decision branch.

Below you will find the "Decisions" campaigns settings for Branch on a tag:

  • Tag to check

With this type of decision branch, you can check for the presence of a Tag on a Record like Person, Company, or Deal (Sale, Project, Property, etc.) or on the user running the Campaign. The campaign can then be triggered to start by a Next Step, Lead Source, or Anniversary Date.

Branching is a decision to go down only one of the different branches. The first branch to match gets its steps run – others are skipped. The Campaign then proceeds to complete all of the steps in the branch.

Campaign Example: Branch of by person tag to automatically send long-term nurturing email

This campaign is designed to help you stay top of mind with your network / sphere of influence

What this campaign does:

  • It fills the gaps in between your real conversations
  • It pauses automatically when you’re actively talking so there’s no “crosstalk”
  • It makes sure not to send the same content twice
    • e.g. you go on vacation and don’t update your newsletter

Cloze makes it easy to create a personalized newsletter by collecting articles you read. This campaign will wait for changes to your personal newsletter and then automatically send it when there is a pause in the conversation to all contacts with the tag "#sphere-of-influence". Here are step-by-step instructions on how to set up this campaign.

Branch on a tag campaign "Decisions" Settings.

Tap on the + icon and select Branch on a tag.

Tag to check

Tag

Enter the Tag that will be checked. 

Check Tag On

  • Record - Person, Company, or Deal (Sale, Project, Property, etc.)
  • User - User running the Campaign

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.