Clearing a User's Missed Call Notification Backlog in Verity CRM

Modified on Thu, 25 Jun at 11:10 PM

Symptom

A CRM user has a backlog of missed call notifications (sometimes dating back months or years) that they cannot clear individually or in bulk from the standard interface.

Background

Verity CRM does not currently support bulk deletion of missed call notifications from the standard user interface. Users can individually disposition calls to remove them going forward, but this is not practical for clearing a large existing backlog.

Resolution Options

Option 1: Mass Mark as Read (Immediate Cleanup)

Portico Support can mass-mark all missed call notifications as read on the backend. This clears the visual notification count without permanently deleting the underlying records.

Action: Contact Portico Support and request a notification read-clear for the affected user.

Option 2: Bulk Delete via Temporary Permission Elevation

If full deletion of notification records is needed:

  1. Contact Portico Support and request a temporary permission elevation for the user to enable bulk delete
  2. Have the user use the bulk delete feature to clear old notifications
  3. Notify Portico Support to revert the user's permissions to their normal level once complete

Option 3: Backend Data Correction Request (Engineering)

For very large backlogs, or where the above options are not practical, Portico Support can submit a data correction request to engineering to clear the notification records directly. This is an escalated path and may take additional time.

Going Forward

Users should regularly manage their missed call notification inbox to prevent future buildup. Calls can be dispositioned individually to keep the list current.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article