Administrators can use the Rules Engine to create or to close multiple CTAs. You might want to create CTAs automatically for a drop in usage data, drop in revenue, low NPS® score, high priority support cases open for more than 14 days, product usage more than the issued licenses, and so on. The examples below are for addressing drops or increases in usage.

The following sections describe how to create and close CTAs using the Rules Engine:

  • Creating CTAs from Rules Engine
  • Closing CTAs from Rules Engine

Creating CTAs from Rules Engine

The following procedure helps you create multiple CTAs using Rules Engine. For example, you want to trigger a CTA when utilization drops below a certain percentage.

1. Navigate to Administration > Rules Engine > click +RULE.

2. On the New Rule page, enter the following details used in the following example:

  • Rule Type: Select Bionic.
    Note: Following are the type of rules available in Rules Engine:
    • BIONIC: Use this rule type to perform multiple fetches and transformations in a single rule like fetch data from multiple sources, merge, aggregate, and then load to an object.
    • CUSTOM: This rule type will be deprecated soon. Gainsight recommends using Bionic Rules to leverage more of the advanced Rules Engine capabilities.
  • Rule For: Select Account if you want to close CTAs created on an Account. Otherwise, select Relationship if you want to close CTAs that are created on a relationship.
  • Rule Name: Enter the name for the rule being created.
  • Description: Enter appropriate description for the rule being created.

Create-Rule-page1.png

  1. Click NEXT. This navigates you to the Setup Rule page.
  2. Click DATASET TASK.

Create-DATASET.png

  1. Drag-and-drop fields from the left hand side panel in the Show area. For example, Account Name.
  2. Drag-and-drop appropriate fields in the Filters area to filter out CTAs that you want to create.
  3. Click SAVE. Name the task before saving it.

new datataset.gif

  1. Click  Setup Action.
  2. Click +ACTION. 
  • Action Type: Select Call to Action from this drop-down list. To create a CTA, select the Create CTA check box and fill out the following fields:

clipboard_e1b262f273f4f4c06aed47a5cb672d997.png

  • Name:  Used to title your CTA. Type @ to see the options available for tokenized comments.
    • Include in identifiers: If this option is selected, CTA name is used as an identifier along with the account, CTA Type, Reason, and Status (open and closed) while looking for open CTAs that should be updated. If there's an existing CTA for an account, but the CTA names have different values, then the rule will create the new CTA. If the CTA names are the same, and the CTA Type, Reason, and Status (open and closed) are the same, then a new CTA will not be created. The rule simply updates the existing CTA. The playbook chosen in this step will only be applied if a playbook was not previously assigned.
  • Priority:  Based on previously established Severity Types
  • Type:  Based on previously established Types
  • Status:  Based on previously established Status Types
  • Playbook: Optional.  Based on previously established Playbooks
  • Reason: Based on previously established Reason Types
  • Owner Field: Optional. From the account level can be based on any user lookup field. Only ID fields are allowed to map in this field.
  • Due Date: Run Date + x Days. Run Date is the date on which the rule is executed. Drop-downs below Due Date address treatment of weekends.

Note: Run Date can be different from Rule Date, if a different date is selected in RUN NOW dialog. For more information, refer Scheduling Rules.

  • Default Owner: Lookup field of all Salesforce Users. This will be used if the Task Owner field is not filled in OR if an account has not been assigned an owner.
  • Link to an existing "Linked Object": Multiple relevant objects can be linked in a rule. All Linked Objects that are linked to the CTA type, will be available in the drop-down. When a linked object is selected from the drop-down, Admins can choose the field to which it should be linked from the Show fields.
  • Post Update to Chatter: Used to control the frequency of Chatter updates.
  • Post Update to Comments: Used to control the frequency of Comments updates.
  • Comments: Optional and shows up in the comments section of the CTA. Type @ to see options available for tokenized comments.
  • Create CTA once in: If this option is selected, it restricts the creation of CTA based on Company ID, Rule ID, and Action ID identifiers. On the first instance of rule execution, a CTA is triggered as per rule configuration. In general, if you do not select this checkbox, it triggers a CTA after the next rule execution if CTA triggered from previous rule execution is closed. Admins can select the Create CTA once in check box in the Create CTA action to prevent creating CTAs from the second instance of rule execution until the selected timeframe. If you do not select this checkbox, CTAs keep triggering as soon the previous triggered CTA is closed.

    Note: If a triggered CTA is deleted, a new CTA is triggered after the next rule execution irrespective of whether you select this checkbox or not. 
  1. Click SAVE to move to the next step or click +ACTION to add more actions.

clipboard_e52fbeb593ff0216988fa3f24b18dba0b.png

  1. Click +CRITERIA and add the appropriate criteria. For example, you might want to create a high priority CTA if the utilization percentage is less than or equal to 40. You can repeat steps 6 and 7 to create additional CTAs for different criteria. For example, apart from creating High priority CTAs, you might also want to create Low and Medium priority CTAs based on utilization percentage.

clipboard_efabfa0d293853c1c38680be6c5f78446.png

Populate Custom fields while creating CTAs from Rules Engine

