URL not dynamic during Engagement Messenger deployment

[zakzadri]

Hello everyone,

We are currently facing an issue during the production deployment of Engagement Messenger.

The URL is expected to be dynamic depending on the instance (DEV / TEST / PROD). However, in our case, the URL remains static and does not automatically adapt to the target environment.

More specifically:

• The configured URL does not change based on the instance.

• At this stage, we have not identified a native mechanism that makes the URL instance-aware.

Has anyone experienced similar behavior?
Is there a recommended best practice to make the URL dynamic during deployment (e.g., system property, environment variable, script adjustment, configuration pattern, etc.)?

Thank you in advance for your feedback.