Admin Set-up 7: Creating Alerts for Request Diversion

How do I direct a requester to information already publicly available or outside of the portal?

You can set up alerts to display instructions based on a particular word or phrase that a requester types in their request. This can help route requesters to the information they’re looking for before they make their request, saving time for everyone. This information might be located on a page that is already on your website or the website for a department that processes public records requests outside of the NextRequest portal. Once an alert has been created, you can track how often it is triggered by requesters.

Watch the video or read on below for instructions on how to create alerts


Creating an Alert

  1. Click the ADMIN link in the header
  2. Click the Alerts link in the sub-header
  3. Click the Create Alert button
  4. Enter the words and/or phrases in the Keywords box that you would like to trigger the alert, separated by a pipe: | (usually found on the same key as \ above the return key)
    • Examples: to trigger an alert for the words “birth,” “death,” and “certificate”, enter ‘birth|death|certificate’. Try to use the singular or stem version of a word so that it will be triggered by different variations. For example if you want to have an alert triggered for the words 'license', 'licenses' and 'licensing', you can put in 'license' as the alert keyword.
  5. Enter text of the alert. This text will display below the request description if the associated keyword is detected
  6. Click the SAVE button


Editing an Alert

To edit an existing Alert, locate it in the Alerts list, then click the Edit icon (pencil_icon_white_background.png) inline on the right. Make any edits you want to the Alert keyword(s) or text, then click the SAVE button.


Deactivating and Reactivating an Alert

To deactivate an existing Alert, locate it in the Alerts list, click the Deactivate button inline on the right, then click OK to confirm. Once an alert has been deactivated it will not longer be triggered when a requester types the keyword.