We've swapped to dynamic first message recently but in the time I've been testing the agents, it looks like the first few words almost always get cut off so the first impression left on the user is fragmented. E.g. if the first message is "one two three four five," more often than not you get "three four five" or even "five" as the first message. Not sure if this has been surfaced but I think this is important to look at because first impression for these agents are critical. We've developed a workaround for this but ideally this is fixed (if this isn't intentional and/or fixable). E.g. You can only hear AI Agent saying the fifth word of the first message: 1f1f6c9a-4c83-4914-8e1d-7424bf88a709 You can only hear AI agent saying the third to fifth word of the first message: 6e044fb6-3518-450f-8daf-ea6d6b02ef03

@george.l Thank you for bringing this to our attention. It's crucial that the first message is delivered completely and clearly, as it sets the tone for the user's experience. The issue you've described with the first few words being cut off is certainly not intentional and should be addressed promptly. To assist you further, could you please provide more details about the current configuration for the first message mode? Specifically, is the

assistant-speaks-first

mode enabled, or are you using the

assistant-waits-for-user

mode? Additionally, is the recording feature currently enabled? With this information, I can offer more targeted advice or escalate the issue to our technical team for a deeper investigation.

4666a22b-2c1b-42e9-951b-ab241a374b83 For this call I do hear one two three four five https://think-bullish.s3.us-east-2.amazonaws.com/6e044fb6-3518-450f-8daf-ea6d6b02ef03-1733230980031-886477de-47f6-46bd-84fc-ae48ea93e615-mono.wav Similar for the first call id. @george.l can you look into the call ids?