If you want to create a CTA with Custom Fields along with the Default Group of fields in Rules Engine > Setup Action, perform the following steps:

  1. Ensure that you have configured the Default Group containing the Custom Fields first from Administration > Calls to Action (CTA) > GLOBAL tab > Select the Default type > Detail view layout configuration section > CALL TO ACTION tab.

a. Standard fields are Read Only by default as shown in the following image. Custom fields that are marked as Read Only, will not be displayed in the Setup Action screen in Rules Engine.

b. Custom fields that are marked as Mandatory, values must be provided in the Setup Action screen in Rules Engine.

123456.PNG

  1. In Administration > Rules Engine > + RULE (Bionic Rule - Custom Fields in Bionic Rules) > Setup Rule screen, click NEXT after adding the required datatypes in the Show and Filters sections and navigate to Setup Action screen.
  2. Click +ACTION and from the Action Type drop-down list, select Call To Action.
  3. Select the CTA Type. Depending upon CTA Type, it will  show all the custom fields (under Additional Fields) that you Configured in Detail view layout configuration section > CALL TO ACTION tab. The following image shows an example of Additional fields section that contains custom fields configured from Calls to Action > GLOBAL tab > Select the Default type > Detail view layout configuration section > CALL TO ACTION tab.

111.png

Updating Existing CTAs with Rules

Based on the identifiers used in the CTA action, CTAs are up-serted (Type and Reason are default identifiers). If there is an existing CTA that matches the identifiers, then it is updated.

While updating:

  • Priority is updated if the new Priority is higher than the existing CTA's priority.
  • Chatter/Comments are updated based on the "Post update to chatter and/or comments" flag.
  • If existing CTA does not have a playbook and the new CTA has a playbook, then the playbook will be applied. 

Manage Calls to Action (CTA's)

To see the list of CTAs created from the Rules Engine, navigate to Cockpit > List View. For more information about how to manage CTA workflow, refer to the Create manual Calls to Action & Tasks article.
Managing Calls to Action (CTA's)

Closing CTAs from Rules Engine

The following procedure helps you close multiple CTAs using the Rules Engine. For example, let's say that some time after a CTA is triggered due to low usage, the usage actually increases above a certain threshold, and the Admin wants to use rules to automatically close out the CTA.

1. Navigate to Administration > Rules Engine > click +RULE.

2. On the New Rule page, enter the following details:

  • Rule Type: Select Bionic.
  • Rule For: Select Account if you want to close CTAs created on an Account as shown in the following image.
  • Rule Name: Enter the name for the rule being created.
  • Description: Enter appropriate description for the rule being created.

CTA-test-create-rule.png

Note: On the New Rule page, enter the following details to close Relationship CTAs:

  • Rule Type: Select Bionic.
  • Rule For: Select Relationship if you want to close CTAs created on a Relationship as shown in the following image.
  • Rule Name: Enter the name for the rule being created.
  • Relationship Type: Select the type from the drop-down list.
  • Description: Enter appropriate description for the rule being created.

CTA-test-create-rule relationship.png

  1. Click NEXT. The Setup Rule page is displayed.
  2. Click DATASET TASK.
  3. Drag-and-drop fields from the left hand side panel in the Show area. For example, Account Name.
  4. Drag-and-drop appropriate fields in the Filters area to filter out CTAs that you want to close.
  5. Click SAVE.

Setup-data.gif

  1. Click Setup Action.
  2. Click +ACTION; and then enter the following details:
  • Action Type: Select Call to Action from this drop-down box. The following page is displayed.
    • To create a CTA, select the Close CTA check box and fill out the following fields:

Close CTA.png

  • CTA ID: Select ID from the drop-down list.
    • Include CTA ID as Identifier: In the Close CTA action, Admins can now select the CTA ID > Include in identifiers checkbox to validate if the CTA ID should be included in identifiers while closing CTAs.
      Notes:
      • When you select the Include in identifiers check box, the rule action will use only CTA ID as an identifier and will close every CTA that is brought into the query in the rule setup. The Type, Source, Reason, and Set CTA status to fields will become disabled and restricts the rule to mapping only with the CTA ID field.
      • When you do not select Include in identifiers check box, the rule action will close any CTA that meets the Type and Reason specified in the Close CTA action for the accounts that are pulled into the query.
  • Type:  Risk, Opportunity, or Event. 
    Note: You cannot close Objective type CTAs via Rules Engine.
  • Reason: Based on previously established Reason Types.
  • Source: Manual, Rules and/or Survey. Select one or multiple.
  • Set CTA status to:  Closed Lost, Closed Success, or Deprecated Internal Escalation.
  • Comments: Optional and shows up in the comment section of the CTA. Type @ to see options available for tokenized comments.

Notes:

  • If a CTA with the same Type, Reason, and Source exists, this rule will close the CTA. You can then click SAVE to move to the next step, or click +ACTION to add more actions.
  • CTA types associated with relationship types are available in the CTA type drop-down. CTA status associated with the Relationship type, CTA type, Global active All, and Private All are available. CTAs of the selected Relationship type can be closed.
  • While Closing CTA's, the Criteria configured is used only to filter out the applicable Accounts. While closing CTA's it is recommended to close by CTA ID.
NPS, Net Promoter, and Net Promoter Score are registered trademarks of Satmetrix Systems, Inc., Bain & Company and Fred Reichheld.