Hello @Sahil @Shubham Bajaj when you set startSpeakingPlan options, how do waitSeconds, smartEndpointingEnabled, and transcriptionEndpointingPlan interact? e.g. If I set smartEndpointingEnabled = true but don't set the other 2 options, are they still active at their default values? Is responseDelaySeconds deprecated? Thanks!

object
Optional
This is the plan for when the assistant should start talking.

You should configure this if you’re running into these issues:

The assistant is too slow to start talking after the customer is done speaking.
The assistant is too fast to start talking after the customer is done speaking.
The assistant is so fast that it’s actually interrupting the customer.

Hide 3 properties
waitSeconds
double
Optional
This is how long assistant waits before speaking. Defaults to 0.4.

This is the minimum it will wait but if there is latency is the pipeline, this minimum will be exceeded. This is really a stopgap in case the pipeline is moving too fast.

Example:

If model generates tokens and voice generates bytes within 100ms, the pipeline still waits 300ms before outputting speech.
Usage:

If the customer is taking long pauses, set this to a higher value.
If the assistant is accidentally jumping in too much, set this to a higher value.
@default 0.4

smartEndpointingEnabled
boolean
Optional
Defaults to false
This determines if a customer speech is considered done (endpointing) using the VAP model on customer’s speech. This is good for middle-of-thought detection.

Once an endpoint is triggered, the request is sent to assistant.model.

Default false since experimental.

@default false

transcriptionEndpointingPlan
object
Optional
This determines how a customer speech is considered done (endpointing) using the transcription of customer’s speech.

Once an endpoint is triggered, the request is sent to assistant.model.