We have heard from a number of users that they have had the experience of completing a call and then having it continue to notify the Exec on their smartphone. This can be pretty annoying to the Exec.
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. We recommend that you not use the Completed Call state for anything other than stuff that is truly done.
- 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, but that hasn’t always done the trick. We recommend that you avoid deleting calls. Just “complete” them.