Let the policy number do the routing.
A licensed agent is the most expensive minute in the building. Spending it on reading a renewal date off a screen is a choice, and it is one the flow can make differently.
Insurance and financial services · 9 steps
Most inbound insurance calls open the same way: who are you, what is your policy number, and what is it doing. Three of those answers are in a system the caller cannot reach and an agent can, so the agent becomes the interface to a database.
That is fine at low volume and ruinous at renewal season, when the queue fills with people who wanted a date.
Step by step, with the node each one uses.
- 01
Recognise the caller if you can
If Existing LeadA known number skips the identification step entirely, which is the part callers hate most.
- 02
Take the policy number
Capture DigitsKeyed in from their documents. Set the minimum length to the real length of a policy number so a fumbled entry re-prompts instead of failing a lookup.
- 03
Look the policy up
Trigger WebhookSends the captured number to your policy system and captures the status, the renewal date and the premium into variables.
- 04
Branch on the status
Match Webhook VariableActive, lapsed, in claim and not found are four different conversations, and only two of them need a licensed person.
- 05
Read back what was found
Playback AudioThe status and the date, spoken with the captured variables. For a large share of callers this is the whole call and they hang up satisfied.
- 06
Offer the next step
Route to IVRRenew, make a change, speak to somebody. The caller chooses, rather than everyone landing in the same queue.
- 07
Send regulated conversations to licensed staff
Route to RoleRouting by role rather than by team, so a call needing a licensed agent cannot land with somebody who is not.
- 08
Mark what the call was about
Manage TagsRenewal, claim, change of details. The reporting writes itself and the follow-up sequence knows which one to send.
- 09
Send the follow-up automatically
Add to Email SequencesA renewal quote or a change form, triggered by the branch the caller took rather than by an agent remembering.
The variables.
Captured mid-call and readable by every later node, including inside a spoken prompt and inside a webhook body.
${POLICY_NO}What the caller keyed in${POLICY_STATUS}Active, lapsed, in claim, used to branch${RENEWAL_DATE}Spoken back to the caller${PREMIUM}Spoken back where the branch calls for itThe calls that were only ever a lookup end without an agent. The ones that reach a licensed agent arrive with the policy already identified and the reason already known.
Routing by role rather than by team matters here specifically. It is the difference between a routing preference and a control you can point at.
- Set the minimum digit length to the real length of a policy number. Otherwise a caller who mis-keys one digit gets a confident answer about somebody else's policy.
- Give the lookup a not-found branch that routes to a person. A caller reading a number off a renewal letter who is told it does not exist will not try again, they will complain.
Book a demo
We will build this one on your numbers.
Half an hour. Bring the awkward case rather than the easy one, and we will tell you if it does not fit.
14-day trial · no card · migration included