Tag: rule editor

Triggering Messages Based on Anniversaries

BizConnector makes it very easy to trigger emails, SMS messages, and other actions based on the anniversary of any date in your Lead, Contact, Account, or Opportunity records.

This could, for example, be a birthday, an appointment date, or a contract start or expiration date.

As usual in BizConnector, this is done by setting up a rule. In the Rule Editor, you will find ‘pseudo’ fields that are related to date fields in your records. These ‘pseudo’ fields are not real fields, but they are inserted in the field list to make it easy to create a condition.

For example, let’s say we want to send a message on the anniversary of an appointment:

The above condition reads ‘Five days before the appointment anniversary’. That’s all it takes to make the rule fire. This example makes the assumption that you want to send a message five days before the date. Once it fires, you can set any action – for example send an email or sequence of emails, send an SMS message, etc.

Do you have any need to automate messages on the anniversary of a date? If you would like more information about this and other features of BizConnector, please contact us.

Happy messaging!

 

Using Rules To Automate Contract Expiration Notices

One popular need for BizConnector users is to automate the production of contract expiration notices.

This is a fairly straightforward use case, but one that is not easily handled by other tools. BizConnector comes to the rescue with two ‘pseudo fields’:

  • Minutes To
  • Days To

that make this easy to implement. These fields are not to be found in the original object definitions, but are derived from date or datetime fields.

For example:
Say you have an Opportunity date field ‘Contract Expiration’. [This is an appropriate field for an Opportunity record].

The objective is to send one or more emails to your customer contact, starting 60 days before the contract is due to expire. To do this, you would create a rule expressly for this purpose. Let’s call the rule ‘Contract Expiration Notices’.

In the rule editor, after naming the rule, you would create the rule condition:


The second (and last) step is to set up the email sequence:

Note that the delay ‘None’ means that Expiration Notice #1 will be sent when the rule fires – 60 days before the expiration date, and Expiration Notice #2 will be sent 30 days later – 30 days before the expiration date.

Note also that the above rule will fire based on information in the Opportunity record, but send emails to the Contact(s) related to that Opportunity. This is a feature of BizConnector, which is deeply integrated with Salesforce and knows the Salesforce model.

That’s all there is to it!

For more information about this, or to attend an online demo, please contact us.