Who approves
Configurable per agency: require an approver, or let the person who prepared the card send it.
Workflows / Auto ID cards
Auto ID cards
Insurance ID cards drafted from the policy record and the vehicles in the request.
- 01Recognize the request
- 02Match the customer and policy
- 03Read the vehicles
- 04Draft the card
- 05Approve and send
What arrivesNew request
A customer or carrier asking for a new or replacement auto ID card, often listing vehicles by year, make and VIN.
Drafted, checked and approved before it goes out
[ Step by step ]
How Shlix handles auto ID cards.
The same order every time, recorded on the task as it runs. Anything unclear stops for a person instead of being guessed.
- From the request
- From your AMS
- Drafted and checked
- Done and on record
Recognize the request
Told apart from certificate and endorsement requests by what it asks for.
Match the customer and policy
By policy number, sender or name, with the match method recorded.
Read the vehicles
Year, make and VIN are taken as written; nothing is invented when they are missing.
Draft the card
Built from the policy record and checked before it is shown to anyone.
Approve and send
A person approves where your rules say so, and the PDF goes to the requester in the same thread.
[ Control ]
Who signs off, and what stays on record.
What is recorded
The card, the checks and who sent it are on the task and in the audit trail.
What if a VIN is missing?+
It is left blank and flagged. Shlix does not guess a vehicle.
[ Read next ]
[ Other workflows ]