After submission your Quote will end up in one of several states as indicated on that status field in the response. Do not worry if you end up in a non-desired state, you can easily modify the quote to help it pass through to the desired one.
The request, while understood, is outside the underwriting rules established for your Product.
The request is understood and valid and it fits within your underwriting authority, but it was submitted without complete information. This Quote does not yet satisfy the requirements to issue a Policy, and needs more information before its status can be converted to a Bindable or convertable state. This quote will have its rating data populated. Indicative Quotes are common in Personal Lines where there is concern about funnel conversion rates. Partners may want to cut non-critical questions (name, address) to establish a Quote with rating data as quickly as possible. If the Customer is going to purchase the Policy then you can obtain the remaining data during the checkout flow.
The request, while understood, falls outside of your standard underwriting authority and therefore requires additional review before a Policy can be issued. In these cases the Quote is referred to Boost for additional review. After a Quote is reviewed by Boost, the Quote’s status will be updated to either bindable or invalid.
The request is valid and fits within your underwriting authority but requires supporting documentation (e.g. a signed application) to be uploaded before a Policy can be issued. Once the Application is signed or other necessary documents are uploaded, the status of the Quote will be updated to a convertable state.
The request is valid and fits within your underwriting authority. This Quote may be converted into a Policy programmatically.
In most cases, valid data being passed to Boost will yield a bindable status. That will trigger a Quote to be returned to you via webhook or email with an Application Document that must be e-signed by the Customer.
Updated almost 3 years ago