ServiceNow Employee Center for Insurance

This page helps an insurance employee-experience owner decide which requests staff can start in Employee Center and which belong in a case or a workflow that owns the risk. It covers role-specific portal views, the knowledge articles that answer common questions, and why a portal request is not the record of a decision.

Field Agent and Underwriting Workflows

Insurance organisations span dispersed field agents, centralised underwriting teams, and claims processors. Field agents work from remote locations, require fast response times for quote approvals, and often use mobile devices. Underwriters work in teams, need to collaborate on complex cases, and rely on shared access to policy documents. Claims staff handle high-volume routine approvals and escalations.

Employee Center accommodates this structure by creating role-specific portal views. A field agent sees a dashboard with quote requests they’ve submitted, approval status, and next steps. An underwriting team member sees a queue of cases assigned to them, with policy details and underwriting guidelines accessible without leaving the portal. A claims processor sees approved claims ready for payment, denied claims requiring documentation, and appeals in progress.

Commission and Compensation Administration

Field agents in insurance depend on commissions tied to policy sales, underwriting accuracy, and claims handled fairly. Commission structures are complex, subject to policy changes, and prone to disputes if calculations are opaque. Employee Center provides a self-service layer where agents can view commission statements, submit adjustments for disputed calculations, and track approval status.

A scenario: an agent believes they’ve been undercredited for a policy that lapsed and was later reinstated. They submit a commission adjustment request through Employee Center with supporting documentation. The request routes to the compensation team for review, who can pull policy records and verify the claim. If approved, the adjustment is processed; if denied, feedback is recorded and visible to the agent. This transparency reduces disputes and keeps compensation administration efficient.

Commission requests also create audit trails for compliance. Insurance regulators scrutinise compensation practices for potential conflicts of interest. By routing all commission adjustments through Employee Center workflows with documented approvals and denials, you create the evidence regulators expect to see.

Documentation and Knowledge Management

Insurance products change frequently. Underwriting guidelines, exclusion lists, policy templates, and claims procedures evolve quarterly or more often. Keeping field agents and claims staff current is challenging. Email distribution creates chaos; wikis become outdated; paper manuals vanish.

Employee Center’s knowledge base solves this by offering role-based articles. Underwriters see detailed underwriting guidelines, risk assessment frameworks, and exception criteria. Field agents see simplified summaries of those same guidelines, focused on questions they ask customers during sales. Claims processors see claims-specific articles covering denial reasons, appeal procedures, and fraud indicators.

Search in Employee Center helps staff find answers quickly. An agent unsure about coverage for a particular medical condition can search Employee Center, find the relevant policy exclusion article within seconds, and give the customer an accurate answer. This reduces call volume to support teams and improves customer-facing service.

Quote and Approval Routing

Complex insurance quotes often require underwriting approval. A commercial property policy quote might exceed standard guidelines and need underwriter sign-off before the agent can present it to the customer. Simple quotes might be auto-approved by the system; complex ones route to a queue for manual review.

Employee Center allows agents to see the status of their pending quotes: approved and ready to present, under review with expected timeline, or denied with feedback. This visibility lets agents follow up proactively with customers rather than leaving quotes in limbo.

Underwriters, working on the other side, see their approval queue filtered by type or complexity. They might batch-review routine quotes, escalating edge cases to senior underwriters. Employee Center can also notify underwriters when their queue grows too large, preventing backlogs.

Claims Support and Process Transparency

Claims staff handle high-volume requests and need transparent workflows to manage customer expectations. Employee Center can expose a simplified claims tracking interface for internal staff that shows claim status, payment authorization status, appeals under review, and documentation requirements.

When a claims processor needs customer documentation—a medical report for a health claim or repair estimates for a property claim—they can submit a request through Employee Center to the document team, track when the document arrives, and manage the claims decision workflow accordingly.

Common Pitfalls and Mitigation

A frequent issue is knowledge fragmentation. If different departments maintain separate knowledge articles without coordination, field agents might read outdated underwriting guidelines while underwriters reference the current version. Centralize knowledge ownership and establish a single source of truth, updated whenever underwriting rules change.

Another pitfall is approval bottlenecks. If quote approvals route to individual underwriters rather than underwriting teams or if no escalation rules exist when an underwriter is unavailable, quotes stall. Assign approvals to queues and define escalation timelines that match customer expectations for response.

