Agency portal: Application submission status

Feature summary

The Application submission status feature allows clients to provide more than one unbound option for an agent to choose from when the agent submits an unbound application. The unbound options are customizable and can clarify why the application is submitted unbound and if payment is required.

Disabled Application submission status feature

Without enabling the Application submission status feature, when an agent is on the Submit screen of an application, they can submit the application as bound or unbound. If binding restrictions are in place and triggered, then an agent can only submit an unbound application.

When a policy or application is created, a statement about the policy/application submission type will display in the Application Submission Type subsection, which can be found in the policy’s Overview section beneath the Email Information Related to Policy button.

Note: The Application Submission Type section exists only in the Provider Administrator portal.

Figure 1: The Application Submission Type subsection when the Application submission status feature is disabled.

The Application Submission Type subsection will display one of the following statements:

  • Not applicable – the quote/application is unsubmitted: If the application wasn’t submitted, this statement will display.
  • Not applicable – the policy was created via the Admin portal: If the policy was created in the Provider Administrator portal, this statement will display.
  • The policy application was submitted unbound: If the application was submitted unbound, this statement will display.
  • The policy application was submitted bound: If the application was submitted bound, this statement will display.

The above statements provide some information about the application’s submission type, but without further clarification, underwriters are unaware of why an application is submitted unbound. To gather additional information, underwriters have to contact agents.

Enabled Application submission status feature

Enabling the Application submission status feature allows clients to create unbound options that provide further clarification on why the application is unbound and if payment is required. For example, a client may choose to create the following unbound options:

  • Submit unbound with request to bind coverage (payment required).
  • Submit unbound for underwriting review only (no payment required).

These unbound options provide more information to underwriters, which saves time as underwriters no longer have to contact agents to know why an application was submitted unbound.

Changes

With the Application submission status feature, clients can add additional unbound options that clarify why the application is submitted unbound and identify if payment is required. To enable these changes, a new advanced setting, use-unbound-options, was created. Before you enable the use-unbound-options advanced setting, your unbound options must be configured.

To implement the Application submission status feature:

  1. Configure your unbound options with your BriteCore content analyst.
  2. Change the use-unbound-options advanced setting to True.

When the Application submission status feature is enabled, the unbound options you configured will appear on the Submit screen of the application.

Figure 2: Example of configured unbound options on the Submit screen of an application.

When an agent submits an application and selects an unbound option, the following will happen:

  • The selected unbound option will populate in the Application Submission Type section of the policy.
    Figure 3: The Application Submission Type subsection displaying a selected unbound option.
  • BriteCore will create a note that indicates an application was submitted unbound and identifies the unbound option the agent selected.
  • BriteCore will send emails to designated email addresses that notify the recipients that an application was submitted unbound and identifies the unbound option the agent selected.

Adoption considerations

When an agent submits an application and selects an unbound option, BriteCore will automatically create a note and email that identifies the unbound option selected for the submitted application. You can locate the note on the policy’s Notes screen. The email created will be sent to the email addresses identified in the Application submitted from BriteQuote and Application submitted from BriteQuote (Unbound) In addition to Application submitted from BriteQuote emails administrative alerts found in Settings > System Wide > Administrative Alerts > Policies.

Questions

For questions, or to request this change, contact your customer service analyst or your support team.