Bug Fix

Call List Attempt Counts Now Update Correctly

What’s New

Call list entries only ever recorded an attempt when an agent pressed “Next”. Anyone who placed a call and then navigated away left the contact showing 0 attempts and a “pending” status, even though the call was logged on the contact record. Agents then re-dialed people they had already called, and the max-attempts cap never tripped for them.

  • Placing a call from a Call List records the attempt immediately.
  • When the call ends, the entry updates itself — status and disposition follow the real outcome, whether or not the agent presses Next.
  • Pressing Next afterwards still applies the disposition the agent chose.
  • An attempt is counted once per call, no matter which of those steps happens first.

Bug Fixes

  • Fixed call list entries staying on 0 attempts and “pending” after a call was placed and the agent left without advancing.
  • Fixed “No Answer” and “Busy” dispositions being recorded as completed instead of feeding into the retry/max-attempts logic. As a result, some entries that previously showed as completed may now show as retry (pending another attempt) — this reflects the actual call outcome more accurately.
  • A contact re-queued after a no-answer now keeps the disposition that sent it back into the queue, instead of losing it.