Introduction: do carriers still need agents if customers can self-serve?
I have spent nearly ten years building insurance and finance products, most recently as Head of Agent Portal at Decerto, and one question comes up in almost every conversation with VP Marketing and Sales Operations leaders at mid-tier carriers: if customers can serve themselves, do we still need agents? And if our distribution is agent-led, do we still need self-service? My answer in 2026 is the same as it was five years ago. You need both. What has changed is which work belongs to each side, and how cleanly the two connect.
This piece is the operational view of an insurance self-service customer portal for US P&C carriers in the $500M-$5B GWP range: where it pays off, where it does not, which regulations shape the build, and how to design the hybrid model so policyholders, agents, and your service team all come out ahead.
Why customer self-service matters more in 2026
Customer trust in carriers is lower than most executive teams assume. PwC's 2024 US Trust Survey found that 90% of business executives believe customers highly trust their company, while only 30% of consumers say they do. In the same survey, 40% of consumers said they had stopped buying from a company because they did not trust it, and fewer executives said their companies disclose data privacy policies (32%, down from 42% a year earlier).
A portal will not fix trust on its own. What it can do is give policyholders something they can check for themselves: their own login, their own documents, their own claim status, updated when it changes.
Bain's ten-year review of insurance customer loyalty, published in April 2024, shows why the timing matters. Use of digital self-service tools has doubled or even quintupled depending on the country, and first-contact digital resolution has improved for simple transactions such as paying a bill. It has not improved for complex episodes such as claims, where customers still rely on people. Bain also reports that P&C switching rates rose over the decade as digital tools made prices more transparent and switching easier.
In my experience, this is exactly the pattern mid-tier carriers feel in their service queues. Routine work is moving to digital channels, complex work stays with the agent and the service team, and the carriers that struggle are the ones that never designed the handoff between the two. For the wider view of how customer-facing tools sit alongside producer tools, see the 2026 buyer's guide to insurance CRM and the modern agent portal; for the carrier-level operating model, see our 2026 guide to digital versus traditional insurance.
What an insurance self-service customer portal actually does
An insurance self-service customer portal is a secure web and mobile application that lets policyholders complete routine insurance tasks themselves - view coverage, pay premiums, download ID cards and certificates, file and track simple claims, and update personal data - without calling the carrier. It connects in real time to the policy administration system, billing, claims, and CRM, and it hands complex requests to an agent or service representative with the customer's context attached.
For the broader picture of digital policyholder journeys, see how digital insurance improves the policyholder experience. These are the insurance customer portal features that matter in practice:
Policy lifecycle management. View policies and coverage, request endorsements within defined limits, manage payment methods and autopay, and see renewal terms. Every one of these depends on live data from the policy administration system at the core of the carrier's stack; a portal that reads an overnight batch shows the customer yesterday's policy.
Claims initiation and status. File first notice of loss (FNOL) for simple claims, upload photos and documents, follow claim status, and message the adjuster. Claim status and automated triage connect to the claims side of the stack, which Decerto covers with ClaimsAI for claims processing.
Document access. Policy documents, ID cards, certificates of insurance, declarations pages, and billing statements, all downloadable on demand with version history.
Communications. Inbound from the carrier (renewal notices, claim updates, marketing) and outbound from the customer (questions, change requests, complaints), with consent status stored per channel.
Identity and security. Multi-factor authentication, session management, and a full audit trail. The portal touches personal, financial, and beneficiary data, so the same bar applies as for producers; see security and compliance in insurance agent portals for the control-level view.
What I push back on when carriers plan the build: a "self-service portal" that is really a static FAQ with a contact form. Gartner's research is blunt on this point. In its 2019 customer study, only 9% of customers reported resolving their issue completely through self-service; the rest ended up in a live channel anyway. In 2026, self-service has to mean the customer can finish the task, not ask someone else to finish it.
Customer portal vs agent portal: the boundary that matters
An insurance self-service customer portal and an agent portal often run on the same carrier data, but they serve different people with different permissions and a different design brief. Folding both sets of requirements into one product is one of the most common scoping mistakes I see among the carriers I've worked with.
| Dimension | Customer self-service portal | Carrier-side agent portal |
|---|---|---|
| Primary user | Policyholder (individual or small business) | Captive or independent producer, service rep |
| Data scope | One customer's own policies, claims, bills, documents | A producer's whole book across many customers |
| Typical tasks | Pay, download, update details, simple FNOL, track a claim | Quote, bind, endorse, renew, cross-sell, track commissions |
| Usage pattern | A few visits a year, often on a phone | Daily working tool |
| Design priority | Task completion without training | Speed and depth for trained users |
| Escalation role | Hands off to agent or service team with context | Receives the handoff and resolves it |
The architecture that works, in my experience, is one data layer with two surfaces. Our carrier-side agent portal architecture guide covers the producer side in depth; this article stays with the policyholder.
The hybrid model: self-service plus human, not either-or
The framing that hurts most carrier strategy conversations is "self-service versus agent-assisted." The 2026 answer is hybrid: customers route themselves based on the complexity and emotional weight of the task.
Self-service handles transactional work. Pay a bill. Download a certificate of insurance. Update a beneficiary. Add a vehicle. View claim status. Print an ID card. None of these needs a human, and customers would rather not call for them.
Agents and the service team handle judgment work. FNOL for a complex claim. Coverage-gap conversations at renewal. Multi-line consolidation. Disputes. Anything where the customer needs reassurance, advocacy, or trade-off advice.
The portal manages the handoff. When a customer clicks help or starts a chat inside a self-service flow, the agent or service rep should see what the customer was trying to do, where they stopped, and which policies they hold. The conversation starts from the customer's last step, not from "may I have your policy number?"
Bain's recommendation lines up with this: make digital processes as simple as possible for episodes suited to self-service, and make it easy to reach an employee for complex issues. Bain cites Allstate's generative AI tool that summarizes claim details for adjusters so claimants do not have to answer the same question twice, which is the same principle applied to the claims handoff. Gartner sees the service mix moving the same way: its August 2025 survey of 265 customer service leaders expects self-service and live chat to overtake traditional channels as top service technologies by 2027, and notes that as simple cases move to self-service, the assisted interactions left over are more complex.
The agent side of that handoff is where Decerto has the most mileage. The eAgent platform we built for Warta (HDI/Talanx Group) runs 40,000 agents on one system. At that scale, every piece of context an agent has to ask for again is repeated across an entire distribution network, which is why I recommend designing the customer-to-agent handoff before designing the customer screens. The agent-facing half of the handoff lives in Decerto's Agent Portal, the 360-degree agent workplace.
The economics of self-service in insurance operations
Cost per interaction is the clearest part of the business case for an insurance self-service customer portal. Gartner's customer service cost benchmarks from February 2024 put the median cost per contact at $1.84 for self-service and $13.50 for assisted channels such as phone, chat, and email. That gap only turns into savings when self-service actually resolves the request: a customer who fails in the portal and then calls costs the carrier twice.
Three other operational outcomes show up in mid-tier deployments.
After-hours coverage without after-hours staffing. Mid-tier service teams rarely staff phones around the clock. A portal handles the evening and weekend requests - payments, ID cards, claim status - that would otherwise wait until the next business day.
Retention at the moment of change. Bain's research shows that promoters stay longer, buy more, and cost less to serve. In my experience, the retention effect of self-service appears at the moment a customer was about to change something anyway: if adding a vehicle takes two minutes online, the customer has less reason to shop the policy. I have not seen a reliable industry benchmark that isolates the retention lift of a portal on its own, so I recommend measuring it against your own renewal baseline rather than a vendor promise. The CRM side of this is covered in how insurance CRM software improves customer retention and loyalty.
Data accuracy. Customers updating their own contact, beneficiary, and vehicle details produce cleaner data than details re-keyed from a phone call. The downstream effect on claims, renewals, and marketing is real but slow, which is why it rarely appears in a first-year business case.
What the carriers I've worked with consistently underestimate: the cost is front-loaded. The portal is not expensive to run. It is expensive to build well, especially identity resolution across PAS, claims, and billing, and integration with legacy systems. Our single customer view architecture guide covers that identity layer in detail. Plan the budget accordingly.
Compliance considerations for a customer self-service portal in 2026
An insurance self-service customer portal handles nonpublic personal information, payment data, and in some lines health information. For a US P&C carrier, these are the frameworks I would require the vendor to map at the control level:
- NAIC Insurance Data Security Model Law (#668). Requires licensees to run a risk-based information security program, investigate cybersecurity events, and notify the insurance commissioner. According to the NAIC's August 2025 legislative brief, 28 jurisdictions had implemented it; New York regulates the same area through its own cybersecurity regulation.
- GLBA and NAIC Model #672. For insurers, the Gramm-Leach-Bliley Act privacy rules are enforced by state insurance authorities under 15 U.S.C. §6805, and states largely implement them through the NAIC Privacy of Consumer Financial and Health Information Regulation (#672). In practice, privacy notices and opt-out choices should be visible and current inside the portal.
- NY DFS 23 NYCRR Part 500. Since November 1, 2025, Part 500 requires multi-factor authentication for user access to a covered entity's information systems (see the NYDFS multi-factor authentication guidance). Confirm with counsel how this applies to policyholder logins versus staff and agent access, and make MFA available to policyholders either way.
- CCPA / CPRA and other state privacy laws. The California Consumer Privacy Act exempts personal information collected under GLBA (Cal. Civ. Code §1798.145), but not everything else in the portal: website analytics and marketing data can still be in scope. Other state privacy laws treat GLBA-regulated institutions differently, some exempting the entity and some only the data, so map each state you write in.
- TCPA. Prior consent for automated SMS, and under the FCC's 2024 consent-revocation rule customers can revoke consent by any reasonable means, with requests honored within 10 business days.
- CAN-SPAM. Commercial email needs a working opt-out honored within 10 business days; a preference menu is allowed, but it must include an option to stop all commercial email (see the FTC's CAN-SPAM compliance guide).
- Accessibility. WCAG 2.1 level AA is the accessibility standard to write into the RFP for any public-facing portal.
- GDPR. For carriers with European policyholders, the General Data Protection Regulation applies, including its Chapter V rules on international data transfers.
I recommend asking the vendor to map its controls to each framework in writing during the RFP. Verbal assurance in a demo does not survive a regulator inquiry.
How Decerto's Self-Service Customer Portal approaches this
A note on positioning. Decerto's Self-Service Customer Portal is built for mid-tier P&C carriers in the $500M-$5B GWP range. It is not the right fit for $5B+ enterprise carriers running Guidewire or Duck Creek customer-facing tools end to end; those carriers are usually better served by extending the suite they already own. For mid-tier carriers, this is how the product is built:
- Five modules, together or separately. Information Source, Communication Channel, Sales, Claims, and Other Services, configurable for P&C, life, or both. The customer sees one portal.
- Hybrid handoff designed in. A purchase can start online and finish with an agent; the agent picks it up in the Agent Portal with the customer's context, so nobody starts cold.
- Integration with existing core systems. The portal connects to your PAS, claims, and CRM. We scope identity resolution as a data engineering workstream from day one, because in my experience that is where portal timelines slip.
- Compliance mapped at the control level. Model #672 privacy notices, Model #668 security program requirements, state privacy laws where they apply, and GDPR for European business, all mapped to specific portal controls during implementation.
What it will not do: replace your PAS, connect to a core system that exposes no APIs without integration work, or fix customer satisfaction if underwriting turnaround is the real bottleneck. I say that in the first call.
Frequently asked questions
What is an insurance self-service customer portal and how does it work?
It is a secure web and mobile application that lets policyholders handle routine tasks themselves: view policies, pay premiums, download ID cards and certificates, file and track simple claims, and update contact details. It reads live data from the carrier's PAS, billing, claims, and CRM systems, and it hands complex requests to an agent or service representative with the customer's context attached.
How does a self-service portal work alongside insurance agents in 2026?
Through a hybrid model. The portal handles transactional work such as payments, certificates, simple claims, and ID cards. The agent handles judgment work such as multi-line consolidation, retention conversations, and complex claims. The portal manages the handoff so the agent sees what the customer was doing and the customer does not have to repeat themselves.
What are the main benefits of a self-service portal for insurance carriers?
Lower cost to serve: Gartner's February 2024 benchmarks put the median cost per contact at $1.84 for self-service versus $13.50 for assisted channels. Carriers also gain after-hours coverage without extra staffing, cleaner customer data, and consent records built into the portal. Retention effects are real but should be measured against the carrier's own renewal baseline.
How long does it take to implement an insurance self-service customer portal?
In my experience, a phased implementation at a mid-tier carrier runs 6 to 12 months end to end, depending on legacy integration scope and lines of business. A first module, typically billing or document access, can go live within roughly 90 to 120 days. Treat promises of full-scope delivery in 12 weeks with skepticism.
What compliance frameworks apply to an insurance customer self-service portal in the US?
The core set is the NAIC Insurance Data Security Model Law (#668) as adopted by each state, GLBA privacy rules as implemented through NAIC Model #672, NY DFS Part 500 for New York business, CCPA and other state privacy laws where GLBA exemptions do not reach, TCPA for SMS, and CAN-SPAM for email. GDPR applies to European policyholders.
Will a self-service customer portal hurt insurance agent commissions?
In a well-designed hybrid model, no. Self-service takes work agents did not want, such as paying bills, printing ID cards, and sending certificates. Agents keep the commissionable work: new business, cross-sell, and renewals that need a conversation. Carriers that let self-service erode commissionable activity without realigning compensation tend to see agent attrition rise.
What is the difference between a customer portal and an agent portal?
A customer portal shows one policyholder their own policies, claims, bills, and documents and is designed for occasional use without training. A carrier-side agent portal gives producers their whole book, with quoting, binding, endorsements, renewals, and commission tracking, and is designed for daily professional use. The two should share one data layer and a clean handoff.
Should a carrier build a mobile app or a responsive web portal first?
For most mid-tier P&C carriers I recommend starting with a responsive web portal that works well on phones, because policyholders log in a few times a year and many will not install an app for that. A native app earns its cost when frequent-use features such as roadside assistance or photo-based claims justify it. Either way, the same APIs should serve both.
Talk to Decerto about your customer self-service portal program
If your service team is fielding calls that should be self-service, the useful first question is narrow: which two or three customer journeys, moved to self-service, would free the most service capacity without breaking the agent relationship?
What you get from a first call: an operational conversation about your current self-service maturity, your top call drivers, how much change your agent network will tolerate, and the legacy integration you would face. No demo loop. The first 30 minutes is Q&A with me and one of our integration architects.
A note on fit: if you are a $5B+ enterprise carrier running Guidewire or Duck Creek end to end on the customer side, Decerto is probably not your partner. If you are a mid-tier P&C carrier ($500M-$5B GWP) that wants a customer portal connected to your existing PAS and agent network, this is the shape we build for, drawing on 20+ years of insurance projects for carriers including Allianz, Warta (HDI/Talanx Group), and Generali.
Sources
- PwC, 2024 Trust Survey (US): "Trust in US Business Survey" and "How to earn customer trust in your sector", March 2024.
- Bain & Company, "After Years of Customer Loyalty Programs in Insurance, What Works, and What's Next?" (Customer Behavior and Loyalty in Insurance series), H. Naujoks et al., April 12, 2024.
- Gartner, "Benchmarks to Assess Your Customer Service Costs", Document 5164231, February 2024.
- Gartner, press release "Gartner Says Only 9% of Customers Report Solving Their Issues Completely via Self-Service", September 25, 2019.
- Gartner, press release "Gartner Survey Finds Self-Service and Live Chat Will Surpass Traditional Channels as Top Customer Service Technologies by 2027", August 27, 2025.
- National Association of Insurance Commissioners (NAIC), Government Affairs Brief "The NAIC Insurance Data Security Model Law (#668)", August 2025.
- NAIC, Privacy of Consumer Financial and Health Information Regulation (Model #672).
- Gramm-Leach-Bliley Act, 15 U.S.C. §6805 (Enforcement).
- New York State Department of Financial Services, "NY DFS Multi-Factor Authentication Requirements" (23 NYCRR Part 500, Section 500.12), July 2025.
- California Consumer Privacy Act of 2018, Cal. Civ. Code Title 1.81.5, including §1798.145 (Exemptions).
- Federal Communications Commission, "Strengthening the Ability of Consumers To Stop Robocalls", Final Rule, 89 FR 15756, March 5, 2024.
- Federal Trade Commission, "CAN-SPAM Act: A Compliance Guide for Business".
- W3C, Web Content Accessibility Guidelines (WCAG) 2.1, W3C Recommendation (current edition May 6, 2025).
- Regulation (EU) 2016/679 (General Data Protection Regulation), Official Journal of the European Union L 119, May 4, 2016.
.avif)





