Architect Bot Intent mismatch mapping Zendesk deflection rates

Trying to make sense of why the Architect flow drops to the human queue despite high confidence scores on mapped intents.

Migrating Zendesk bot deflection logic to Genesys Cloud AI Bots using the latest SDK version 2.8. The intent mapping seems correct in the interface, yet the /api/v2/analytics/conversations/details/query endpoint shows zero matches for migrated intents. The JSON payload from Zendesk triggers the ‘No Match’ path immediately. Is there a specific tokenization difference between Zendesk AI and Genesys that I am missing in the admin config?