I use call.timeElapsed in single assistant configs to help prevent calls from lasting too long. Basically at 240 seconds first message says "We've been on this call for a while now so let's start wrapping this up" and at 300 seconds it says something like "I'm reaching the end of my time for this call. I'll pass this on to the team to follow up." Then triggers the endCall tool. Like I mentioned it works great for single assistants, but can get it to work in squad.

Hey! I’ve worked with squad-based setups and this is a common issue. The problem is that call.timeElapsed isn’t shared consistently across assistants in a squad, so each one doesn’t reliably track the same timer. I can help you fix this by setting a centralized timer logic (or shared state) so all assistants respect the same timeout and trigger wrap-up + endCall correctly. @LongBeard

Thanks, how did you solve the centralized timer/shared state piece for squads? You used an external server-side timer or vapi based event handling? @Adam

Yes