Issue: Partial transcripts trigger endpointing and are sent to custom-LLM
Description:
We are experiencing an issue where partial transcripts generated by Deepgram trigger the endpointing rules and are forwarded to our custom-LLM, causing incorrect messages to be sent before the final transcript arrives.
For example (call id below):
Partial transcript at Sep 08, 12:17:16.183
Message to custom-LLM (incorrect transcript) at Sep 08, 12:17:17.095
Final transcript at Sep 08, 12:17:17.129
Message to custom-LLM (correct transcript) at Sep 08, 12:17:17.632
This behavior creates multiple issues in our workflow, as only the final transcript is accurate enough for our use case.
Request:
We would like guidance on how to configure Deepgram so that endpointing and downstream triggers only occur on final transcripts. Ideally, partial transcripts should not trigger endpointing events or be sent downstream.
Call ID:
d3fe3c30-67fd-4ad8-bb22-8672fc7219e9
We are experiencing an issue where partial transcripts generated by Deepgram trigger the endpointing rules and are forwarded to our custom-LLM, causing incorrect messages to be sent before the final transcript arrives.
For example (call id below):
Partial transcript at Sep 08, 12:17:16.183
Message to custom-LLM (incorrect transcript) at Sep 08, 12:17:17.095
Final transcript at Sep 08, 12:17:17.129
Message to custom-LLM (correct transcript) at Sep 08, 12:17:17.632
This behavior creates multiple issues in our workflow, as only the final transcript is accurate enough for our use case.
Request:
We would like guidance on how to configure Deepgram so that endpointing and downstream triggers only occur on final transcripts. Ideally, partial transcripts should not trigger endpointing events or be sent downstream.
Call ID:
d3fe3c30-67fd-4ad8-bb22-8672fc7219e9
