Co-browsing can help reduce insurance claims portal abandonment when seeing the page reveals what is preventing a policyholder from progressing. Its value is in distinguishing problems that sound alike but need different responses.
“I can’t upload my estimate” is a contact reason, not a diagnosis. The file may exceed the portal’s size limit. An attachment category may be missing. Or the upload may have worked, while the policyholder remains unsure whether the estimate contains what the insurer requested.
The next step depends on that diagnosis: explain a requirement, escalate a portal fault or help the customer work out what evidence they still need.
Find the unresolved submission behind the exit
A session exit does not establish insurance claim abandonment. A policyholder may save a draft, return with a document or complete the claim by phone. Another may believe they submitted successfully even though the portal still holds a draft.
For operational reporting, define claims portal abandonment as a started digital claim submission with no confirmed portal receipt within a stated observation window. Count a start at the first persisted claim-specific entry or draft creation, rather than a portal visit. Choose the window around the time customers reasonably need to gather evidence and state it in the report.
Reconcile later returns and completion through other channels before interpreting the results. Report confirmed portal receipt, confirmed completion through another channel, unresolved saved drafts and unresolved exits separately. A channel switch remains digital drop-off, but it may represent a completed customer task. A saved draft may need evidence gathering rather than a rescue call.
To investigate an unresolved attempt, connect the last saved step with validation events, upload errors, submission records and the customer’s explanation. The useful question is what prevented the next action:
- Did an incident question ask for information the policyholder could not interpret or provide?
- Did the portal reject a file or require an attachment category?
- Was a control inaccessible or unresponsive?
- Was the requested document unavailable?
- Did the customer select Submit without receiving a clear result?
These are diagnostic possibilities, not interchangeable reasons to offer live assistance. A contact code such as “upload problem” needs enough detail to distinguish a file-handling rule from uncertainty about the requested evidence.
Use co-browsing to identify the visible obstacle
Co-browsing lets an advisor and customer view the relevant web journey together. Available visibility and interaction controls vary by deployment; sharing the portal does not imply access to local files, file-picker dialogs or every browser-generated error. Its value here is specific: the advisor can connect the customer’s description to the displayed page instead of asking them to reconstruct every click.
For example, imagine a property policyholder contacting support because the evidence step will not advance after they add a repair estimate. The advisor first establishes the blocked step and asks what happened after the last action. If that explanation does not identify the obstacle, the advisor offers co-browsing.
Before sharing begins, explain what the advisor will see, what actions they can take, how sensitive information will be handled and how the customer can end sharing. Base that explanation on the actual restricted-field, document-access and session-retention controls; do not assume sensitive information is masked. Offer accessible verbal assistance or another approved claims route if sharing is declined, unavailable or unsuitable. The customer should not have to accept sharing to obtain help, and co-browsing cannot replace accessible portal controls.
Resolve the displayed requirement first
On the shared portal page, the advisor sees that the estimate is listed as uploaded but a validation message asks the customer to select a document category. That changes the diagnosis. The immediate problem is neither a missing file nor a failed upload.
The advisor explains the category field. The customer selects the appropriate category and advances, retaining control of their entries and submission.
If the category correction resolves the problem and the customer understands the evidence request, no document review is needed. The customer can continue to submission.
Review the document only if the question changes
With the upload problem resolved, suppose the same policyholder asks, “The portal wants an itemized repair estimate. Does mine include that?” They can now progress through the portal but still need help understanding the evidence request. The filename alone cannot answer their question.
Where an approved document-review route is available, the advisor can ask permission to review the relevant part of the estimate with the customer. Within their authority, they can explain what the request means and point to relevant entries. For example, they might show where the estimate separates materials and labor, or explain that the document displays only a total where the request calls for a breakdown.
This is submission support. Coverage, claim approval and acceptance of the evidence remain decisions for the authorized claims process.
If information is missing, establish whether the insurer’s process allows the claim to be submitted with evidence supplied later. Otherwise, explain how to preserve progress, obtain the missing information and return. Keeping the policyholder online will not produce a revised estimate from their contractor.
Check receipt after the customer submits
Once ready, the customer reviews their entries and submits. The advisor then checks the insurer’s recorded submission status and claim reference, where available, through the existing receipt process.
If the status is pending or unclear, follow the insurer’s status-check process before advising another submission. Give the customer a clear next step and explain how they will obtain confirmation.
Choose assistance, repair or an evidence-gathering pause
The advisor’s next action should follow the obstacle, not the availability of a tool. Seeing a clear validation message may make an explanation possible; seeing the same control fail repeatedly should lead to a defect report and a workable alternative.
| What the investigation shows | Appropriate response |
| A visible field or validation message is unclear | Explain the requirement and let the customer correct the entry. Feed recurring confusion back to the content owner. |
| A file does not meet a displayed format or size rule | Explain the approved requirements and available options without asking the customer to remove necessary evidence. |
| A valid action repeatedly fails | Record the step, error and relevant technical context for escalation. Offer an approved alternative claims route where needed. |
| The customer does not have the requested information | Explain what is needed, whether it can follow later and how to save or resume the attempt. |
| The document is available but the request is unclear | Use an approved document-review route if seeing the contents will help an authorized advisor explain the requirement. |
| A control is inaccessible | Offer accessible assistance or another approved route and escalate the barrier for repair. |
| Submission status is uncertain | Check the receipt record before starting another submission. |
Recurring obstacles belong with the owner who can remove them. Engineering needs reproducible failures. The claims-process owner needs examples of evidence requests that customers cannot interpret. Content teams need labels and validation messages that repeatedly require explanation. Coverage questions should go to an appropriately qualified handler.
Measure received claims and the work that follows
Evaluate assistance against confirmed receipt and submission quality, then check whether customers need further help with the original obstacle.
Build reporting around distinct submission attempts, linking repeat sessions to the same attempt. Use the insurer’s submission record to establish receipt, with a confirmation status and reference where available. Apply the same stated observation window to comparable groups and allow it to elapse before classifying attempts as unresolved. Report confirmed other-channel completion separately.
Count an assisted attempt when a customer has started a claim submission and an advisor helps with an obstacle to progressing or submitting it. Count it once across multiple contacts, whether the customer submits, pauses to gather evidence or takes another claims route. Excluding pauses and alternative routes would overstate portal recovery.
Exclude general inquiries unrelated to a started submission and contacts solely about the status or assessment of a claim already received. Decide eligibility from the purpose of the assistance, before the outcome is known.
Use the following measures together:
- Receipt-confirmed submission rate: eligible assisted submission attempts with confirmed portal receipt within the observation window, divided by all eligible assisted submission attempts in the cohort.
- Submission-related missing-information request rate: received assisted submissions that generate at least one request to correct or supply information expected at initial submission, divided by received assisted submissions with the full follow-up period available.
- Repeat-contact rate for the original obstacle: eligible assisted submission attempts followed by at least one further contact about the same obstacle, divided by eligible assisted submission attempts with the full follow-up period available.
Define the follow-up periods and reason-coding rules. Separate avoidable submission omissions from evidence legitimately requested later during claim assessment. A later request does not automatically mean the original submission was wrong.
If reporting correctly completed submissions as a separate outcome, review receipt-confirmed submissions against the information required at initial submission. Report the number meeting those requirements divided by all receipt-confirmed submissions reviewed. State whether the review covers every received assisted submission or a sample, and describe how that sample was selected. This measures submission completeness, not claim merit; the absence of a later information request is not a substitute for review.
Break results down by obstacle type. Attachment validation, missing evidence and unclear receipt need different interventions. Assisted customers may also have harder cases, so a raw assisted-versus-unassisted comparison does not establish causal uplift. Use comparable groups or a controlled pilot when testing whether co-browsing changes outcomes.
Use recurring obstacles to improve the claims route
Assistance should leave the organization with a more precise account of why customers struggle. “Cannot upload estimate” is too broad to guide investment. A document-category label that repeatedly needs explanation belongs with the content owner; a failing attachment control belongs with engineering; an unclear evidence request belongs with the claims-process owner.
Use confirmed receipt and submission-related rework to check whether each response helps. If the same obstacle continues to require an advisor, the service is carrying a recurring cost that the portal or process owner should address. Targeted co-browsing earns its place by resolving ambiguity in the moment and making the underlying problem specific enough to remove.
