Add small delay to assistant-speaks-first
# support
a
We're finding that for an outbound call assistant-speaks-first is waay too fast. User barely has time to put the phone to their ear. How would we be able to add a slight delay so that the message starts after 1-3 secs? assistant-waits-for-user did not work reliably for us with users having to repeat themselves to start the call
v
message has been deleted
@amir I understand the need for a comfortable delay before the assistant starts speaking during an outbound call. While there isn't a direct function to add a delay, you can implement a workaround by adding a short period of silence at the beginning of the message that the assistant is supposed to speak. This can be done by prepending the audio message with a few seconds of silence. If you're using text-to-speech (TTS), you could add a pause using SSML (Speech Synthesis Markup Language) by including a break tag at the beginning of your message, like this:
Copy code
xml
<break time="2s"/>
This would create a 2-second pause before the message is spoken. You can adjust the duration (
"2s"
) to your preference, between 1 to 3 seconds as you mentioned. If you're playing an audio file, you would need to edit the audio file itself to include silence at the beginning. If you need assistance with implementing this or if you have any other questions, please let me know!
You can continue this conversation by mentioning me in the message.
a
Hey @User adding break time would be perfect, but this doesn't seem to be respected in First Message. Any suggestions for what i can do? Assitant ID is 59ef7e61-f6d9-498e-9fc1-5f15ac1bea76
I'm doing this from the dashboard for context
I was able to solve it. Putting at the beginning of text doesn't get respect by 11labs. Putting a period in front of it fixed it though! So now my first message is: ". Hi! am i speaking with {{first_name}} {{last_name}}?"
s
Hey @amir To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help me figure out what went wrong!
a
Thanks @Shubham Bajaj this issue is solved, but when i press "Mark as resolved" Discord says "The intereaction failed".
5 Views