Request, review, and approve change coverage request workflows

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Request, Review, and Approve Change Coverage Request Workflows

    This document outlines the workflows for agents to manage service requests related to policy change coverage. It details the process from submitting a request to reviewing and approving changes, ensuring efficient handling of insurance policy modifications.

    Show full answer Show less

    Key Features

    • Workflow Customization: Insurance policy administrators can tailor the predefined workflow to meet organizational needs.
    • Agent Task Management: Agents access their tasks through the Workspace, guided by a case playbook that outlines necessary steps.
    • Request Submission: Requests can be submitted by policy requesters on behalf of customers via multiple service portals, provided the necessary plugins are activated.
    • Automated Workflow Triggers: Upon submission, workflows automatically route tasks to appropriate processor teams based on assignment rules.
    • Quote Management: Processors and underwriters can manage quotes based on customer requests, leading to policy updates and document distribution.

    Key Outcomes

    By implementing this workflow, organizations can streamline the processing of change coverage requests, enhance communication between agents and customers, and ensure timely updates to policy records. The process culminates in the customer either accepting or rejecting the provided quote, resulting in the case being marked as Closed Complete once finalized.

    Learn how agents, using the change coverage limits workflows, resolve service requests for requesting, reviewing, and approving policy change requests.

    The following diagram shows how the application helps agents resolve a change policy coverage request.
    Figure 1. Change coverage workflow example
    Workflow showing how a policy change coverage request is resolved using the Personal Lines Servicing application. For the text description, refer to the workflow steps that follow.
    The insurance policy admin can review and customize this predefined flow based on the business needs of your organization.

    The following workflow routes the case and tasks for changing coverage for a policy to agents in different departments. The agents log in to the Workspace to work on the tasks in their queue. The case playbook guides agents through the steps that are needed to fulfill the request.

    Submitting a request as a policy requester, contributor, or processor
    An insurance policy requester submits a request on behalf of a customer.
    A customer (consumer or contact) can directly submit a request from the Customer Service Portal, Consumer Service Portal, or another self-service portal.
    Note:
    For consumers to submit a request using the Consumer Service Portal, you must have the Consumer Service Portal plugin (com.glide.service-portal.consumer-portal) activated.

    A policy service case is created based on the request type, and routes to the processor.

    Note:
    In the case playbook, the requester or contributor updates the case details in the Initiate and review stage, and submits the change for fulfillment.

    A workflow triggers automatically, and the assignment rules route the associated tasks to the appropriate processor teams.

    Reviewing a request and submitting a decision as a processor
    1. In the case playbook, the processor reviews the policy change request and determines if underwriting is required. The processor approves or rejects the request.
      • If the processor approves the change request, a quote for the requested change is sent to the customer or contributor.
      • If the processor is not sure about whether to approve the requested change, a task is created to advance the case to an underwriter.
    2. An underwriter reviews the case details and approves or rejects the case. If they approve the case to authorize the policy change request, a quote for the requested change is sent to the customer or contributor.
    3. If the customer approves the quote, the processor updates the policy record, sends updated policy documents to the customer, and closes the change coverage task in the playbook.
    Accepting or rejecting a quote as a customer
    When the customer receives a quote after acceptance of the requested policy change, they can accept or reject the quote.

    The case is complete, and the state and stage of the case are set to Closed Complete.