A customer-service team deploys a Foundry-hosted chat model and wants it to consistently stay polite, avoid discussing competitor products, and respond only in English, no matter what a customer types across a long, multi-turn conversation. Rather than repeating these instructions inside every customer message sent to the model, a developer sets them once in a distinct instruction channel that the model treats as standing guidance for the whole conversation. What is this instruction channel called?

The system message is the channel intended for exactly this purpose: standing instructions that shape the model's behavior, tone, and boundaries across an entire conversation. The developer sets politeness, the competitor-topic restriction, and the English-only requirement there once instead of repeating them in every customer turn, and the model treats that guidance as persistent context rather than something tied to a single message. The user-message approach is incorrect because user messages represent what the customer actually types in each turn; repeating behavioral rules there would require restating them constantly and would mix instructions with the customer's own content rather than establishing them as a stable baseline. The content-safety-configuration approach is incorrect because content safety configuration governs filtering of harmful content categories like hate speech or self-harm; it is not the mechanism for shaping tone, topic scope, or language preference, which are behavioral instructions rather than safety categories. The temperature-setting approach is incorrect because temperature controls how random or deterministic the model's word choices are; it does not cause the model to adhere to behavioral rules more closely, and a low-temperature response can still ignore instructions if those instructions were never actually provided.