On Attribute Changed
On Attribute Changed is a bot trigger that activates when a customer attribute is updated in DoubleTick.
Attributes are stored customer details that help you track progress and segment leads, such as:
Lead stage
Customer type
Interested product
Location
Visit scheduled (Yes/No)
Whenever the value of an attribute is set, updated, or removed, this trigger can automatically start a bot journey.
Where to Use This Trigger
Use this trigger when your automation depends on customer status or lifecycle movement.
It is especially useful for:
Lead funnel automation
Sales stage follow-ups
Personalized messaging based on customer actions
CRM-style workflows inside DoubleTick
How This Trigger Works
When you select On Attribute Changed, DoubleTick gives you a dropdown to choose:
Which attribute you want to track Example: Lead Stage
When the bot should run, based on three trigger conditions:
Option 1: On Set First Time
This runs only when the attribute is being assigned for the very first time.
Use this when you want automation only at the initial update.
Example: Lead Stage is set to “Interested” for the first time → Bot starts welcome journey.
Option 2: On Changed Any Time
This runs whenever the attribute value changes from one value to another, at any point.
Use this when you want automation at every stage movement.
Example: Lead Stage changes from “Interested” → “Converted” → Bot sends onboarding steps.
Option 3: On Removed
This runs when the attribute value is removed or cleared.
This is useful for attributes that work like Yes/No flags.
Example: Visit Scheduled = Yes is removed → Bot sends a follow-up asking to reschedule.
How to Use It in Bot Studio
Open Bot Studio and create a new journey
Select trigger: On Attribute Changed
Choose the attribute from the dropdown (example: Lead Stage)
Select when the trigger should run:
On Set First Time
On Changed Any Time
On Removed
Build the automation steps and publish the journey
Key Capabilities
Supports automation based on customer lifecycle updates
Helps build stage-based and personalized journeys
Works well for CRM-style workflows
Gives control over first-time, repeated, or removed changes
Example Use Case
A sales team uses Lead Stage as an attribute.
When Lead Stage is set to “Interested” (first time), the bot sends product details
When it changes to “Converted”, the bot sends onboarding steps
If a scheduled visit value is removed, the bot sends a rescheduling reminder
Last updated