Wawanesa Home product is currently only available to a limited number of brokerages, in certain provinces.
There are some differences in the processes that occur in the platform and the workflows that you may follow, so here is a summary here:
Coverage |
Coverage Details/Limits |
Special Homeowners |
Guaranteed replacement cost (GRC) Single Inclusive Limit |
Building Bylaw Coverage |
$30,000 Limit |
Identity Fraud |
$10,000 limit |
Personal Cyber Coverage |
$25,000 limit |
Service Line Coverage |
$10,000 limit |
Home Equipment Breakdown |
$50,000 limit |
Sewer backup coverage |
Full policy Limit (Unless restricted due to risk territory) |
Fire Department Charges |
$10,000 limit |
Water Defense Coverage |
Optional – max limit dependent on risk territory |
Personal Liability Coverage |
$1,000,000 |
Liability - $1 or $2 million
Deductible - $1K, $2.5K and $5K
Water Defence – Add or Decline – policy limit (based on Eligibility)
Sewer Backup included if eligible
Home Equipment - $50K or Decline
Personal Cyber – $25K or Decline
Scheduled items
- Jewellery up to $9,900/item ($250 deductible)
- Bikes up to $9,900 ($250 deductible)
- Watercraft – not available
- Total schedule - $100K
- Policy Change is not available – Policy Change should be processed using Blue Pass.
- Broker can proceed thru Policy Change like usual though as system will put activity with notes for Pending change and put policy in Pending change status awaiting download of change.
- Activity is left open for broker to follow up on Policy Change update, once received and reviewed then broker to close activity.
- No changes can be made to policy while in Pending state.
- Changes made outside of Bond (in BluePass or by Wawanesa directly) to policies issued in Nude WILL be updated in Bond via View Policy including Cancellations.
- Policies NOT initiated on the Nude Platform will not be available in the Nude platform.
- Customers in pocket will receive a message to tell them to contact their broker. They will not be able to perform Policy Change there.
- Cancellations are mostly short rate (AFI updated) – however flat cancel allowed.
- Policy Change emails will likely only be received upon the effective date of the change (when the wording is available) so will not be received ‘immediately’.
- Registered letter process works like this:
- When bond user selects Registered letter icon, an email is sent to Wawanesa.
- When Wawanesa process the Registered letter on their end, the cancellation is sent through to the platform and updates Bond (including Policy Documents, Pending Cancellation date updates, time on risk shows in payments section).
- Then the Bond user must manually attach the Registered letter to bond upon receipt.
- Selecting Reinstate will send email request to Wawanesa.
- When Wawanesa processes reinstatement on their end Bond will be updated (including View Policy).
- When a claim is submitted through pocket or bond, the claim report email is sent directly to Wawanesa.
- There is no broker intervention in this process, at this time. All reports go direct.
- Although the customer is directed to Pocket immediately, they can only see their dec under View Policy. There is a delay on the Wording and Application to appear in bond or pocket.
- There are Hourly policy sync calls, when a renewal is captured and this is created in the system. The customer renewal email is sent approximately 21 days prior to expiry date.
- The renewal dec page and wording are attached to the policy in bond (the renewal activity).
- The Renewal version is available under View Policy icon as 'Renewal'.
- System generated activities will be provided if a renewal fails to download, like here:
Occasionally, Wawanesa's system that interfaces with us will experience downtime during the day, which could interrupt the renewal process. It is advisable to allow a grace period until the following day. This period permits the system to attempt a subsequent operation and resolve any pending processes. It is anticipated that the renewal documentation will be processed during this interval.
If the renewal remains unprocessed after the aforementioned period, a support request should be logged.
Here is an example of the renewal failure activity: