Producer and policyholder portals that handle appointments, submissions and policy documents directly, instead of routing every request through an underwriting assistant's inbox.
Experience Cloud lets an insurance organization give producers and insureds secure, role-specific access to the Salesforce data that concerns them. Agencies can apply for appointment, submit new business, upload loss runs and check where each submission stands with underwriting. Insureds can download declarations pages, request certificates and see open service items. Each site uses the same records the internal team works from, so status is never out of date, and sharing rules ensure an agency sees only its own book and an insured sees only their own policies.
Insurance portals serve an unusual hierarchy of users. A carrier or MGA works through agencies, agencies employ many producers and account managers, and each of those people needs different rights: a principal may see commissions while a customer service representative may not. Insureds sit at the end of that chain, and on commercial accounts several people at the insured business may need access too. Experience Cloud handles this through account-based sharing, external roles and permission sets that follow the distribution hierarchy. The harder part is data: submissions, quotes and policies often live in underwriting and policy systems, so the portal becomes the front end for several back-office systems rather than a standalone website.
Prospective agencies apply through the portal, upload errors and omissions certificates and licensing details, and sign agreements electronically. Distribution staff review each application in Salesforce, and approval creates the agency account and its first producer users automatically. Expiring licenses or coverage documents trigger reminders inside the portal, so the carrier keeps a current file without a compliance analyst chasing every agency by email.
For MGAs and specialty carriers, producers submit new business through a guided form that asks only the questions relevant to the class of business, then attach applications, schedules and loss runs. Underwriters receive a complete submission in their queue, and the producer sees each status change, request for information and quote as it happens instead of waiting on a reply email.
Declarations pages, ID cards, endorsements and renewal notices generated by the policy system can be surfaced on both the producer and insured sites. Users find the current version themselves, and the service team stops spending time on resend requests. Document access is logged, which helps when a question arises later about whether the insured received a notice. Renewal packets can be posted before the producer's review call.
Commercial insureds frequently need certificates for contracts and job sites. A portal form collects certificate holder details and any additional insured wording, routes unusual requests for review and releases standard certificates quickly. Holder lists stay on the account, making renewal-time reissues much easier, and the agency can see every certificate issued on its clients' behalf. Nonstandard wording always reaches a person first.
Portal design in insurance starts with the distribution hierarchy: how agencies, sub-agencies, producers and account managers map to accounts, contacts and external users. The second decision is which system owns each record type. Submissions may live in Salesforce, while bound policies and documents are usually mastered in the policy administration system and exposed read-only. The third is sharing, where account relationships or custom sharing logic determine which producer sees which policy, especially when a book moves between agencies or a producer changes firms mid-term.
Bound policies, endorsements and generated documents appear in the portal read-only, so producers and insureds always see what the system of record says.
Submissions flow to the underwriting workbench for rating, and quotes, referrals and declinations flow back to the portal as status updates.
Single sign-on lets agencies use existing credentials, while multi-factor authentication protects insured accounts that expose personal and policy information. Access ends when an agency relationship does.
Producers change agencies and books of business are sold or transferred. Decide how portal access, historical submissions and commission visibility move when that happens, and test those scenarios before launch, because incorrect access after a transfer is both a privacy problem and a relationship problem.
A producer may be licensed and appointed in some states but not others. The portal should restrict submission forms and product options accordingly, drawing on appointment data maintained by the distribution team rather than trusting producers to self-select correctly. Appointment changes should update access promptly.
External user licensing differs by portal type and login pattern. Estimate how many agency staff and insureds will log in, and how often, before choosing license types; the right mix depends heavily on whether insureds need occasional or frequent access.
Client names are anonymized.
Usually, yes. Their tasks, navigation and security needs differ enough that separate sites on the same org work better, sharing the underlying data and components. Producers need submission and book-of-business tools, while insureds need documents, payments and service requests. Separate sites also let each audience have its own branding and sign-in approach without compromise. Components can still be reused across both.
That depends on the integrations. Submission status tracked in Salesforce is immediate. Policy and document data depends on how often the policy administration system shares updates, which may be real time or on a schedule. We agree the acceptable delay for each data type with underwriting and service leaders before designing the integration. The portal should show when data was last refreshed.
Make it faster than email for the tasks producers do most, such as submitting business and checking status, and stop accepting those requests by email once the portal is proven. A pilot group of friendly agencies helps refine the experience first. Training should be short and task-based, ideally recorded so new agency staff can learn on their own.
An Agentforce agent can answer questions about appetite, document locations and submission status, drawing on knowledge articles and the records a user is allowed to see. It should not interpret coverage or make binding decisions. We scope agents to clearly defined tasks, test them against real producer questions and keep a route to a human underwriter.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.