Is it possible to update the confidence threshold for a specific intent via the /v2/bots/botId/nlu/intents endpoint without triggering a 400 Bad Request? The payload below results in a validation error despite matching the schema definition.
{
"id": "intent_123",
"name": "OrderStatus",
"confidenceThreshold": 0.85
}
This issue stems from the confidenceThreshold field being read-only during intent updates via the Bot API. Unlike Zendesk, where custom attributes could sometimes be patched directly on ticket forms, Genesys Cloud enforces strict immutability on NLU configuration parameters to maintain model integrity. The API documentation explicitly states that confidence thresholds are managed at the Language Model level, not the individual intent level, which explains the 400 Bad Request when attempting to modify it here.
To resolve this, navigate to Admin > Bot > Language Model and adjust the global confidence threshold for the specific language. Alternatively, use the /v2/bots/{botId}/languages/{languageId} endpoint to update the confidenceThreshold property within the language configuration object. This mirrors the Zendesk approach of setting global deflection rules rather than per-ticket thresholds. After updating, retrain the bot model to apply the new NLU settings. This ensures the virtual agent evaluates intents against the correct baseline without triggering validation errors.