What's new, 21 October 2026: A customer who sends several messages before the bot's first reply no longer gets the opening sequence of a Chat Flow twice
WASync · Developers

The call duration in the CRM is wrong; it includes the ringing time.

It does not any more: the timer starts when the call is answered, and a missed call is logged with a duration of zero.

The logged duration is the talk time only: the timer starts when the call is answered (confirmed by Meta or by the first audio packet), not when it starts ringing. A call that nobody answered is logged as missed with a duration of zero, so the reports count real conversations.

Was this page helpful?

On this page