Renewal settings, client setup queue, manager setup page, combobox grouping, nav updates
This commit is contained in:
parent
d109a5f73a
commit
4315f704c7
29 changed files with 2588 additions and 65 deletions
8
ondeck/docs/Renewal Groups.md
Normal file
8
ondeck/docs/Renewal Groups.md
Normal file
|
|
@ -0,0 +1,8 @@
|
|||
# Purpose
|
||||
They are used to group together insurance policies with similar renewal dates or common tasks. They can be assigned by the system, manager, or end user.
|
||||
|
||||
## Default Renewal Group and Client Renewal Date
|
||||
The renewal date field for this renewal group will be the `renewalDate` for the client. If the client doesn't have any renewal groups and only has a single policy then the renewal date of that policy will be used. If neither of these scenario's fit then the client does not have a renewal date and one must be assigned by a team member
|
||||
|
||||
## New Client
|
||||
When a client first appears in the system (they would've been synced from AMS360) they will need to be assigned a `renewalDate` and a `claimsAdvocate`. At this time the manager/admin will be able to view any policies (their respective renewal dates) - and see system generated recommendations for Renewal Group and Renewal Date. They can accept the recommendations and assign an advocate, or modify any part. This would include not making a renewal group, manually setting a Renewal Date - or adding any client, or policy specific notes.
|
||||
Loading…
Add table
Add a link
Reference in a new issue