Lucity has the ability to generate automated notifications for Requests. These notifications are often based on the Problem noted on the Request record or the Supervisor assigned to oversee the work.
Any automated email notifications the system sends in relation to the Request are recorded in the Request > Tracking grid.
Users can document notifications made by phone, postal service or other methods by adding records to the Request > Notifications grid.
Automated Notifications
Agencies can configure Lucity to automatically send a number of email Notifications at different points in the lifetime of the Request.
Customer Thank You - Thanks the primary Requester for making the agency aware of the issue and provides directions for follow-up.
Customer Completed - Notifies all Requesters that the issue has been resolved.
Overdue Problem - Notifies the associated Supervisor that the Request remains open past the expected completion date.
Problem/Categorized Problem - Alerts designated users that a Request related to a particular Problem has been submitted.
Supervisor - Notifies a supervisor that he or she has been assigned to the Work Request.
Manual Notifications
The system also enables users to manually send Notifications to stakeholders.
Requester - Enables a user to send a Notification to a Requester on demand.
Auxiliary Notifications
Auxiliary notificationsare sent by other Work Request applications that perform special functions.
Citizen Portal Thank You - Thanks citizens who used the Lucity Citizen Portal application to submit a Request.
Feedback Survey - Asks Requesters to complete a Feedback Survey at the point a Request is closed.
Work Order Status Change - Notifies the assigned Supervisor that the status has changed on an assigned Work Order. Also has the ability to send the same Notification to the Requesters on the related Work Request.
Lucity can be configured to send automated Notifications to 1) thank a customer for making the agency aware of the issue; and 2) provide directions regarding follow-up.
The Customer Thank You Notification is sent to the original Requester when a user saves a new Request.
Note: The Customer Thank You Notification does not apply to Requests submitted through Lucity Web's Citizen Portal. Agencies must configure customer notifications for Citizen Portal separately.
Users have the ability to override most of the automated Work Order Notifications simply by checking the appropriate Override box on the Work Order form before saving the record. When one of the Override fields is marked, the system does NOT send the corresponding Notification.
Override Fields
Leadworker
Prevents the system from sending the Leadworker Notification for the particular Work Order.
Overdue
Prevents the system from sending the Overdue Task Notification for the particular Work Order.
Work Order Overdue Notifications can also be globally overridden by enabling the Disable Work Order Overdue Notifications item in Lucity's Work Options.
Problem
Prevents the system from sending the General Problem Notification for the particular Work Order.
Problem Notifications may also be overridden in the Work Request module.
Supervisor
Prevents the system from sending the Supervisor Notification for the particular Work Order.
Task
Prevents the system from sending the General Task Notifications for the particular Work Order.
Note:Start Date, Priority Change, Work Order Completion, and Status ChangeNotifications CANNOT be overridden.
For inquires about this request, please call 555-555-5555.
City Name - Public Works
Customer Completed Notification
The Request module can be configured to send customers an automated email Notification advising them that the issue they reported has been addressed or resolved.
These emails are sent to all Requesters associated with a Request when the Request is closed.
Open the Work > Administration > Work Flow Setup > Problems Setupmodule.
Select the desired Problem and click to open the record.
Check the Customer Completed checkbox to direct the system to send Customer Complete Notifications for Requests based on this Problem.
Click the button to save the record.
Repeat Steps 2.b - 2.d for each Problem that should send out this Notification.
Set up the system.
Go to Admin Portal > Settings > Work Options and select the Requests tab.
Find the Notification Completed option and click the Clear Notification button. A list of related Notification templates appears.
Select the desired Notification. The system is now configured to send the chosen Customer Complete Notification whenever a user saves a Request with the designated Problem(s).
Most agencies configure Lucity to automatically close a Request when the associated Work Order is closed. The system automatically triggers the Customer Complete Notification as part of that process.
However, there may be cases in which a user wishes to closes a Request that either didn't result in a Work Order or for which the Work Order remains open. The following instructions describe how to close a Request manually, thus triggering the Customer Complete Notification.
In the Work Requests module, open the desired Request record.
Confirm that the appropriate Problem is selected.
Make sure the Request has an Email address listed for the Customer/Requester.
Set the Request's Status to > 951.
Save the Request.
The system sends the Customer Complete Notification to the address listed in the Email field, as well as to the email addresses of any other Requesters added to the original Request.
Users have the ability to override most of the automated Work Order Notifications simply by checking the appropriate Override box on the Work Order form before saving the record. When one of the Override fields is marked, the system does NOT send the corresponding Notification.
Override Fields
Leadworker
Prevents the system from sending the Leadworker Notification for the particular Work Order.
Overdue
Prevents the system from sending the Overdue Task Notification for the particular Work Order.
Work Order Overdue Notifications can also be globally overridden by enabling the Disable Work Order Overdue Notifications item in Lucity's Work Options.
Problem
Prevents the system from sending the General Problem Notification for the particular Work Order.
Problem Notifications may also be overridden in the Work Request module.
Supervisor
Prevents the system from sending the Supervisor Notification for the particular Work Order.
Task
Prevents the system from sending the General Task Notifications for the particular Work Order.
Note:Start Date, Priority Change, Work Order Completion, and Status ChangeNotifications CANNOT be overridden.
Thank you again for bringing the issue to our attention. If you have any other questions about this matter, please call 555-555-5555.
City Name - Public Works
Overdue Request Notifications
Lucity can be configured to send automated Notifications to alert the Supervisor on a Request that the work is overdue. A Supervisor is assigned to a Request based on its Problem.
The Overdue Request Notification is sent to the designated Supervisor whenever a Work Request with a Problem tagged to generate the Notification remains open after the Follow-Up Date (Request Creation Date + Problem Setup Overdue Days = Request Follow-Up Date).
Open the Work > Administration > Work Flow Setup > Problems Setupmodule.
Select the desired Problem and click to open the record
In the Ovedue Days field, enter the number of days it should take for a problem of this nature to be resolved.
In the Overdue Notification field, select the Notification template you created in Step 1. This is the message a supervisor will receive if a Request that he or she is associated with is overdue.
Repeat Steps 2.b - 2.d for each Problem that you wish to generate an Overdue Notification.
Click the button to save the record.
Verify that Email addresses are supplied for all Employees considered supervisors.
Go into the Work > Administration > Work Flow Setup > Employee Setupmodule.
Click to open the desired Employee record.
Make sure the Supervisor field is checked.
Confirm that the Email field contains an accurate email address.
Repeat Steps 3.b - 3.d for all employees who serve as supervisors.
Click the button to save the record.
The system is now configured to send the Overdue Notification to the designated Supervisor whenever a Work Request with that Problem remains open after the Follow-Up Date (Request Creation Date + Problem Setup Overdue Days = Request Follow-Up Date).
Create a new Work Request or edit an existing record.
Make sure a Problem is selected on the Request.
Make sure a Supervisor is identified on the Request.
Save the Request. The system automatically calculates the Follow-upDate.
During its overnight processes, Lucity Services checks all Work Requests to determine if any have a Status that is less than 950 (indicating that the Request is open) and a Follow-upDate that is in the past (when compared to the system date).
When those criteria are met, the system checks the Problem Setup record's Overdue Notif field and triggers the Notification, if any, listed in that field. The Notification is sent to the Supervisor listed on the Work Request, as well as any recipients listed on the Notification Template.
Steps 6-7 repeat every night until the Work Request is closed (i.e., its Status> 950).
Users have the ability to override most of the automated Work RequestNotifications simply by checking the appropriate Override box on the Request form before saving the record. When one of the Override fields is marked, the system does NOT send the corresponding Notification.
Override Fields
Lucity enables agencies to automatically send email notifications to the customer who made a Request, as well as tothe employee responsible for supervising the work. The following fields, when enabled, allow a user to block such communications for a specific Request.
Override Supervisor
Prevents the system from sending the Supervisor Notification for this Request. By default, the system sends the Supervisor Notification at the point at which a user selects the Supervisor on the Request and the record is then saved.
Override Problem Notif
Prevents the system from sending the Problem Notifications for this Request. By default, the system sends the Problem Notification at the point at which a user selects the Problem on the Request and the record is then saved.
Override Overdue
Prevents the system from sending the Overdue Notification for this Request. By default, the system sends the Overdue Notification to the designated Supervisor when the current date is past the Follow-up Date.
Prevents the system from sending the Customer Thank You Notification for this Request. By default, the system sends the Customer Thank You Notification when a new Request is saved for the first time.
Override Customer Compl
Prevents the system from sending the Customer Completed Notification for this Request. By default, the system sends the Customer CompletedNotification to the Customer when the Request is closed.
Override WO Status
Prevents the system from sending the Work Order Status Notification to the requestors listed on this Request. When configured, the system will send a notification to the requestor when the related work order's status changes.
Please be aware that the following Work Request remains open beyond its scheduled date of completion:
Request: [RQ_NUMBER]
Problem: [RQ_PROB_TY]
Priority: [RQ_PRTY_TY]
Please contact the Requester to explain the delay.
Requester:
Phone Number:
Email:
You will continue to receive a daily notification until the related Work Order is closed.
Problem Notifications
A Problem Notification sends a standard message to designated people when a Work Request is created with a particular Problem. An agency can configure a Problem Notification to be sent via email or to generate a printed report.
Example:
An agency sets up a Problem Notification to automatically email Wastewater Manager Billwhen a Request is created with "Sewer Illicit Discharge Cleanup" as its designated Problem.
In some cases, the same Problem may fall under several Categories on the Request form. (For example, the Problem "Leaky Pipe" might be found under both the "Sewer"Category and the "Landscape Irrigation" Category.) If a Problem Notification is required for only one of these situations, an agency can customize the Notification to apply to aspecific Category and Problem.
In the System Configuration > Notification Setup module, click the button to create a Notification template.
Give the template a unique name using the Notification Label field (required).
In the Notification Type field (required), select the preferred notification method: 1: Email, 2: Report to Printer, or 3: Report to Default Printer.
If you selected Email:
Create a Subject line, and in the Message field, draft the body of the notification. Every Problem Notification the system sends will use this text.
Enter one or more email addresses in the Recipient List.
If desired, use the Sender Type field to designate a specific sender for the Problem Notification and provide the Sender Email Address.
If you selected Report to Printer:
Enter the printer name in the Printer field.
Enter the filename of a report from the Work Order module in the Work Report field. or Enter the filename of a report from the Work Request module in the Request Report field.
If you selected Report to Default Printer:
Enter the filename of a report from the Work Order module in the Work Report field. or Enter the filename of a report from the Work Request module in the Request Report field.
In the Notification Module field (required), select 2: Work Requests.
Step 2: Configure the Problem to send the Notification.
Open the Work > Administration > Work Flow Setup > Problem Setup module.
Click the button to expand the ProblemSetup record to which you want to add a notification.
Select the Notifications grid and click the button. A new Notification record appears.
Use the Notification Label pick-list to select the Notification you created previously. The options in this pick-list come from the General >Notification Setup module.
Click Select.
Indicate which module(s) (Requests and/or Work Orders) should trigger the Notification.
Save and close the record.
The system is now configured to send the Notifications related to that Problem to the printer and/or email addresses listed in each Notification's Recipient List.
Note: Several Problem Notifications can be set up for a single Problem.
In the Work Request module, create a new Work Request or edit an existing record.
Set the Problem on the Request.
Save the Request. The system checks the designated Problem Setup record's Notifications grid, and triggers any Notifications marked for Work Requests. The Notification is sent to all email addresses in the Notification template's Recipients List.
In the System Configuration > Notification Setup module, click the button to create a Notification template.
Give the template a unique name using the Notification Label field (required).
In the Notification Type field (required), select the preferred notification method: 1: Email, 2: Report to Printer, or 3: Report to Default Printer.
If you selected Email:
Create a Subject line, and in the Message field, draft the body of the notification. Every Problem Notification the system sends will use this text.
Enter one or more email addresses in the Recipient List.
If desired, use the Sender Type field to designate a specific sender for the Problem Notification and provide the Sender Email Address.
If you selected Report to Printer:.
Enter the printer name in the Printer field.
Enter the filename of a report from the Work Order module in the Work Report field. or Enter the filename of a report from the Work Request module in the Request Report field.
If you selected Report to Default Printer:
Enter the filename of a report from the Work Order modulein the Work Report field. or Enter the filename of a report from the Work Request module in the Request Report field.
In the Notification Module field, select 2: Work Requests.
Click the button to save the record.
Step 2: Configure the Desired Work Order Problem Setup Records
In the Work > Administration > Work Flow Setup > Problem Setup module, click the button to expand thedesired Problem record.
Select the Categories grid and click the button to expand the Category record that you would like to associate with a Problem Notification.
In the Category Notification grid, click . The Problem Category Notification form appears.
Click to select an existing Notification template (required). The options in this pick-list come from the System Configuration >Notification Setup module.
Click Select.
Indicate whether the Notification should be triggered by a Request and/or a Work Order that bears the selected Problem and Category.
Save and close the record. The selected Notification now appears in the Category Notifications grid.
Now, when a user selects this Category and Problem combination on a Request and/or Work Order, Lucity will send the designated Notifications to the email addresses listed in each Notification's Recipient List.
Note: Several Notifications can be set up for a Category associated with a particular Problem.
In the Work Request or Work Order module, create a new record or edit an existing record.
Set the Category.
Identify the Problem.
Save the record.The system checks the designated Problem Setup record's Category > Category Notificationsgrid, and triggers any Notifications marked for Work Requests associated with that Category/Problem combination. The Notification is sent to all email addresses in the Notification template's Recipients List.
In the System Configuration > Notification Setup module, click the button to create a Notification template.
Give the template a unique name using the Notification Label field (required).
In the Notification Type field (required), select the preferred notification method: 1: Email, 2: Report to Printer, or 3: Report to Default Printer.
If you selected Email:
Create a Subject line, and in the Message field, draft the body of the notification. Every Supervisor Notification the system sends will use this text.
Enter one or more email addresses in the Recipient List if desired. (This list represents people who should receive the Supervisor Notificationin addition to the Supervisor.)
If desired, use the Sender Type field to designate a specific sender for the Supervisor Notification and provide the Sender Email Address.
If you selected Report to Printer:
Enter the printer name in the Printer field.
Enter the filename of a report from the Work Order module in the Work Report field or Enter the filename of a report from the Work Request module in the Request Report field.
If you selected Report to Default Printer:
Enter the filename of a report from the Work Order module in the Work Report field. or Enter the filename of a report from the Work Request module in the Request Report field.
In the Notification Module field (required), select 2: Work Requests.
Confirm that the appropriate Employee records are tagged as Supervisors.
In the Work > Administration > Work Flow Setup > Employee Setupmodule, select the Employee you want to configure and click to open the record.
Make sure the record has the Active and Supervisor fields marked.
Make sure the Email field contains the employee's email address.
In the Supv Request Notif field, select the Notification template you created in Step 1 above.
Click the button to save the record.
Repeat Step 2for every Employee who should receive this Supervisor Notification.
Note: The same Notification template can be assigned to multiple Employees.
Every time the Employee is selected as the Supervisor on a Work Order, the system will notify him or her using the designated Supervisor Notification template.
In the Work Requests module, create a new Work Request or edit an existing record.
Set the Supervisor on the Request.
Save the Request. The system checks the supervisor's Employee record and, if the employee is Active, triggers the Notification specified in the Supv Request Notif field.
If the triggered Supervisor Notification is an email message, the message will be sent to the address listed in the Employee record's Email field. The email Supervisor Notification is also sent to any additional recipients listed on the Notification template.
Users have the ability to override most of the automated Work Order Notifications simply by checking the appropriate Override box on the Work Order form before saving the record. When one of the Override fields is marked, the system does NOT send the corresponding Notification.
Override Fields
Leadworker
Prevents the system from sending the Leadworker Notification for the particular Work Order.
Overdue
Prevents the system from sending the Overdue Task Notification for the particular Work Order.
Work Order Overdue Notifications can also be globally overridden by enabling the Disable Work Order Overdue Notifications item in Lucity's Work Options.
Problem
Prevents the system from sending the General Problem Notification for the particular Work Order.
Problem Notifications may also be overridden in the Work Request module.
Supervisor
Prevents the system from sending the Supervisor Notification for the particular Work Order.
Task
Prevents the system from sending the General Task Notifications for the particular Work Order.
Note:Start Date, Priority Change, Work Order Completion, and Status ChangeNotifications CANNOT be overridden.
Requester Notifications are emails manually sent to Requesters on a Work Request. The function requires a Notification template; however, a user can choose among multiple templates. For example, an agency might use one template to notify the requester that the Request was canceled. Another template might be used to request more details about the Problem.
Users send Requester Notifications using a toolkit available through the Request record's Requesters grid.
In the Request module, click the to expand the Request about which you want to send a Notification.
In the Requesters grid, select one or more Requester records.
Click the button and select Send Email Notification | Selected Record(s). The following pop-up appears:
Select a Notification template from the list.
Click OK. The system sends the Notification via email to the Email addresses of the selected Requesters. It also adds a record to the Request's Notifications grid.
Request Denied: City does not provide this service.
Body:
The City of NAME does not provide services related to animal control, nuisance wildlife, road kill removal or pest control. Please contact County Animal Control or a professional animal removal company for assistance.
Number: [RQ_NUMBER]
Problem: [RQ_PROB_TY]
City Name - Public Works
Citizen Portal Notifications
The Citizen Portal application sends an automated Notification to thank a customer for submitting a request.
Note, however, that the Citizen Portal Notification differs from the Customer Thank YouNotification sent using Lucity Web's Work Request module.
Lucity Web includes a Request Feedback application that agencies can use to solicit customers' opinions about the service the agency provided. The feedback request is delivered to requesters via email with a link to an online survey.
Most agencies configure Lucity to automatically close a Request when the associated Work Order is closed. The system automatically triggers the Feedback Survey Notification as part of that process.
However, there may be cases in which a user wishes to closes a Request that either didn't result in a Work Order or for which the Work Order remains open. The following instructions describe how to close a Request manually, thus triggering the Feedback Survey Notification.
In the Work Requests module, open the desired Request record.
Confirm that the appropriate Problem is selected.
Make sure the Request has an Email address listed for the Customer/Requester.
Set the Request's Status to > 951.
Save the Request. The system sends the Feedback Survey Notification to the address listed in the Email field.