The most expensive call in your agency is the one you already answered
Your service team handles dozens of calls a day. Someone needs an ID card for the new car. Someone wants to know why the payment changed. Someone bought a boat and wants to know if it is covered. Every one of those calls ends the same way: the request gets handled, the customer says thanks, the line goes dead.
Now look at what was on the other end. A household that has been with you for years and holds one policy. A new car that means a new driver or a new commute. A boat with no coverage on it. A payment question from a customer who is comparing numbers because a neighbor mentioned a lower rate. Every one of those was a coverage conversation the customer opened for you, and your office closed it.
You cannot see this on any report. The ticket count says the team is productive. The retention number says the book is fine. The policies-per-household number says otherwise, and by the time you notice it the household with one policy has already been quoted by someone who asked about the house.
Why it feels like a pitch, and why that is a training problem
Ask a service rep or a producer why they did not bring up the house on the ID card call and you get the same answer. "They called about a card. It felt pushy." That is an honest answer and it points at the real problem. Nobody gave them a way to ask that does not sound like selling.
The customer does not experience a coverage question as a pitch when it is connected to what they called about. "You mentioned the new car is for your son. Is he going to be driving to school? Let me make sure he is listed right." That is service. A cold offer to quote the home at the end of a card request is a pitch. The words are the difference, and words can be trained.
The pitch feeling also comes from asking cold. A rep who has never said the question out loud before will say it badly on the first live call, hear the awkward pause, and never say it again. 84% of what reps learn in training is gone within 90 days (Sales Performance International). A sentence said once at a meeting is gone by Friday.
The one-question review
Do not train a full review on every service call. Train one question, tied to the reason for the call. The structure is: handle the request completely, confirm it is handled, then ask one question about what changed. "Anything else change since this was set up? New car, new driver, anyone move in or out, any work on the house?" Listen. If something changed, offer to look at it. If nothing changed, say so and get off the phone.
Write the question for each common call type. The ID card call gets a question about who drives the car. The billing call gets a question about whether the household is carrying anything the agency does not know about, because a bundle is the honest answer to a payment question. The mortgagee change gets a question about the roof and the renovation. Five or six versions. Your words, your carriers' language.
Then the handoff to a producer, if service takes the call. "Let me have Dana call you tomorrow at ten to walk through that." A named person and a time, not "someone will reach out."
- Handle the request completely and confirm it
- Ask one question tied to the reason for the call
- If something changed, book a named producer at a set time
- If nothing changed, say so and end the call
Practice it until it sounds like service
The question has to be said out loud dozens of times before it stops sounding like a script. Run it against an AI customer who called about a billing question and answers the coverage question with "no, just the card please." By text or live voice, five personas plus custom, three difficulty levels. Each run is scored in about 60 seconds on script adherence, objection handling, close attempt, energy and tone, and follow-up setup, 20 points each, with a coach's note. A 70 clears. Three under 60 in a row open a manager enforcement action.
Ten minutes a day for two weeks and the question is automatic. It gets asked on the real ID card call because it was asked on fifty practice calls first. In the Sales Academy inside Revenue OS, month three of the 90-day plan is ticket and pricing, which is where the second-policy conversation lives, but the one-question review can start on day one because it is a single sentence.
Make it a scored step, not a suggestion
A suggestion gets skipped on a busy Tuesday. A scored step does not. Add the coverage question to your written process. Then record service and sales calls with consent and score them against that process. In Revenue OS the Intel Suite transcribes and scores every real conversation on six skills, including value stacking and follow-up setup, plus your own process at 60% of the weight. If the question was not asked, the score says so, and the moment where the call should have turned is timestamped.
A call under 80 becomes a redo due 6pm the next business day against an AI customer seeded with the real customer's words. The rep practices the exact ID card call where they skipped the question. You see whether the redo happened. Over a month you see which reps ask and which reps close tickets, and you have a specific call, not a hunch, to coach from.
Only 29% of companies can see whether training changed what their reps do. The scored step is how you become one of them. Recording is initiated by your agency, you own consent including in all-party states, audio is deleted after 90 days and no voiceprints are created.
What this does to the book
Nothing about this buys a lead. The calls are already coming in. The households already trust you enough to call. All that changes is one question at the end of a call that was going to happen anyway, asked by a rep who has practiced it and knows it is scored. Multiply across every service call in a month and the policies-per-household number moves, retention moves with it, and the agency grows on a phone bill it was already paying. That is the cheapest way an agency has to break its revenue record.
The short version
- Every service call is a customer already on the phone with no shopper's guard up, and most agencies close the ticket and hang up.
- The question feels like a pitch only when it is cold; tie it to the reason for the call and it is service.
- Train one question per call type, not a full review, and write it in your words.
- Practice it daily and score real calls against the step so skipping it is visible the next morning.
Questions owners ask
How do I get service staff to cross-sell without sounding pushy?⌄
Stop calling it cross-selling and train one question tied to the reason for the call. After the request is handled, the rep asks what has changed since the policy was written: new car, new driver, work on the house. If something changed, they book a named producer at a set time. If nothing changed, they end the call. Practiced daily, it sounds like service.
Which service calls are worth a coverage question?⌄
Almost all of them, because the customer is already talking to you. ID card requests reveal new cars and drivers. Billing questions reveal a household comparing numbers, where a bundle is the honest answer. Mortgagee and address changes reveal renovations and moves. Write a version of the question for each call type your office handles most.
How do I know whether the coverage question is actually being asked?⌄
Put it in your written process, record calls with consent and score every call against that process. When the question is missing, the score drops on that step and the moment is timestamped. A weak call becomes a redo against a practice customer, and after a month you can see which reps ask and which reps only close tickets.
See how the system runs in Insurance.
Revenue OS for InsuranceYour best month ever, and the plan to beat it.
Break Your Revenue Record