Playbook How to - Set Modify Attribute Control
- Parker Hutcheson (Deactivated)
A modify attribute control allows the playbook designer to influence data on an account for the purpose of influencing their journey through a playbook or setting attributes for use in reporting/analytics.
Oftentimes, the modify attribute control will be required for instances where data supplied by the client is not satisfactory to achieve a use case.
Table of Contents
Feature Capabilities
The modify attribute control can be placed anywhere within a campaign and allows the playbook designer to configure up to 10 attributes to be updated within the same control. The attribute modifications that are available to the playbook designer are as follows:
Modify a Boolean Attribute to Fixed value of True or False
Modify a String Attribute to a Fixed string value
Modify a Number Attribute to a:
Fixed Number Value
Random Number between a Min and Max Value
Modify a Date Attribute to a:
Fixed Date Value
Date/Time relative to the account entering the control
How to Set a Modify Attribute Control
During the execution of a playbook, the set attributes will be updated upon entering the Modify attribute control. Special Considerations on execution are as follows:
The Modify Attribute control will be executed for each unique entry to a campaign. This means if a Modify Attribute control was executed in Campaign A, and that account moves to Campaign B and back to Campaign A, the same modify attribute will be eligible to execute again.
Setting a Key Date for use in Outreach Scheduling
Clients of Symend expect that we are able to engage with their customers at the right time. The right time may be derived from key dates provided by the client, actions that their customers have taken, or non-date based attributes provided by the client.
All clients not have the capabilities to provide “key dates” that correspond with their desired outreach timing. Their expectation is that if a customer has had a change in their attributes and those attributes have been transmitted to Symend, that Symend has enough information and logic to trigger engagements. For example, their expectation is that if a CUSTOMERSTATE attribute has been updated from “Overdue” to “Suspend” with no other corresponding attribute change for that account, an outreach should be delivered within N days to indicate that customer has entered a new state of delinquency. In this example, the desired outcome may look something like this:
Send Email N Day(s) After CUSTOMERSTATE = “Suspend”
This above outcome can be achieved by placing a modify attribute control at the start of that campaign, where a custom attribute such as “SuspensionDate” is modified to {{TODAY}} which is a date relative to the date/time the customer entered the control.
Setting Short-Term Holds Provided via an “Exclusion File”
Clients of Symend expect that they can hold customers from outreaches at their discretion through use of an “exclusion” file. Often times, the exclusion file contains a list of accountID’s and expect that Symend will hold outreaches based on an agreed upon period, typically 24 hours.
The modify attribute control can be leveraged in this scenario to accommodate limited time holds as outlined here:
Exits when Limited Information is Provided in an Exit File
Clients of Symend expect that they can exit customers from a playbook episode at their discretion through use of an “exit” file. In some cases, the exit file contains a list of accountID’s and expect that Symend will be able to exit accounts from their playbook episodes based on that information.
The modify attribute control can be leveraged in this scenario to accommodate playbook exits as outlined here: