Why are different speaker_ids assigned to the same speaker in a transcript?
Last updated: January 15, 2025
You may notice that in some transcripts, the same speaker is assigned different speaker_ids. This is expected behavior in certain situations and doesn't indicate an error in the transcription process.
Why does this happen?
Different speaker_ids are assigned to the same speaker when a participant leaves and rejoins the meeting while the Recall bot is active in the call.
How Recall assigns speaker_ids
Recall assigns a unique speaker_id to every participant in the meeting. When a user leaves and rejoins the call, they are considered a new participant because most meeting platforms don't provide a consistent unique ID for participants across disconnections.
Impact on transcripts
This behavior can cause the transcript to appear as if there are different speakers, even though it's the same participant. For example:
{
"speaker": "Jay Dedhia",
"speaker_id": 200,
...
},
{
"speaker": "Jay Dedhia",
"speaker_id": 400,
...
}
If you have any further questions about speaker identification in Recall transcripts, please don't hesitate to reach out to our support team. Thank you!