Skip to content
Patient Copilot Help Center

Workflow Trigger - Contact Changed

Imagine having a helper that automatically does important tasks whenever a contact’s information changes. That’s exactly what the “Contact Changed” Workflow Trigger does in your CRM! It keeps track of changes, like new tags being added, updates to custom fields, or when a contact is assigned to someone, and then performs actions based on those changes. Let’s learn why it’s useful and how you can set it up step by step. * * * ## Frequently Asked Questions Q. What types of contact changes can trigger the “Contact Changed” workflow? The “Contact Changed” trigger can activate based on various contact updates, including: - Tags Added or Removed – Example: If a contact is tagged as “Hot Lead”, trigger a sales follow-up.

  • Contact Type Changed – Example: If a contact goes from a “Lead” to a “Customer”
  • Custom Field Updates – Example: If a contact’s “Preferred Service” is updated, send targeted promotions.
  • Assigned User Change – Example: If a contact is reassigned to a new sales rep, notify the rep immediately.
  • DND Status Change – Example: If a contact enables “Do Not Disturb”, stop all outgoing messages. Q. Can I track multiple contact changes within a single workflow? Yes! You can add multiple filters under the “Contact Changed” trigger to track different types of changes simultaneously. For example, you can configure the workflow to trigger when either a tag is added OR a custom field is updated, ensuring the automation responds to multiple events. Q. What happens if a contact’s details change multiple times? Will the workflow trigger each time? Yes, the workflow will trigger each time a tracked change occurs. However, to prevent unnecessary actions (e.g., multiple emails being sent), you can: - Use workflow conditions to check whether the action has already been performed.
  • Apply filters to trigger only on specific changes.
  • Add time delays to avoid excessive automation. Q. Can I trigger actions based on a deleted tag or an old value being removed? No, the “Contact Changed” trigger detects new updates but does not track removed values. If you need to automate actions based on a tag being removed, consider: - Using an “If/Else” condition to check whether a contact still has a specific tag.
  • Manually monitoring tag removals and triggering a different workflow accordingly.