The problem seems to be caused by either of two possibilities that we will address more permanently in a future release.

Call Actions that put a call in the Completed state but also require the Exec to do something, create a situation where the Exec can’t seem to do anything about it. The call is already completed, after all. In tests, the Exec can place it in a different “completed” Call Action that doesn’t require the Exec to do something and satisfy the nagging notification, but usually the Completed call goes into Archive faster than this happens. Sometimes a Completed call that is still awaiting an Exec’s precious attention will cross over into the Archive. All the same issues still apply. Once you have fixed the errant Completed Call Action, you can log out and back into the app on the mobile device and that should halt all the notification. We recommend that you not use the Completed Call state for anything other than stuff that is truly done.

Avoid setting the “Action requires Exec to so something” switch to “Yes” on Call Actions that are in the Completed call state.

Deleting calls that are still in an active state is a bad idea. We didn’t really intend this as a way to end things for a call, so we’ve noticed that there are some unpredictable results – especially if that call had a notification to it. Logging out of the mobile app and back in can clear these. If that doesn’t work, you can try deleting the app and then reinstalling from the App Store or Play Store. If that doesn’t work, you have the problem described in the first bullet. We recommend that you avoid deleting calls. Just “complete” them.