Who approves
Usually needs an account manager, and every decision is recorded.
Workflows / Cancellations and non-pay
Cancellations and non-pay
Cancellation requests and notices kept from slipping, with the chase clock running while you wait.
- 01Recognize it as urgent work
- 02Route and time it
- 03Mark what you are waiting on
- 04Escalate when it goes quiet
- 05Close it on the record
What arrivesNew request
A customer asking to cancel, or a carrier notice of cancellation or non-payment.
Routed, timed and tracked until it is done
[ Step by step ]
How Shlix handles cancellations and non-pay.
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 it as urgent work
Cancellations are not left in a shared inbox waiting to be noticed.
Route and time it
To the right person, with a tight due time and Overdue flags.
Mark what you are waiting on
A customer, a carrier or an underwriter. The clock pauses while you wait and a follow-up is scheduled.
Escalate when it goes quiet
After the agreed chases, the task is raised to the owner rather than forgotten.
Close it on the record
Approval where required, a reply, and the email filed as complete.
[ Control ]
Who signs off, and what stays on record.
What is recorded
The full history, including every chase and who owned the task at each point.
Sending the customer reminder emails automatically, and stopping them when payment is recorded, is planned. Today your team sends the reminders; Shlix keeps the schedule.
[ Questions ]
About cancellations and non-pay.
More in the how it works walk-through and the glossary.
Will Shlix email my customers about late payments?+
Not yet. It tracks the request and schedules the follow-up for your team. Automatic reminders are planned and will always be owner-approved.
[ Read next ]
[ Other workflows ]