# Wait for customer property change

The "Wait for Customer Property Change" component provides a dynamic approach to user journeys, enabling you to wait for specific customer properties to change before proceeding to the next step. This feature proves invaluable when you want to engage customers at precisely the right moment, ensuring that your interactions align with their evolving preferences and behaviors.

For instance, you can wait until a customer's segment changes, their age is updated, or their email address is modified, ensuring that your communication is always current and relevant.

<figure><img src="/files/Uxy0hqUUkDoPQ1dhJ70c" alt=""><figcaption></figcaption></figure>

The flexibility of this component allows you to wait for any change in specified customer properties or wait for specific values to be reached.

Utilize standard system properties such as Name, Email, Phone, and others, or incorporate custom properties created in the [Customers](/en/admin-ui/customers.md) section. These properties can be sourced from external systems like CRM or ERP, enabling seamless integration and real-time updates.

By leveraging the "Wait for Customer Property Change" component, you can engage customers precisely when their profile information evolves, fostering a sense of timeliness and relevance in your interactions. This real-time approach ensures that your communication remains personalized and responsive, enhancing customer satisfaction and engagement.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://academy.gopersonal.ai/en/admin-ui/journeys/workflow/delays/wait-for-customer-property-change.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