Over-customisation per role can also backfire. If field agents see such a simplified portal that they miss critical information, they’ll seek answers elsewhere, defeating the purpose of Employee Center. Find the right balance between simplicity and completeness for each role through pilot feedback.

Checklist for Insurance Implementations

• Create separate portal views for field agents, underwriters, claims staff, and compensation team
• Build request types for quote approvals, commission adjustments, and documentation requests
• Publish role-specific knowledge articles covering underwriting guidelines, policy exclusions, and claims procedures
• Route commission adjustment requests to the compensation team with policy details accessible in the request form
• Configure auto-approval rules for routine quote approvals and manual queues for complex cases
• Set escalation timelines for pending approvals to prevent quote backlogs
• Integrate Employee Center with policy and claims systems to pre-populate request details
• Track commission adjustment and quote approval metrics to identify bottlenecks and process improvements

Which requests belong in the portal and which need a case

The reader here is the employee-experience owner at an insurance agency or carrier who has been asked to decide what staff can start in Employee Center. The common mistake is to treat the portal as one front door for everything. Field agents, underwriters, claims processors and the compensation team generate different kinds of request, and those requests carry different weight. A quote approval is routine and time-sensitive. A commission dispute can turn into a regulatory matter if it is handled badly. The portal should collect the request cleanly, but what happens next should sit in the workflow that owns the risk.

The last row matters most. A portal is visible to the people it serves, and a complaint about a producer routed through a channel that the producer’s own manager can read is not a complaint process at all. Keep the portal for the requests it handles well, and make the other routes visible from it, so staff know where to go without being pushed into the wrong place. The HR case route should be one click away from the portal, not something staff have to search for.

Why a portal request is not the record of a decision

When an underwriter approves a quote, the approval must be recorded in the system that prices and issues the policy, with the reasons. The portal request is the way the approval was asked for. It is not the evidence that the approval was correct. Teams that confuse the two can end up with a request marked closed, a policy issued, and no reason on file for the exception that was granted. Decide for each request type which record is the authoritative one, and make sure the portal links to it rather than duplicating it.

Setting up the rollout in an order that avoids rework

1. Agree the list of request types with the owner of each downstream queue, and remove any type that has no owner.
2. Write the knowledge article that answers the common question before the matching request type exists, so the portal does not become the first place a question is asked. Articles that help a person make a decision or complete a task are the ones people use, and the employee knowledge articles note covers why a title that does not match the question can make a good article fail.
3. Build one role view at a time, starting with the group that carries the most volume.
4. Pilot with a small group of field agents who will report confusion, and log every point where they ask a question the portal does not answer.
5. Fix the confusion points before opening the view to the wider group.
6. Switch on reporting only after the request types have stopped changing.

Signs the portal is working, and signs it is not

• Staff ask fewer questions by email about the same process, and the questions that remain are new ones.
• Requests are routed to a queue on the first attempt, with few reassignments between teams.
• Approvers clear their queues on a predictable rhythm rather than in bursts before a review.
• Requests with a missing field come back repeatedly, which suggests the form asks for the wrong thing.
• A growing share of requests are filed under “Other”, which means the request types do not match real work.

Mistakes that turn the portal into a second inbox

A common mistake is keeping the email route open alongside the portal with no rule about which one wins. People use whichever is faster, and the portal can end up holding only part of the record. Set one rule for each request type and publish it. The second mistake is a request form with too many fields. A producer who must fill in many answers to ask a simple question will go back to the phone. Ask only for what the receiving queue needs to act, and collect the rest from the record that already holds it. Status visibility, covered in request status transparency, explains where a request is, who owns the next action and what is blocking it, which can reduce the chase emails a second inbox creates.

Questions about Employee Center in an insurance business

Should producers be able to see each other’s commission data?

No. Commission data should be scoped to the person and to the managers who are allowed to see it. Apply role-based access in the portal and in the underlying records, and test it with a user from each role before go-live.

Can a contract agent use the same portal as an employee?

Often yes, but with a narrower view. Contract agents often need quote and document requests and little else. Keep their request types separate and review their access when the contract ends.

What happens to a queue when the approver is away?

Define a delegate for each approval queue before the approver goes on leave, and make the delegation visible to requesters. A queue with no named delegate can become the first thing that breaks in a holiday period, and the requests stall without anyone noticing until a customer calls.

How should reporting on portal activity avoid exposing personal details?

Report on counts, times and request types, and keep names out of the shared dashboards. Where a manager needs detail, the detail should come from the record they are authorized to open, not from a summary report that copies the detail into a wider audience.