Claims intake is among the most outsourceable work in insurance and among the easiest to get badly wrong. The task itself is straightforward. The boundary around it is not, and that boundary is where liability lives.
This guide sets out what an outsourced first notice of loss programme does, what it must never do, and how to plan capacity for the weeks that decide an insurer's reputation.
What our agents handle, and what stays with you
An agent taking a first notice of loss records what happened, when, where, who was involved, what the immediate situation is, and how the policyholder can be reached. They confirm the policy number, open the claim in your system, explain what happens next, and set an expectation for who will make contact, using the wording you have approved.
- Our agents take first notice of loss calls and open the claim record to your prescribed minimum.
- Our agents handle claim status calls: where the claim is, what is outstanding, and what the policyholder needs to send.
- Our agents capture and route requests that need an adjuster, a supervisor, or a specialist.
- Adjusting, reserving, and every coverage decision stay with your licensed and authorised staff.
- Selling or advising on cover stays with people who hold the required state licence, because state licensing is required to sell insurance.
Why the boundary is a liability control
That last line is not caution for its own sake. An agent who answers a coverage question on an intake call, however well meant, can bind an insurer in ways nobody intended. The intake script is not a service document. It is a liability control, and our agents are trained to treat it as one.
The boundary also protects the agent. A clear rule that coverage questions are always escalated means nobody on the intake line is ever put in the position of guessing under pressure from a distressed caller. The approved phrase is some version of: your claim has been opened, an adjuster will review it, and here is how you will hear from us. Anything beyond that is escalated, not answered.
Scripts are yours to approve. During onboarding, the wording our agents use for opening a claim, setting expectations, and declining to answer coverage questions is drafted against your process and signed off by whoever owns compliance on your side. When your process or your policy wording changes, the script changes with it, and agents are retrained before the new version goes live.
The intake script is not a service document. It is a liability control.
Capture everything, promise nothing
The two halves of that sentence protect different things. Capture everything protects the claim. Promise nothing protects the insurer.
A complete first notice shortens the whole claim. A thin one generates callbacks, delays assignment, and frustrates a policyholder who has already had a bad day. Define a prescribed minimum for the record and enforce it through the script, so the adjuster who picks up the file has what they need to act on the first read. The minimum differs by product line: a motor claim needs vehicle, location, third parties, and injuries; a property claim needs the nature of the damage, whether the home is habitable, and whether emergency mitigation has started. Write each one down.
Promise nothing means the agent does not indicate whether the loss is covered, does not estimate what will be paid, and does not describe a timeline you have not committed to. It also means the agent does not advise on what the policyholder should do beyond the safety and mitigation guidance you have approved for the script.
Distressed callers need a different script
Someone reporting a house fire or a serious accident is not in a transactional frame of mind. Scripts written for routine service handle these badly, and the failure shows up in complaints rather than in handle time. Acknowledgement, pacing, and clear next steps matter more than efficiency here.
A practical check: read your intake script aloud imagining the caller has just watched their home flood. If it sounds like a form, it needs rewriting. The information still has to be captured, but the order and the tone change. Safety first, then the immediate situation, then the details that can wait. Our agents are trained on both the routine version and the distressed version, and on recognising within the first exchange which one they are on.
Status contact is the second wave
Once claims are filed, the queue fills with people asking where theirs has got to. This is high-volume, low-complexity, and highly outsourceable, and handling it well removes a large distraction from adjusters who should be adjusting.
It depends on one thing: agents can see the claim status in your system, and the status is meaningful. If your claims platform shows a stage and the outstanding items, an agent can tell the policyholder exactly what is needed from them and log the contact. If it shows only 'open', the agent transfers the call to an adjuster, and you have paid for a call that did not need to happen. Read access to claim status, with clear stage definitions, is the systems item worth pushing hardest on at launch.
Status calls are also where a delayed claim becomes a complaint. An agent who can see that a claim has been waiting on an inspection for longer than your standard can say so honestly, log the concern, and route it to the adjuster's team as a follow-up rather than a transfer. That is a small script decision with a large effect on how the policyholder remembers the claim. Some insurers also use the same agents for outbound status updates at agreed milestones, which removes a share of the inbound queue before it forms.
Catastrophe weeks define the year
Claim volume is not evenly distributed. A single storm can generate more contact in a few days than the preceding quarter, and staffing to an annual average guarantees failure in exactly the week that determines your reputation. Plan to a surge floor instead, and accept the cost of capacity you will not always use.
Catastrophe intake is also different in kind. The same event produces thousands of similar claims, the policyholder may have lost documents, and the adjuster assignment queue is already deep. A catastrophe script captures less per call and captures it faster, with a follow-up path for the details the policyholder cannot supply yet. Agree that script in advance, and agree the trigger for switching to it, so that the switch does not require a meeting in the middle of the event.
Plan the surge with the provider in the quiet season. Agree the trigger that activates catastrophe mode, the size of the trained bench that expands into it, the hours it runs, and how work is prioritised when the queue is deep. Agree the language coverage too, because a catastrophe affects everyone in an area regardless of what they speak. None of this can be arranged in the first hours of an event, and all of it can be arranged in advance.
Train in the quiet season
Agents cannot be trained into claim intake while claims are arriving. The preparation window is the quiet part of the year, and insurers who treat it that way come out of catastrophe weeks intact.
Our onboarding follows the same sequence for every programme: a call to define scope, hours, and agent numbers; a project manager who maps your intake process and prepares systems access; training against your scripts and your product lines; and a launch with quality control and reporting from the first day. For a claims programme, the mapping step covers every product line whose claims the agents will take, because each has its own prescribed minimum and its own escalation triggers. The first ninety days guide covers what a healthy launch looks like from your side.
Data handling and quality
A claim record contains personal, financial, and sometimes health information, and the policyholder is trusting you with it at a bad moment. Access for our agents is scoped to the claim and status functions in the agreed scope, through named accounts, with role-based workflows and confidentiality practices built to your requirements. Where a line of business involves protected health information, a business associate agreement and the minimum necessary principle apply, and the arrangement is confirmed with your counsel before launch rather than assumed. The broader principles are in our data security guide.
Quality is checked by listening, not by counting. A sample of intake calls is reviewed against the prescribed minimum and the promise-nothing rule, and the findings feed back into training on the reporting rhythm agreed at the start. The number worth watching most is the share of first notices an adjuster could act on without calling the policyholder back. Escalations are reviewed separately: how many, for what reason, and how long each waited for a licensed decision. A rising count in one category usually means a script gap rather than an agent problem.
When outsourcing intake is the wrong move
If your product lines are so varied that no script can hold them, start with one line and expand. If your claims system cannot give an external agent scoped access, the programme will add a transfer step rather than removing one. If your adjusters are not available to take escalations during the hours the intake line runs, the boundary will hold but the policyholder will wait, and that is a different failure. And if what you actually want is someone to make coverage decisions faster, that is not intake work and cannot be handed to unlicensed agents.
The insurance outsourcing overview covers policy servicing alongside claims, and back office outsourcing covers the document processing that follows a well-captured first notice.