25 requests,
handled end to end.
Every one of these starts with a client asking and ends with a form submitted to the carrier. What happens in between is the part Casewave does.
The ones that need your judgment aren't automated. They're routed to you, which is a different thing than not being supported.
WHAT'S AUTOMATED
The full list
Collected, filled, and prepared for your signature, without you doing the middle.
BENEFICIARY
6- Primary beneficiary change
- Contingent beneficiary change
- Add or remove a beneficiary
- Beneficiary allocation change
- Trust named as beneficiary
- Minor beneficiary or custodian designation
CLIENT INFORMATION
3- Address change
- Phone and email update
- Legal name change
PAYMENT AND BILLING
9- Bank account or EFT change
- Draft date change
- Payment mode change
- Credit or debit card update
- Payment method change
- One-time or catch-up premium payment
- Failed draft resolution
- Premium payer change
- Reinstatement after lapse
OWNERSHIP
5- Ownership change or transfer
- Add or remove an owner
- Collateral assignment
- Absolute assignment
- Transfer of ownership to a trust
CASH VALUE
2- Policy loan request
- Loan repayment
DOCUMENTS AND STATUS
3- Policy status inquiry
- Duplicate policy or certificate request
- In-force illustration request
Available on the carriers you select at onboarding.
HOW IT STARTS
Two ways in
Your client doesn't need to know what the form is called.
PICK IT
Choose from the list
A client opens the app, taps request servicing, and selects what they need. Casey takes it from there.
SAY IT
Just describe it
Or they tell Casey what's going on in their own words, like ‘I switched banks’ or ‘my daughter got married,’ and Casey works out which request that is.
THE ONES THAT NEED YOU
Not everything should be automatic
Some requests need an agent, not a form.
A term conversion, a face amount change, a surrender, a rating reconsideration. These aren't paperwork problems. They're conversations, with real consequences for coverage and cost, and a client shouldn't complete one by filling in fields.
So they don't dead-end. They route.
Your client can start any request in the app, including the ones Casewave doesn't automate. Casey recognizes what it is and routes it based on type, either putting time on your calendar or bringing it to you in chat so you can move it forward yourself.
The client gets an answer instead of silence. You get a conversation you would have wanted to have anyway.
Requests that route to you include face amount changes, term conversions, riders, surrenders, and rating reconsiderations.
THE SEQUENCE
What happens after they ask
The same five steps, whichever request it is.
- 01
Casey identifies it
She works out which request this is and what that carrier requires for it.
- 02
She collects
Names, relationships, dates, allocations, account details, all gathered from the client, not from you.
- 03
The form gets filled
The correct carrier form is pre-filled from the client record and what Casey collected.
- 04
You sign
The finished packet comes to you for review and e-signature through your own DocuSign.
- 05
It gets submitted
Casewave sends it to the carrier and keeps the whole thread on the client's record.
QUESTIONS
Common questions
What agents ask about the list.
Does this work on every carrier?
It works on the carriers you select during onboarding, which is where Casewave loads their servicing documents and portal links. More than 500 carriers are supported.
What about requests that aren't on this list?
Your client can still start them in the app. Casey routes those to you, either by scheduling time on your calendar or bringing it to you in chat, instead of leaving the client with nothing.
Will Casey ask my client for their bank account number?
No. Account numbers, social security numbers, and driver's license numbers are collected through DocuSign, not in a chat with Casey.
Can I start a request myself instead of waiting on the client?
Yes. You can open any request from a client's profile in your own account and run it the same way.
What about death claims?
Claims are not currently part of the automated request list.