Collections - Flag as Sent to Collections

The "Flag as Sent to Collections"Collections feature isallows usedadministrators to manually update a violation's status to bypass thestandard standardautomated notification processesworkflows, such as the Notice of Impending Charge (NIC) and Certificate of Request for aCourt violation(CRC) processes. Its primary purpose is to efficiently process violations that isare being handled externally by a collections agency.agency Thisor isto usefulaccommodate ifusers a person wantsrequesting to go directly to trialtrial. insteadThis ofarticle waitingis intended for OPS-COM administrators handling violation management and going through the entire process.  Once this flag is enabled, the violation will bypass the existing NIC (Notice of Impending Charge) letter and the CRC (Certificate of Request for Court) process.collections.

Setup &and Configuration

YouTo use this feature, the specific administrative role must have the Managecorrect Collectionspermissions permission to do this. This permission can be added to your profileenabled by youra Primary Admin. 

To enable this permission:

1. Go to

   Hover over System Configuration, thenclick Admin Management, andthen Manage Roles.

2. Locate the Rolespecific role you want to edit and click the Permissions button.

3. Click the Violations tabtab.

   and
enable

4. Enable the Manage Collections permission.checkbox.

5. Click the Save Settings. button to apply the changes.

---

Using this Feature

Once the correct permissions are assigned, administrators can manually apply this flag to individual tickets from the search screen.

1. Go to

   Hover over Violations and click Search.Search.

2. Search for the specific violation you wantwish to flag.

3. Click the specific ticket # link in the results to open the Violation Information page.

4. Select

   Click the Action dropdrop-down downmenu and clickchoose Flag as Sent to Collections.

5. Click Ok.
   the Ok button to confirm the status change.

---

Best Practices &and Considerations

One-Time

• AdminsProcess: should use the existing Violations Notes feature to add detailed notes to the violation. This could include the customer's request and any necessary details explaining why the ticket was placed in the Collections state.

• Admins with the appropriate permissions will still be able to pay or cancel the violation as necessary.

• Once a violation has successfully gone through the collections processworkflow, once,the system permanently marks it is marked as suchsuch. andA ticket cannot re-enter the Collectionscollections process again.a second time.

  • Audit Trails: Always use the Violations Notes feature to add detailed comments to the violation record. Documenting the user's request or the specific reason the ticket was manually escalated to collections ensures a clear, reliable administrative history.

  • Administrative Overrides: Administrators with the appropriate permissions will still retain the ability to pay or cancel the violation within the system as necessary, even after it has been formally flagged for collections.