This article gives an explanation of the use of Note Types and the generation of Email Notifications when a note is added to a Service Request.
Note types are configurable and access is controlled by setting the different permissions. There are 3 types of notes
- User note
- Customer note
- Guest note
Customers can only view or add 'Customer' notes.
Users can only view or add 'User' Notes'.
A 'User' can add a note which is then visible by a 'Customer' if the access level is defined as both 'Customer' and 'User'.
By using the ‘Access Level’ in the note type, this will define the result when sending notifications on a note being added to a Service Request.
If a customer adds a note, the following notifications will be sent.
- Email the person who submitted the service request
- Email the account for the organization (myorganisation.gov.uk)
- Email the person who submitted the note.
If a user adds a note, the following notifications will be sent.
- Email the owner of the service request (if present)
- Email the account for the organization (myorganisation.gov.uk)
- Email the person who submitted the note.
Note
If both access levels are specified in the note type i.e. Customer & User, the system will send notifications for both scenarios.
Things to consider
If the notification is set at the system level to send note email (Service request note mail), this will automatically send the notification as per the logic above. If this is unticked on your system, you will need to configure Rules to send the appropriate notification(s).
You can check how this is configured using the notification page, Administration > Email > Notifications
Customer notes - will display on both the customer portal and administration portal (if appropriate access is given to 'Users')
User notes - these will display on the administration portal only,
If a user note is locked down to specific access roles, only those users with the appropriate access role can view the note in the Admin Portal.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article