Who approves
Set per request type. Policy checks are usually set to need an account manager.
A carrier's policy document compared with your own record, with every difference flagged for a person and nothing overwritten.
An email with a carrier policy or endorsement PDF attached, or a request to check that a policy was issued as quoted.
Routed, timed and tracked until it is done
The same order every time, recorded on the task as it runs. Anything unclear stops for a person instead of being guessed.
The request is told apart from other policy work, and the customer and policy are found from the email.
The text of each PDF attachment is read. A document that cannot be read is flagged, not guessed at.
Insured name, policy number, carrier, effective date and expiration date are compared with what your record says. Names are compared loosely, so "Hartford" and "The Hartford Insurance Group" are not flagged as different.
A value the document does not state is shown as not stated, never as a mismatch. A real difference is shown side by side, and neither value is changed.
Your team corrects the AMS or goes back to the carrier. Shlix records the decision.
An account manager approves where required, and the task is closed on the record.
Set per request type. Policy checks are usually set to need an account manager.
What each document said, what your record said, the result of each comparison and who resolved it are kept on the task.
Comparing premium, limits, named insured detail and mortgagees is planned. Premium needs your agency system to supply it, so it is not compared today.
No. It compares and flags. A person decides which side is right, and neither is changed automatically.
Not yet. Today it compares five identifying fields. Limits, forms and endorsements are checked by your team.