Who approves
Set by your agency; renewals are often reviewed by the account manager.
Workflows / Renewals
Renewals
Renewal requests recognized and routed with their own follow-up rhythm, so none sit unanswered.
- 01Recognize and match
- 02Route to the account owner
- 03Give it its own rhythm
- 04Track the conversation
- 05Finish on the record
What arrivesNew request
A renewal offer or request from a carrier, a customer or an account manager.
Routed, timed and tracked until it is done
[ Step by step ]
How Shlix handles renewals.
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
- Done and on record
Recognize and match
The renewal, the customer and the policy it belongs to.
Route to the account owner
Renewal work goes to the person who handles that account.
Give it its own rhythm
Renewals follow up on their own interval (five business days by default) rather than the same-day rhythm of a certificate.
Track the conversation
Waiting on the customer or carrier is recorded, and the clock pauses.
Finish on the record
Approval where required, the reply, and the email filed.
[ Control ]
Who signs off, and what stays on record.
What is recorded
Every step and owner is on the task, and reports show renewals by person and by age.
A renewal calendar that raises work ahead of expiry is planned. Today renewals start when a request arrives.
Does it start renewals before the carrier notice?+
Not yet. Today a renewal task starts from an email; a calendar-driven start is planned.
[ Read next ]
[ Other workflows ]