Hi Stéphane,
Thanks for confirming this with engineering - that aligns with what I've seen as well 👍
Just to add a bit of context for others reading this:
even though the alternatives array is still part of the event structure, it's effectively always a single element today, so it's safe to treat it that way in most implementations.
That said, since it remains an array for backward compatibility, it's still a good practice to handle it generically (iterate instead of assuming index [0]) to stay future-proof.
Best regards,
Cesar
------------------------------
Cesar Padilla
INDRA COLOMBIA
------------------------------
Original Message:
Sent: 06-05-2026 02:29
From: Stéphane Labrune
Subject: Question about the structure of the topic v2.conversations.{id}.transcription
Thank you for the response, it confirms what I observed.
Regards,
------------------------------
Stéphane Labrune
NA
------------------------------
Original Message:
Sent: 06-04-2026 12:26
From: Jerome Saint-Marc
Subject: Question about the structure of the topic v2.conversations.{id}.transcription
Hello,
I have just checked with the engineering team in charge of speech analytics.
The fact that multiple values were possible in the alternatives property is for legacy reasons. Some former speech analytics services which could send several alternatives.
But it is not the case anymore. Now, Genesys Cloud will not send more than one alternative.
Regards,
------------------------------
Jerome Saint-Marc
Senior Development Support Engineer
------------------------------