The inbound message flow keeps dropping the custom priority_level attribute we attach via the webchat SDK. External endpoint receives a JSON payload with null values. Webchat console confirms it’s set on the participant object before routing, so we’re mapping {{contact.attributes.priority_level}} in the data action JSON mapping and the architect expression evaluator just skips webchat metadata.